plane-mcp-server

What it does

The Plane MCP server integrates Plane project management with Claude, exposing comprehensive APIs for projects, work items, cycles, and modules. It supports three active transports: local stdio (Python 3.10+ via uvx, recommended), remote HTTP with OAuth authentication, and remote HTTP with personal access token authentication. The legacy SSE transport remains available for backward compatibility. All tools use Pydantic models from the Plane SDK for type safety and validation.

Who it's for

Engineering teams and product managers using Plane for issue tracking and sprint management who want to query, create, and update work items directly from Claude without context-switching to Plane's web interface.

Common use cases

• List and filter work items or projects within a Plane workspace
• Create new work items with assignees, labels, and other metadata
• Search work items across an entire workspace by query string
• Manage cycles (sprints): create, archive, and transfer work items between cycles
• Retrieve detailed information about projects, including members and enabled features

Setup pitfalls

• Stdio transport (local) requires three environment variables: PLANE_API_KEY, PLANE_WORKSPACE_SLUG, and optionally PLANE_BASE_URL
• Remote HTTP with OAuth triggers an interactive browser flow; no credentials needed in config but requires user interaction
• Remote HTTP with PAT requires Authorization and X-Workspace-slug headers instead of environment variables
• Incorrect or missing workspace slug causes silent auth failures; verify the slug matches exactly in Plane