All servers · Email & messaging

Plate

to.plate/mcp · v1.0.0

Measured by MCP Station

Description written by the publisher, not verified

Minimal project management for teams and AI agents.

Connect

claude mcp add --transport http mcp https://plate.to/mcp

{
  "mcpServers": {
    "mcp": {
      "url": "https://plate.to/mcp"
    }
  }
}

Tools as reported by the server

• list_workspaces
  List all Plate workspaces the user is a member of.
• list_projects
  List projects in a workspace.
• list_tasks
  List tasks in a project, or look up a specific task by its public number. To resolve a public ID like 'TES-1': pass taskPrefix='TES' and number=1 — the prefix locates the correct workspace automatically (do NOT hardcode workspaceId when the prefix belongs to a different workspace). Alternatively pas
• list_sections
  List sections (columns) in a project.
• get_task
  Get full details of a task. You can look up by internal taskId OR by public task identifier. To resolve a public ID like 'TES-1' or 'SCD-409', pass it as taskId — the prefix is used to find the correct workspace automatically. Alternatively, pass workspaceId + number (digits only).
• list_comments
  List a task's comments, oldest first. The taskId is the internal document ID from list_tasks — NOT the public SCD-XXX number.
• list_members
  List workspace members with their userId, name, email, and role. Use userId as assigneeId when creating or updating tasks.
• list_activity
  List task activity history (status changes, assignments, moves, etc.) over a time range. Use it for time-based questions like which tasks were completed last week or what someone did. Filters: from/to (ISO 8601 dates), actorId (who made the change — get userIds from list_members), type ('task_status
• list_statuses
  List workflow statuses for a workspace. Use the returned IDs as statusId when creating or updating tasks.
• list_labels
  List task labels for a workspace. Use the returned IDs (or names) as `labels` when creating or updating tasks.
• create_task
  Create a new task in a project section. Only call this tool when creating a brand-new task that does not yet exist. To change the name, status, assignee, or description of an existing task, call update_task instead. To mark an existing task as done, call complete_task instead. If unsure whether a ta
• update_task
  Update one or more fields on an existing task. Use this instead of create_task when the task already exists. The taskId is the internal document ID from list_tasks — NOT the public task number (e.g. SCD-408). To resolve a public number to an internal ID, call list_tasks with workspaceId + number fir
• complete_task
  Mark an existing task as completed or reopen it. Use this instead of create_task when the task already exists and you only need to change its completion state. The taskId is the internal document ID from list_tasks — NOT the public task number (e.g. SCD-408). To resolve a public number to an interna
• delete_task write/delete
  Permanently delete a task. Comments and attachments are removed automatically. The taskId is the internal document ID from list_tasks — NOT the public task number (e.g. SCD-408).
• create_project
  Create a new project in a workspace. If a project with the same name already exists in the workspace, returns the existing project instead of creating a duplicate — check the `created` field in the response to tell the two cases apart.
• update_project
  Rename a project or update its description.
• create_section
  Create a new section (column) in a project. If a section with the same name already exists in the project, returns the existing section instead of creating a duplicate — check the `created` field in the response to tell the two cases apart.
• update_section
  Rename a section.
• delete_comment write/delete
  Delete a comment from a task.
• create_comment
  Add a comment to a task. The taskId is the internal document ID from list_tasks — NOT the public task number (e.g. SCD-408).
• create_tasks
  Create multiple tasks in a project in one action. Use this instead of calling create_task multiple times when the user asks to create several tasks at once. All tasks are created atomically — if validation fails for any item, nothing is created.
• update_tasks
  Update multiple existing tasks in one action. Use this instead of calling update_task multiple times when the user asks to change several tasks at once. All updates are applied atomically.
• complete_tasks
  Mark multiple tasks as completed in one action. Use this instead of calling complete_task multiple times. Already-completed tasks are left as-is.
• delete_tasks write/delete
  Permanently delete multiple tasks in one action. Use this instead of calling delete_task multiple times. All tasks are validated before any are deleted.
• create_sections
  Create multiple sections in a project in one action. Use this instead of calling create_section multiple times.
• update_sections
  Rename multiple sections in one action. Use this instead of calling update_section multiple times.
• create_comments
  Add multiple comments to tasks in one action. Use this instead of calling create_comment multiple times.
• delete_comments write/delete
  Delete multiple comments in one action. Use this instead of calling delete_comment multiple times. All comments are validated before any are deleted.

JSON · Text for agents · Registry updated 2026-06-05