# to.plate/mcp

Minimal project management for teams and AI agents.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.0
- **Author:** to.plate
- **License:** Unknown
- **Endpoints:** streamable-http https://plate.to/mcp
- **Source:** https://plate.to/mcp
- **Endpoint health:** reachable (last checked 2026-10-02T01:40:17.402Z, 6 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 32 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-04T16:36:07.064Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

28 declared. Observed from a live `tools/list` probe.
- `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 l
- `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
- `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 we
- `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 des
- `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
- `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. 
- `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
- `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
- `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 du
- `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
- `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
- `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.

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp\": {\n      \"type\": \"http\",\n      \"url\": \"https://plate.to/mcp\"\n    }\n  }\n}"
```

## Blast radius

Extensive blast radius — deletes data; runs on someone else's infrastructure.
- Floor 35, ceiling 59 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/to.plate%2Fmcp
- Install plan: https://forgeregistry.com/api/v1/packages/to.plate%2Fmcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/to.plate%2Fmcp
- HTML page: https://forgeregistry.com/registry/to.plate%2Fmcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.