Plane MCP Server

What is Plane MCP Server?

Plane MCP Server is a Model Context Protocol (MCP) server that enables LLMs like Claude to interact with Plane.so, allowing them to manage projects and issues through Plane’s API while maintaining user control and security.

How to use Plane MCP Server?

Install via Smithery (npx -y @smithery/cli install @kelvin6365/plane-mcp-server --client claude) or manually by cloning the repo, running npm install && npm run build, then configuring the server in Claude for Desktop’s config file with environment variables PLANE_API_KEY, PLANE_WORKSPACE_SLUG, and optionally PLANE_HOST. Restart Claude for Desktop to use the tools.

Key features of Plane MCP Server

• List all projects in your Plane workspace
• Get detailed information about specific projects
• Create new issues with customizable properties
• List and filter issues from projects
• Get detailed information about specific issues
• Update existing issues with new information

Use cases of Plane MCP Server

• List all projects in a Plane workspace via natural language
• Create a high-priority issue titled “Update social media strategy” in a specific project
• Retrieve all high-priority issues from the Development project
• Update an issue’s priority to urgent in the QA project

FAQ from Plane MCP Server

What are the prerequisites to run Plane MCP Server?

Node.js 22.x or higher, a Plane.so API key, and a Plane.so workspace are required.

What tools are available and how are they named?

Tools include list-projects, get-project, create-issue, list-issues, get-issue, and update-issue. Tool names use hyphens (e.g., list-projects), and the server automatically converts underscores to hyphens for compatibility.

How does authentication work with Plane MCP Server?

Authentication is handled via environment variables: PLANE_API_KEY for your Plane API key and PLANE_WORKSPACE_SLUG for your workspace slug. The API key requires proper Plane permissions to function.

What are the known limitations or common errors?

The assignees parameter must be an array of user ID strings (not a dictionary or object). Supplying the entire issue data inside the assignees field is a common mistake. The server attempts to handle these cases but correct formatting is recommended.

Are any data-modifying operations performed automatically?

No — all operations that modify data (create, update) require explicit user approval before execution. API keys should never be committed to version control.