Supported Tools

    Learn what you can do with PlumoAI MCP tools. These tools work seamlessly together through prompts, and their real power comes from combining them.

    WorkspaceList

    Fetch all workspaces (locations) for the authenticated company and user.

    Parameters: None required

    ProjectList

    Fetch projects. Supports optional filtering by projectId or workspaceId. If workspaceId=-1, returns all projects (useful for searching by name). Note: Also fetch sprints for Scrum projects after getting specific project.

    Parameters: projectId (optional, number), workspaceId (optional, number, -1 for all)

    ProjectTablesList

    Fetch all tables for a given project.

    Parameters: projectId (required, number)

    ProjectCategories

    Fetch state categories for a specific project by project ID.

    Parameters: projectId (required, number)

    ProjectSprints

    Fetch all sprints for a specific project by project ID. Note: if project is not scrum template project then it will return empty array.

    Parameters: projectId (required, number)

    RecordList

    Fetch list of records with including all custom field values of record. Supports filters (project, sprint, table etc.). Note: Required Sprint ID for scrum project. Pass 0 For non Scrum projects, and For scrum project must be pass sprint ID by fetching all sprints and pass current sprint id after identifying from sprint list.

    Parameters: projectId (required, number), sprintId (required, number), workitemTypeId (number, default -1)

    DetailedRecord

    Fetch full details of a record (task). Includes: basic record fields, users (created by, modified by, assignee), comments, attachments, linked tasks, and checklist items.

    Parameters: recordId (required, number)

    CreateRecord

    Create a new record inside a project. Requires projectId, workflowId, statusId and table ID. Supports assignees and optional sprint/parent task linking.

    Parameters: projectId, title, statusId, tableId (required), description, parentTaskId, sprintId, priority, assignedUsers (optional)

    UpdateRecordField

    Update a single field value in a record. Requires recordId and fieldId. Supports text, users, teams, and JSON fields.

    Parameters: recordId, fieldId (required), value, requiresQuotes, text, users, teams, userType, jsonValue, uniqueField (optional)

    ChangeRecordStatus

    Change record status in a record. Requires recordId and statusId.

    Parameters: recordId, statusId (required)

    TableFieldsTab

    Fetch field tabs (sections of fields) for a given table (workitem type).

    Parameters: tableId (required, number)

    CustomTableFields

    Fetch custom fields for a given table (workitem type) within a project. Fetch all and ask all required fields before create new in table.

    Parameters: projectId, tableId (required, number)

    ProjectTableStatusList

    Fetch all table records status list for a given project and optional table id.

    Parameters: projectId (required, string), tableId (optional, string, default "-1")

    AddRecordComment

    Add comment in a record. Requires recordId and comment.

    Parameters: recordId, comment (required, string, HTML format)

    Document_List

    Fetch list of documents. Use ProjectList if projectId is unknown.

    Parameters: projectId (required, number), webDocumentId (optional, number, 0 for all)

    Document_Detail

    Fetch document detail. Use ProjectList if projectId is unknown.

    Parameters: projectId, webDocumentId (required, number)

    Implement-Project

    Create or Implement a Project.

    Parameters: projectId (required, number)

    Rate Limits

    Standard API request limits apply per user's usage of PlumoAI MCP (totaled across all tool calls).

    Currently, this is an average of 180 requests per minute (3 requests per second).

    Some MCP tools have additional, tool-specific rate limits that are stricter:

    • Search: 30 requests per minute

    Note: In most cases, the time it takes to do a complex AI-powered search across PlumoAI and your connected tools means that sequential searches will typically stay under the rate limit. If you encounter rate limit errors, prompt your LLM tool to reduce the amount of parallel searches or operations performed using PlumoAI MCP, and/or try again later.