makeplane/plane-mcp-server

A Model Context Protocol server for
Plane. Gives an AI agent tools to read and manage projects,
work items, cycles, modules, releases, customers and more.
Built on FastMCP and the official
plane-sdk.
- **30 tools**, one per Plane resource, covering 207 operations
- **Local or remote** — stdio, streamable HTTP, SSE
- **OAuth or API key** authentication
Quick start
Get an API key from Plane: **Workspace Settings → API tokens**.
Add this to your MCP client's configuration:
uvx needs no install step. Requires Python 3.10+.
For a self-hosted Plane, add "PLANE_BASE_URL": "https://plane.example.com".
Transports
stdio — local
Runs as a subprocess of your MCP client. Configuration as shown above; needs
PLANE_API_KEY and PLANE_WORKSPACE_SLUG.
HTTP with OAuth — hosted
https://mcp.plane.so/http/mcp
The OAuth flow is handled on connect; no credentials in your config. For clients
without native remote MCP support, bridge with mcp-remote:
Requires Node.js 22+.
HTTP with a personal access token — hosted
https://mcp.plane.so/http/api-key/mcp
| Header | Value |
|---|---|
| Authorization | Bearer |
| X-Workspace-slug | |
SSE — deprecated
https://mcp.plane.so/sse is maintained for backward compatibility only. Use an
HTTP transport instead.
Tools
The server advertises 30 tools, one per resource. Each takes an action
parameter that selects the operation:
Every tool's description lists its actions with their required and optional
parameters, so the catalogue is self-documenting at call time.
**→ Full tool and action reference**
Querying work items
List, count and search accept **PQL**, Plane's query language:
Call get_pql_reference for the full syntax, operators and worked examples.
Upgrading from the per-operation tools
Earlier releases exposed one tool per API operation. **Existing integrations keep
working**: 169 of those 177 names still resolve to the consolidated tool, so a
saved prompt or script calling create_work_item or list_cycles needs no
change. They are no longer advertised, and they keep the parameter names they
shipped with (work_item_id, not workitem_id).
Seven names chose between two operations with a parameter
(manage_project_archive(archive=False)), which one tool-and-action pair cannot
reproduce; calling one tells you its replacement. get_pql_reference is
unchanged.
Configuration
Authentication
| Variable | Required for | Purpose |
|---|---|---|
| PLANE_API_KEY | stdio | API key |
| PLANE_WORKSPACE_SLUG | stdio | Target workspace |
| PLANE_BASE_URL | optional | Plane API URL (default https://api.plane.so) |
The remote transports carry credentials in the connection — the OAuth flow or the
PAT headers — and need none of these.
Outbound proxy for attachment uploads
HTTP_PROXY / HTTPS_PROXY / NO_PROXY (and their lowercase forms) are honored
for the attachment-upload-from-URL fetch (upload_from_url). When a proxy
applies to a given request, **the proxy — not this server — is that request's
SSRF control**: the server does not pin or validate the target's resolved
address itself, since the proxy connects to and resolves the target
independently. Scope NO_PROXY and proxy egress policy accordingly.
Self-hosting the server itself: