Plane MCP Server

Official MCP server for Plane, the open-source project management platform. Manage projects, work items, cycles, modules, pages, and more via AI agents.

Project Management by Plane (makeplane) OAuth2, API Key active

Connect (Remote Server) GitHub Docs npm: @makeplane/plane-mcp-server

Overview

Plane MCP Server is the official Model Context Protocol integration for Plane, an open-source project management tool. It exposes Plane's project management APIs to AI agents and developer tools, enabling them to create projects, manage work items, run cycles and modules, organize initiatives and epics, and interact with workspace pages and comments. The server is built in Python on FastMCP using the official plane-sdk.

The server supports three transport modes: stdio for local self-hosted setups, streamable HTTP (with OAuth or PAT token) for Plane Cloud users, and SSE for legacy integrations. The hosted endpoint at https://mcp.plane.so/http/mcp provides an OAuth flow for cloud workspaces, while self-hosted instances can run via uvx plane-mcp-server stdio with environment variables for API key and workspace slug.

It ships with over 100 tools across 20 categories including projects, work items, cycles, modules, epics, initiatives, milestones, labels, states, comments, links, work item types, relations, activities, work logs, pages, workspaces, and users. An earlier Node.js implementation exists but is deprecated in favor of the current Python and FastMCP based version.

Tools

Tool	Description
`projects`	List, create, retrieve, update, and delete projects; manage members and features.
`work_items`	CRUD operations, search, and retrieval of work items (issues) by identifier across the workspace.
`cycles`	Create and manage project cycles including archiving and assigning work items to cycles.
`modules`	Create and manage project modules and track work items within them.
`initiatives`	Manage workspace-level initiatives with dates, state, and leadership.
`intake_work_items`	Manage the separate intake pipeline for incoming work items before triage.
`work_item_properties`	Manage custom work item properties with type and validation rules.
`epics`	Create and manage epics across their lifecycle.
`milestones`	Create milestones and manage associated work items.
`labels`	Manage project labels for tagging and organizing work items.
`states`	Configure and manage workflow states for projects.
`work_item_comments`	Create, read, update, and delete comments on work items.
`work_item_links`	Add and manage external links attached to work items.
`work_item_types`	Define custom work item type definitions.
`work_item_relations`	Create and remove relationships between work items (blocks, relates to, duplicates).
`work_item_activities`	Retrieve activity logs and change history for work items.
`work_logs`	Log time and effort against work items.
`pages`	Manage workspace and project pages.
`workspaces`	Manage workspace member access and feature configuration.
`users`	Retrieve information about the currently authenticated user.

Setup Guide

Prerequisites

A Plane workspace (cloud at plane.so or self-hosted)
A Plane API key (Personal Access Token), found under Workspace Settings > API Tokens
Your workspace slug (the URL segment after plane.so/)
Node.js 22+ for remote HTTP/SSE transports, or Python 3.10+ with uvx for stdio

Option 1: Remote HTTP with OAuth (Plane Cloud, recommended)

{
  "mcpServers": {
    "plane": {
      "command": "npx",
      "args": ["mcp-remote@latest", "https://mcp.plane.so/http/mcp"]
    }
  }
}

A browser window opens to complete the OAuth flow on first use.

Option 2: Remote HTTP with PAT Token

{
  "mcpServers": {
    "plane": {
      "command": "npx",
      "args": ["mcp-remote@latest", "https://mcp.plane.so/http/api-key/mcp"],
      "headers": {
        "Authorization": "Bearer <YOUR_PAT_TOKEN>",
        "X-Workspace-slug": "<YOUR_WORKSPACE_SLUG>"
      }
    }
  }
}

Option 3: Local Stdio (self-hosted Plane)

{
  "mcpServers": {
    "plane": {
      "command": "uvx",
      "args": ["plane-mcp-server", "stdio"],
      "env": {
        "PLANE_API_KEY": "<YOUR_API_KEY>",
        "PLANE_WORKSPACE_SLUG": "<YOUR_WORKSPACE_SLUG>",
        "PLANE_BASE_URL": "https://your-plane-instance.com/api"
      }
    }
  }
}

Environment Variables

PLANE_API_KEY: Personal Access Token for the workspace (required for stdio)
PLANE_WORKSPACE_SLUG: Workspace identifier (required for stdio)
PLANE_BASE_URL: Defaults to https://api.plane.so; set this to your self-hosted instance URL when applicable

Use Cases

Create and triage work items in a Plane project from an AI assistant, including setting priority, assignees, labels, and target dates
Spin up a new cycle or module, then bulk assign in-flight work items to it for sprint planning
Query work item status, comments, and activity logs to generate stand-up summaries or weekly progress reports
Manage epics, milestones, and initiatives at the workspace level for roadmap and release planning
Log time against work items and pull work log reports for effort tracking

Example Prompts

"Create a new work item in the Mobile project titled Fix login crash on Android 14, set priority to urgent, and assign it to Alex."
"List all work items in cycle Sprint 24 that are still in In Progress state and summarize their latest comments."
"Create a new module called Billing v2 in the Payments project and add work items PAY-101, PAY-102, and PAY-105 to it."
"Add a comment to work item ENG-432 saying that the regression has been reproduced on staging, and link the Sentry issue URL."
"Show me all epics under the Q3 initiative and their current state, then create milestones for each one with a target date of August 30."

Pros

Official server maintained by the Plane team, with the official plane-sdk under the hood
Broad coverage of the Plane API with 100+ tools across projects, work items, cycles, modules, pages, and more
Multiple transport options (stdio, HTTP with OAuth or PAT, SSE) covering both Plane Cloud and self-hosted deployments
Hosted OAuth endpoint at mcp.plane.so removes the need to manage API keys for cloud users

Limitations

Requires either Python 3.10+ with uvx or Node.js 22+ with npx, so toolchain setup is a prerequisite
The earlier Node.js implementation is deprecated, so older configs and tutorials may be out of date
Self-hosted users must manually manage API keys and workspace slugs via environment variables

Alternatives

Linear MCP Server for teams using Linear instead of Plane
Atlassian Jira MCP Server for Jira-based project management
GitHub MCP Server when issues and projects live in GitHub