Plate MCP Server

by plate

answering

Plate is answering right now. Last checked 14 min ago. It exposes 28 tools.

Minimal project management for teams and AI agents.

Uptime history 53 hours of history

53 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

209 ms

Response time

average over 24h

open, no key

Access

streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://plate.to/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 28

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

task

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 task already exists, call list_tasks first.

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).

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).

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 first.

tasks

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.

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.

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 pass workspaceId + number when you are certain of the workspace.

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.

comments

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.

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.

sections

create_sections

Create multiple sections in a project in one action. Use this instead of calling create_section multiple times.

list_sections

List sections (columns) in a project.

update_sections

Rename multiple sections in one action. Use this instead of calling update_section multiple times.

comment

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).

delete_comment

Delete a comment from a task.

complete

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 internal ID, call list_tasks with workspaceId + number first.

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.

project

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.

section

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.

activity

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_changed', or 'completed' for transitions into a Done status), and projectId. Each row gives the task identifier, the status change, who did it, and the task's owner and assignee.

labels

list_labels

List task labels for a workspace. Use the returned IDs (or names) as `labels` when creating or updating tasks.

members

list_members

List workspace members with their userId, name, email, and role. Use userId as assigneeId when creating or updating tasks.

projects

list_projects

List projects in a workspace.

statuses

list_statuses

List workflow statuses for a workspace. Use the returned IDs as statusId when creating or updating tasks.

workspaces

list_workspaces

List all Plate workspaces the user is a member of.

Endpoints

URL	Transport	State	Latency	Checked
https://plate.to/mcp	streamable-http	answering	184 ms	14 min ago

Alternatives to Plate

same job, measured the same way

Hubd

by bzdos

The project tracker for teams of humans and AI agents — in plain files. MCP server + CLI.

113 installs/wk local only

Masaro

by masaro

Task management for teams building with AI agents. Agents claim tasks and report progress.

answering

Agent Memory OS

by yamantaka520

Local-first memory engine for AI-agent teams: team/project ACL, recall, and federated sync.

2 534 installs/wk local only

OneLore

by onelore

Shared project context for AI agents and teams: docs, tasks, and messages that stay current.

answering

Memberpass

by memberpass

MemberPass MCP — manage projects, plans, members, payments, and analytics for Telegram creators.

answering

Orcha

by westonhancock

Securely search and manage workspace context files for AI agents and teams.

answering

Phano Intelligence Platform

by phano

Read-only account intelligence for Customer Success and Account Management teams.

answering

Teamwork

by teamwork

The Teamwork.com official MCP server helps teams efficiently manage client projects with AI.

190 tools answering

Plate — questions

Answers built from our own checks of this server.

What can Plate do?

It exposes 28 tools, read directly from the server on our last check. Among them: complete_task, complete_tasks, create_comment, create_comments, create_project, create_section and 22 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Plate mostly used for?

Its tools cluster around tasks, task and comments. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Plate working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 209 ms. The bar chart above shows every period we have measured.

How do I connect Plate?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Plate need an API key?

No. Plate completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 28 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Plate?

It answers our handshake in 209 ms on average, which is faster than 62% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.