Plane MCP

Connect Claude to your Plane workspace to manage projects, work items, cycles, modules, and more — directly from Claude.

Prerequisites

You need a Plane API key. To generate one:

1. Go to https://<your-plane-host>/<workspace>/settings/account/api-tokens
2. Click Add personal access token
3. Copy the token

Setup

A single Docker container runs the Plane MCP server centrally so that team members can connect from Claude Code or Claude Desktop without installing anything locally.

How it works

Claude Code / Desktop
        │
        │  HTTP (Authorization: Bearer <api_key>)
        ▼
┌─────────────────────┐
│  Node.js Proxy :3000│  ← auth gate, header whitelist, bulk_create handler
│         │           │
│         ▼           │
│  Python MCP :8211   │  ← plane-mcp-server (upstream)
└─────────────────────┘
        │
        │  REST API (X-Api-Key)
        ▼
   Plane Instance

• The Node.js proxy on port 3000 is the only exposed endpoint. It enforces authentication (rejects requests without a valid Authorization: Bearer header), whitelists headers forwarded upstream, validates inputs, and handles the bulk_create_work_items tool directly with rate-limit retry logic.
• The Python MCP server (plane-mcp-server) runs internally on port 8211. It implements the MCP protocol and translates tool calls into Plane REST API requests.
• Each user authenticates with their own Plane API key. The proxy passes it through to both the Python server and the Plane API — no shared credentials are stored on the server.

Endpoints:

Limits: Request body 1 MB, response body 5 MB, bulk create max 100 items per call.

Connect from Claude Code

claude mcp add plane-mcp --transport http \
  --url https://<server-host>/mcp \
  --header "Authorization: Bearer YOUR_PLANE_API_KEY"

To target a specific workspace:

claude mcp add plane-mcp --transport http \
  --url https://<server-host>/mcp \
  --header "Authorization: Bearer YOUR_PLANE_API_KEY" \
  --header "x-workspace-slug: your-workspace"

Connect from Claude Desktop (HTTP transport)

Claude Desktop does not natively support HTTP transport, so we use mcp-remote as a bridge. Add to your claude_desktop_config.json:

macOS / Linux:

{
  "mcpServers": {
    "plane": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://<server-host>/mcp",
        "--header",
        "Authorization: Bearer ${PLANE_API_KEY}"
      ],
      "env": {
        "PLANE_API_KEY": "YOUR_PLANE_API_KEY"
      }
    }
  }
}

Windows:

On Windows, npx often fails due to spaces in the Node.js install path (C:\Program Files\nodejs\). Install mcp-remote globally first, then reference it directly:

npm install -g mcp-remote

{
  "mcpServers": {
    "plane": {
      "command": "mcp-remote",
      "args": [
        "https://<server-host>/mcp",
        "--header",
        "Authorization: Bearer ${PLANE_API_KEY}"
      ],
      "env": {
        "PLANE_API_KEY": "YOUR_PLANE_API_KEY"
      }
    }
  }
}

Deploy the Server

# Clone and start
docker compose up -d --build

Environment variables:

Health check:

curl http://localhost:3000/health

Available Tools

License

MIT