plane-mcp-server

What it does

The Plane MCP server acts as a gateway between Claude and Plane, a project management platform. It exposes Plane's project, work item, cycle, and module APIs through the MCP protocol. The server supports multiple transports: stdio for local use with API keys, and HTTP with OAuth or Personal Access Token (PAT) authentication for remote connections. A legacy SSE transport is also available for backward compatibility.

Who it's for

Teams using Plane who want Claude to participate in project management—project managers creating or updating issues from conversation, engineers integrating AI into sprint workflows, and developers automating work-item creation and assignment across a Plane workspace.

Common use cases

• List projects, work items, and cycles without leaving Claude to gather context
• Create new work items with assignees, labels, and descriptions from conversation
• Search work items across a workspace to find related issues or prior decisions
• Manage cycles: create, update, and transfer work items between sprints
• Update project configuration and features programmatically via Claude

Setup pitfalls

• Requires Python 3.10+ for stdio or Node.js 22+ for HTTP/SSE transports
• For stdio, set env vars PLANE_API_KEY, PLANE_WORKSPACE_SLUG, and PLANE_BASE_URL; remote transports use OAuth or PAT headers instead
• Automated scanning reported zero tools despite extensive tooling in the README—verify tool availability against your Plane SDK version
• No CI configured; last update was recent but evaluate stability for production use