Plane MCP Server: project management in Plane
Plane MCP Server
Official Plane MCP server: the agent manages projects, work items, cycles and releases through 30 tools
- 353 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The API key lets the agent create, change and delete projects and tasks in the workspace
- Requests to Plane are logged together with their content until you set LOG_PAYLOADS=false
Install
- Works in
Manual install
PLANE_API_KEY=... PLANE_WORKSPACE_SLUG=... uvx plane-mcp-server stdioLocal run through uvx; substitute your own key and workspace slug.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The API key lets the agent create, change and delete projects and tasks in the workspace
- Requests to Plane are logged together with their content until you set LOG_PAYLOADS=false
This is third-party code. Review the repository files before installing.
What it does
The MCP server gives an agent access to a Plane workspace: projects, work items and cycles. It also covers modules, releases, pages, customers and members. There are 30 tools, one per resource type, and the agent picks the operation with an action parameter, which makes 207 operations in total. Lists, counts and searches over work items accept PQL, Plane's own query language. An agent can, for example, pick started tasks with urgent priority or count a member's tasks by state. The get_pql_reference tool returns the syntax guide. Locally the server runs through uvx, which needs an API key and the workspace slug. Plane also hosts two endpoints: one with OAuth sign-in and one with a personal access token in headers. The server works with a self-hosted Plane too.
Who it is for. For teams that track work in Plane and want an agent in Claude Code or Cursor to create, search and triage work items.
Good fit when
- You want to create a batch of tasks from a spec without opening the Plane interface
- You need urgent tasks in progress pulled out with a PQL query and summarized in a report
- Before cycle planning you need task counts per member and state
- You want to close tasks and leave comments from a coding session once a commit is ready
- Plane is self-hosted and the agent needs its API at your own address
Not a fit when
- The workspace lives in another tracker such as Jira or Linear, which have their own servers
- You still rely on the deprecated Node.js package @makeplane/plane-mcp-server, which this Python server replaces
- The environment blocks outbound requests to Plane and OAuth sign-in is not available
Example request
Show urgent tasks in the started state in the Backend project and group them by assignee.MCP
- Transport
- stdio, http
- Authentication
- API key
Environment variables
PLANE_API_KEYrequired, secret- API key from the API tokens section of workspace settings; required for stdio.
PLANE_WORKSPACE_SLUGrequired- Slug of the workspace the agent works with.
PLANE_BASE_URL- Plane API address, https://api.plane.so by default; change it for a self-hosted instance.
Limitations
Local mode needs Python 3.10 or newer, a Plane API key from the API tokens section of workspace settings, and the workspace slug. The agent's rights equal those of the key owner: the server does not separate read from write.
For attachment uploads from a URL the server does not validate the target address, so protection against requests to internal addresses has to come from your environment's proxy. The hosted SSE endpoint is kept for compatibility; use HTTP for new connections.
Whether the hosted mcp.plane.so endpoints are reachable from Russia has not been checked.
How to disable. Remove the plane block from the MCP client configuration and revoke the API key in the Plane workspace settings.
FAQ
How do I connect Plane to Claude Code or Cursor?
Add an MCP server with the command uvx and the arguments plane-mcp-server and stdio, and set PLANE_API_KEY and PLANE_WORKSPACE_SLUG in the environment. The key is created in workspace settings under API tokens.
Do I need to install the server to use Plane?
No, you can connect to the hosted endpoint https://mcp.plane.so/http/mcp. Sign-in goes through OAuth, and clients without remote server support can use the mcp-remote bridge, which needs Node.js 22 or newer.
What is PQL in Plane MCP?
PQL is Plane's query language for work items. It works in the list, count and search actions and can, for example, pick urgent tasks in the started state. The get_pql_reference tool returns the full syntax with examples.
How do I connect a self-hosted Plane?
Set PLANE_BASE_URL to the address of your instance, for example https://plane.example.com. The key and the workspace slug stay the same.
Is the old Node.js server still needed?
No. The Node.js package @makeplane/plane-mcp-server is deprecated and unmaintained. Its PLANE_API_HOST_URL variable is now called PLANE_BASE_URL, and the other names match.
Discussion
No questions or reviews yet.
Related
MCP serversPlanfix MCP
planfix-mcp
Planfix MCP server: tasks, projects, contacts, comments and employees through the REST API
An MCP server for Linear: issues, projects, cycles, milestones, documents and project updates via the GraphQL API
MCP server for Linear: the agent creates and updates issues, searches the tracker and adds comments through the Linear API
Trello MCP server with 57 tools: cards, lists, checklists, attachments, comments, custom fields and workspaces, plus acceptance-criteria extraction
monday.com's official MCP server: boards, items, columns, forms and the full GraphQL API, plus a monday CRM plugin
Official Anytype MCP server: an agent searches, creates and edits objects, lists and types in your knowledge base
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Plane MCP Server: project management in Plane (this entry) | yes | API key | 353 | |
| Linear MCP Server | no | API key | 346 | the same job for the Linear tracker, a different workspace |
| Jira MCP | no | key is optional | 96 | the same job for Jira, Atlassian's tracker |
README in short
The documentation splits setup into three transports: local stdio, hosted HTTP with OAuth and hosted HTTP with a token. Separate sections cover environment variables, the OAuth redirect allowlist and logging settings.