The official Plane MCP server provides integration with Plane APIs, enabling full AI automation of Plane projects, work items, cycles and more.
Most monitoring and observability work still happens through a UI a human drives. Plane MCP server moves it into the conversation instead. The official Plane MCP server provides integration with Plane APIs, enabling full AI automation of Plane projects, work items, cycles and more.
A Model Context Protocol (MCP) server for Plane integration. This server provides tools and resources for interacting with Plane through AI agents.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The server publishes 12 tools. What each one is for:
Authentication — The server requires authentication via environment variables:Logging — The server emits structured JSON logs. Each tool call is logged with its tool name, duration, status, and (when available) the opaque user id andProjects — The Projects tool exposed by this serverCycles — The Cycles tool exposed by this serverModules — The Modules tool exposed by this serverInitiatives — The Initiatives tool exposed by this serverMilestones — The Milestones tool exposed by this serverLabels — The Labels tool exposed by this serverStates — The States tool exposed by this serverPages — The Pages tool exposed by this serverWorkspaces — The Workspaces tool exposed by this serverUsers — The Users tool exposed by this serverConfiguration is passed through the environment: PLANE_API_KEY, PLANE_WORKSPACE_SLUG, PLANE_BASE_URL, PLANE_API_HOST_URL, PLANE_OAUTH_ALLOWED_REDIRECT_URIS, LOG_USER_INFO, PLANE_ACCESS_TOKEN, YOUR_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Plane's toolset — Authentication, Logging, Projects and 9 more — is a fair guide to whether it matches your workflow.
This entry was verified against Plane's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Authentication | The server requires authentication via environment variables: |
| Logging | The server emits structured JSON logs. Each tool call is logged with its tool name, duration, status, and (when available) the opaque user id and workspace slug. |
| Projects | The Projects tool exposed by this server. |
| Cycles | The Cycles tool exposed by this server. |
| Modules | The Modules tool exposed by this server. |
| Initiatives | The Initiatives tool exposed by this server. |
| Milestones | The Milestones tool exposed by this server. |
| Labels | The Labels tool exposed by this server. |
| States | The States tool exposed by this server. |
| Pages | The Pages tool exposed by this server. |
| Workspaces | The Workspaces tool exposed by this server. |
| Users | The Users tool exposed by this server. |
{
"mcpServers": {
"plane": {
"command": "uvx",
"args": ["plane-mcp-server", "stdio"],
"env": {
"PLANE_API_KEY": "<your-api-key>",
"PLANE_WORKSPACE_SLUG": "<your-workspace-slug>",
"PLANE_BASE_URL": "https://api.plane.so"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PLANE_API_KEY | Credential the server authenticates with. | Yes |
| PLANE_WORKSPACE_SLUG | Configuration value read at startup. | Optional |
| PLANE_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| PLANE_API_HOST_URL | Endpoint or connection string the server talks to. | Yes |
| PLANE_OAUTH_ALLOWED_REDIRECT_URIS | Filesystem location the server is allowed to use. | Optional |
| LOG_USER_INFO | Configuration value read at startup. | Optional |
| PLANE_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| YOUR_API_KEY | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
A Model Context Protocol (MCP) server that enables AI assistants to integrate with Prometheus Alertmanager
Auth0 Model Context Protocol (MCP) Server (Beta) — A secure and extendable implementation of an MCP server that provides AI assistants with
Query Onchain data, like ERC20 tokens, transaction history, smart contract state.