# Plate MCP server

Source: https://glimind.com/server/mcp-registry%2Fto.plate%2Fmcp
Registry id: `mcp-registry/to.plate/mcp`
Status: live (checked 2026-10-27T06:17:09.666Z)

## Verdict

Plate MCP server answered 99.87% of Glimind's liveness checks over 30 days, better than 27% of MCP servers, with 725 ms median handshake and 6 outages in 90 days. Its agent-readiness grade is A (98/100) across 28 tools, costing an agent about 4,929 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.87% | 27% of MCP servers |
| Median handshake latency | 725 ms | 30% of MCP servers |
| p95 handshake latency | 3288 ms | — |
| Checks in 30 days | 4,922 | — |
| Outages, 90 days | 6 | — |
| Median recovery | 6 min | — |
| Agent-readiness score | 98/100 (A) | 91% of MCP servers |
| Tools | 28 | — |
| Tool-list size for an agent | ~4,929 tokens | 38% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "plate-mcp-server": {
      "type": "http",
      "url": "https://plate.to/mcp"
    }
  }
}
```

Claude Code:

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

## Tools (28)

- `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. 
- `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.
- `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_comments`: Add multiple comments to tasks in one action. Use this instead of calling create_comment multiple times.
- `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 duplica
- `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 du
- `create_sections`: Create multiple sections in a project in one action. Use this instead of calling create_section multiple times.
- `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 des
- `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
- `delete_comment`: Delete a comment from a task.
- `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.
- `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 numb
- `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.
- `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
- `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 we
- `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_labels`: List task labels for a workspace. Use the returned IDs (or names) as `labels` when creating or updating tasks.
- `list_members`: List workspace members with their userId, name, email, and role. Use userId as assigneeId when creating or updating tasks.
- `list_projects`: List projects in a workspace.
- `list_sections`: List sections (columns) in a project.
- `list_statuses`: List workflow statuses for a workspace. Use the returned IDs as statusId when creating or updating tasks.
- `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 l
- `list_workspaces`: List all Plate workspaces the user is a member of.
- `update_project`: Rename a project or update its description.
- `update_section`: Rename a section.
- `update_sections`: Rename multiple sections in one action. Use this instead of calling update_section multiple times.
- `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_ta
- `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 upd

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.