A client that asks permission once per tool call turns "create the fifteen tasks we just agreed" into fifteen interruptions; create_tasks makes it one, and it lands atomically. The same thinking shows in create_project and create_section returning the existing item with created: false instead of a duplicate, which is what makes a setup safe to run twice. Two details before wiring an agent in: the write scope is chosen at sign-in, so a genuinely read-only connection is available, and get_task takes the SCD-426 style reference people quote rather than making you resolve an internal id first.
A remote MCP server for Plate, a lightweight project and task manager built for automation. Read tools are always available; write tools depend on the scope you grant at sign-in. Every tool returns structured output with a declared outputSchema, so clients that support structured content get typed results rather than prose to re-parse.
- Reading: list_workspaces, list_projects, list_sections and list_tasks — up to 100 by default and configurable — with list_statuses, list_labels and list_members supplying the values a write call will need
- get_task accepts an internal id, a prefixed reference like SCD-426, or a workspace id plus public number: the form a person would actually paste
- list_comments returns a task's comments oldest first, each carrying contentText as Markdown and content as Plate nodes
- list_activity is the change history over a date range, filtered by actor, by type such as completed, or by project — the tool behind "what got finished last week"
- Writing: create_task, update_task for name, status, assignee, section, description or labels, complete_task which also reopens, delete_task, create_project and update_project, create_section and update_section, create_comment and delete_comment
- create_project and create_section return the existing one with created: false when the name is already taken, so re-running a setup does not leave duplicates behind
- Batch tools execute atomically and collapse the confirmation prompts in clients that ask once per call: create_tasks, update_tasks and delete_tasks up to 50, complete_tasks up to 100, create_sections and update_sections up to 30, create_comments and delete_comments up to 50
Point a client at https://plate.to/mcp over HTTP. There is no API key: the first call opens a browser for OAuth 2.0 with PKCE, where you choose read or read write and approve. Tokens refresh on their own and you only re-authorize if the refresh token lapses after 30 days. Access is revoked from Workspace Settings → Apps inside Plate.
One command — npx -y mcp-remote https://plate.to/mcp