plane

The Plane MCP Server exposes a set of MCP tools that let an LLM interact with Plane.so to manage projects and issues. It includes operations to list projects, retrieve project details, create new issues with Plane-specific fields, list and filter issues, retrieve individual issues, and update existing issues. When integrated with Claude or other MCP clients, the server converts generic MCP tool calls into Plane API requests, handling authentication via your Plane API key. You can configure the server in your MCP client (e.g., Claude for Desktop) by supplying the Plane API key and workspace slug as environment variables so the server can perform actions on your Plane workspace. Tools are named with hyphens (e.g., list-projects, create-issue) and can be invoked by the MCP client to drive Plane workflows.

Typical usage involves listing projects to identify the workspace scope, then creating or updating issues within a chosen project, optionally setting priority, state, and assignees. The server also provides filtering options for listing issues, so you can query by priority, state, or assignee to zoom in on relevant items. This enables LLMs to participate in project management tasks while ensuring that sensitive operations are performed with explicit user approval and proper Plane permissions.

Prerequisites:

• Node.js 14+ (the Plane server README specifies Node.js 22.x or higher as a prerequisite)
• npm (comes with Node.js)
• A Plane.so API key and a Plane workspace slug

Option A: Quick setup via Smithery

1. Install to a supported client (Claude, Cursor, etc.) using Smithery:

# Install to Claude for Desktop
npx -y @smithery/cli install @kelvin6365/plane-mcp-server --client claude

This automates configuration for Claude. After installation, add your Plane API key and workspace slug in the Claude settings as directed by Smithery.

Option B: Manual setup

1. Clone the repository and install dependencies

git clone https://github.com/kelvin6365/plane-mcp-server.git
cd plane-mcp-server
npm install

2. Build the server (if a build step exists for this project)

npm run build

3. Run or package the server as needed (see mcp_config for the node-based startup path)

npm run dev

4. In your MCP client, configure the server under the mcpServers section with command "node" and the path to the built index.js, plus the required Plane environment variables.

Tips and considerations:

• Keep your Plane API key secure; do not commit it to version control.
• If you use a host or proxy, set PLANE_HOST accordingly to ensure the server can reach Plane API endpoints.
• When updating issues or creating them, ensure assignees is an array of user ID strings; avoid sending objects or dictionaries in that field to prevent API rejections.
• The MCP server converts underscores to hyphens in tool names automatically, so you can use either format in your prompts.
• Start with list-projects to validate connectivity before performing create/update operations.
• Ensure your Node.js version matches or exceeds the prerequisites in the README (Node.js 22.x or higher is recommended).
• If your environment requires local development, use the npm run dev script as documented in the repository’s Development section.