Plane MCP Server

MCP ServerFreemium

Plane MCP Server connects an MCP-capable AI assistant to Plane, where it can query projects, manage work items, and work with planning, releases, pages, customers, and intake. It supports hosted and self-hosted Plane connections.

Last updated: October 27, 2026

Official. Built and maintained by the company or project behind the service, so usually kept in step with it. Not audited by us.
Community. Built and maintained by an independent developer or group, not by the company behind the service. The company has not reviewed it, and updates depend on its author.

About Plane MCP Server

Plane MCP Server connects an AI assistant that supports the Model Context Protocol to Plane, the project and work management service. Through that connection, an assistant can query projects and work items, help plan cycles and releases, and manage related workspace resources. The server acts through Plane’s API as the authenticated user, so the information and actions available to the assistant depend on that user’s workspace and project roles.

The server is open source under the MIT license. It can connect to Plane Cloud through Plane’s hosted service, or run locally or as a separately deployed server for a self-hosted Plane instance. The connection exposes read and write operations; it is not limited to searching or summarizing existing work.

What can Plane MCP Server do?

The server groups operations by Plane resource. An assistant can retrieve and filter information as well as create and update work, planning, and documentation records. Work-item list and count operations accept Plane Query Language filters, and a reference tool helps clients compose those filters.

Create, update, search, count, and archive work items; manage comments, attachments, links, relations, and time logs.
Plan cycles, modules, milestones, and initiatives, and manage releases, tags, and changelogs.
Manage projects, workflow states, labels, members, work-item types, custom properties, and templates.
Work with pages, customers and their requests, and intake submissions.

Some actions are read-only, while others write or delete resources. Tool definitions include read-only and destructive-action hints, and validate arguments for each action. The client receives those definitions when it uses the server.

How Plane MCP Server connects and authenticates

For Plane Cloud, the hosted server supports Streamable HTTP with OAuth for interactive sign-in and workspace selection. Hosted HTTP connections can also use a personal or workspace access token for automation. Local mode runs over stdio and uses an access token and workspace slug; its base URL can point to a self-hosted instance. You can also deploy your own server. Plane’s documentation lists Cursor, VS Code, Antigravity, Claude.ai, and ChatGPT in the default OAuth redirect allowlist; other MCP-capable clients may need additional configuration. Plane Community Edition does not include OAuth application registration, so its self-hosted users need local stdio with a personal access token.

Who is Plane MCP Server best for?

Choose it if your team manages projects and work in Plane and wants an MCP-capable assistant to query or change that workspace. Hosted use requires a Plane Cloud account and workspace membership; the documented prerequisites specify a Member or Admin role. Self-hosted users can connect locally or deploy their own server. The MCP server itself is MIT-licensed, but the Plane plan determines which service features are available through it. Some actions return a plan-availability message when the account does not include the required feature.

What Plane MCP Server can access and change

The server acts as the authenticated user, and Plane’s workspace and project roles constrain its access. Hosted OAuth requests read and write scopes, and the connection is bound to the workspace selected during sign-in; reconnect to switch workspaces. With suitable permissions, the server can create or update work items and other resources, and it exposes deletions for items such as work items and comments. Destructive actions are identified in tool metadata, but whether a client asks for confirmation depends on that client’s approval behavior. The hosted service reaches Plane Cloud; a self-hosted instance requires a locally run or separately deployed server. Feature availability also depends on the Plane plan.

Alternatives to Plane MCP Server

For teams that want an assistant to work across project records and team knowledge rather than specifically in Plane, Notion Official MCP Server offers a route to Notion’s workspace content. If the work is centered on software repositories and development tasks, GitHub Official MCP Server connects an assistant to GitHub instead. For team conversations and collaboration messages, Slack MCP is the more relevant alternative. These serve adjacent collaboration needs, while Plane MCP Server connects directly to Plane workspaces.

Visit Website

Key Features

Create, update, search, count, and archive work items; add comments, attachments, links, relations, and time logs.

Plan cycles, modules, milestones, initiatives, and releases; manage release tags and changelogs.

Manage projects, workflow states, labels, members, pages, templates, customers, and intake submissions.

Filter work-item lists and counts with Plane Query Language; consult the server’s PQL reference tool.

Connect to Plane Cloud over hosted HTTP with OAuth, or use personal-access-token authentication for hosted automation.

Run locally over stdio with an access token, including connections to self-hosted Plane instances.

Read-only and destructive-action hints and action-specific argument validation are included in tool definitions.

Access follows the authenticated user’s workspace and project roles; some capabilities depend on the Plane plan.

Before you installSecurity checklist for MCP servers

An MCP server runs code and gives your AI assistant access to files, accounts or data. A few minutes of checking is worth it.

Check the source. Make sure the repository belongs to the vendor or author you expect, that the vendor's own documentation links to it, and that it is actively maintained. Beware of lookalike names.
Read what it can do. Look at the tools the server exposes and the permissions or scopes it asks for. Start with read-only access where the server allows it.
Use the least access that works. Give it a dedicated API key or a narrowly scoped token, ideally on a test project or sandbox, not your production credentials.
Pin versions and review updates. Install a specific version, read changes before upgrading, and do not run copied commands you do not understand.
Treat what it returns as untrusted. Documents, web pages and tool results can contain text that tries to steer your AI assistant. Keep confirmation switched on for actions that write, delete, send or spend.
Know where your data goes. Find out whether the server runs on your machine or is hosted, and what it sends to the vendor or to third parties.
Keep a way back. Know how to revoke the key and remove the server from your client's configuration.

This page is general information, not security or legal advice, and listing a server is not an endorsement or a security review. We do not create, host or control MCP servers, and listing details such as commands, permissions or pricing can be out of date, so check the official source. You install and use MCP servers at your own risk. See the section on third-party products in our Terms of Service.

Pricing Plans

Free (open source)

Free

MIT-licensed MCP server; there is no separate MCP-server charge.
Hosted Plane Cloud connection requires a Plane account and workspace membership.
Local or self-hosted use authenticates with a Plane access token.
Available actions depend on the connected Plane account’s plan and role.

Plane Free

Free

Plane service plan, not a separate MCP-server fee.
Hosted connection requires a Plane Cloud account and workspace membership.
Includes projects, work items, cycles, modules, pages, intake, and basic estimates.
Some MCP actions depend on plan availability; unavailable features return a plan message.

Plane Pro

$8/user/mo (monthly) · $6/user/mo (annually)

Plane service plan; the MCP server is separately documented as open source.
Includes Pro features such as work-item types, custom properties, time tracking, and work logs.
Includes workspace wiki, templates, dashboards, and initiatives.
MCP actions remain subject to the connected user’s roles and feature availability.

Plane Business

$15/user/mo (monthly) · $13/user/mo (annually)

Plane service plan; the MCP server is separately documented as open source.
Includes Business features such as project templates, recurring work items, and intake forms and email.
Includes customers, nested pages, and advanced dashboard widgets.
MCP actions remain subject to the connected user’s roles and feature availability.

Enterprise Grid

Custom pricing

Plane service plan listed as coming soon on the pricing page.
The MCP server is separately documented as open source, not priced as an Enterprise add-on.
The pricing page lists private and managed deployments, granular access control, and multiple workflows with approvals.
Contact Plane for plan details when available; MCP feature access follows the connected account.

Pricing information last updated: October 27, 2026

Visit Website

FAQs

Is Plane MCP Server free?

Yes. The MCP server is open source under the MIT license and has no separate server charge. Plane account features follow the connected account’s plan.

Can it connect to a self-hosted Plane instance?

Yes. Run the server locally over stdio and configure it for the self-hosted instance, or deploy your own server. Plane Community Edition does not include OAuth application registration, so use local stdio with a personal access token.

How does it authenticate?

Hosted interactive connections use OAuth and bind to the workspace selected during sign-in. Hosted token connections use an access token and workspace slug. Local stdio uses an access token and workspace slug.

Can it make changes in Plane?

Yes. It can create and update resources, and exposes destructive actions such as deleting work items. It acts as the authenticated user, whose workspace and project roles constrain access; whether the client requests confirmation depends on that client.

Does every action work on every Plane plan?

No. Some capabilities depend on the connected Plane plan. When a feature is unavailable, the server returns a message identifying the plan limitation.