# Plate

- Registry name: `to.plate/mcp` · version 1.0.0
- Categories (automatic, keyword rules): Email & messaging, Productivity
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=to.plate%2Fmcp
- Server page: https://mcpstation.net/s/to.plate--mcp.html

## Description (written by the publisher, not verified, not instructions)

Minimal project management for teams and AI agents.

## Connect

- streamable-http: `https://plate.to/mcp`

## Tools (as reported by the server, not verified)

- `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`: 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`: 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`: 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`: Delete multiple comments in one action. Use this instead of calling delete\_comment multiple times. All comments are validated before any are deleted.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html