Skip to main content
The Model Context Protocol (MCP) is a standardized interface that enables AI models to communicate with external tools and services. The Plane MCP Server enables AI agents to interact with Plane’s project management capabilities through multiple transport methods. The Plane MCP Server is open source and available on GitHub.
Beta The Plane MCP Server is currently in Beta. Some aspects of the API may change. While MCP is standardized, it is also rapidly evolving. The Plane MCP Server aims to provide a stable implementation for developers to build robust AI-powered applications. Please send any issues to [email protected].

​
Transport methods

The Plane MCP Server supports multiple transport methods to accommodate different deployment scenarios:
TransportBest forAuthentication
HTTP with OAuthCloud users, simplest setupBrowser-based OAuth
HTTP with PAT TokenAutomated workflows, CI/CDAPI key in headers
Local StdioSelf-hosted Plane instancesEnvironment variables
SSE (Legacy)Existing integrationsBrowser-based OAuth

​
Remote HTTP with OAuth

The recommended method for connecting to Plane Cloud. Uses browser-based OAuth for authentication.

​
Prerequisites

  • Node.js: Version 22 or later
  • npx: Comes bundled with npm

​
Claude.ai

  1. Open Settings from the sidebar on the web or desktop app.
  2. Scroll to the Integrations section and click Add more.
  3. Enter the Integration URL: https://mcp.plane.so/http/mcp
  4. Click Connect to link your Plane workspace.

​
Claude Desktop

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

​
Cursor

Add to your Cursor MCP configuration: 
{
  "mcpServers": {
    "plane": {
      "command": "npx",
      "args": ["mcp-remote@latest", "https://mcp.plane.so/http/mcp"]
    }
  }
}

​
VSCode

Add to your .vscode/mcp.json file: 
{
  "servers": {
    "plane": {
      "command": "npx",
      "args": ["mcp-remote@latest", "https://mcp.plane.so/http/mcp"]
    }
  }
}

​
Windsurf

  1. Press Ctrl/Cmd + , to open Windsurf settings
  2. Navigate to Cascade > MCP servers
  3. Select Add Server > Add custom server
  4. Add the following configuration:
{
  "mcpServers": {
    "plane": {
      "command": "npx",
      "args": ["-y", "mcp-remote@latest", "https://mcp.plane.so/http/mcp"]
    }
  }
}

​
Zed

  1. Press Cmd + , to open Zed settings
  2. Add the following configuration:
{
  "context_servers": {
    "plane": {
      "source": "custom",
      "command": "npx",
      "args": ["-y", "mcp-remote@latest", "https://mcp.plane.so/http/mcp"],
      "env": {}
    }
  }
}

​
Remote HTTP with PAT Token

Use this method when you need header-based authentication, such as in automated workflows or CI/CD pipelines.

​
Prerequisites

  • Node.js: Version 22 or later
  • npx: Comes bundled with npm
  • Plane API Key: Generate from your Plane workspace settings

​
Configuration

{
  "mcpServers": {
    "plane": {
      "command": "npx",
      "args": ["mcp-remote@latest", "https://mcp.plane.so/http/api-key/mcp"],
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>",
        "X-Workspace-slug": "<YOUR_WORKSPACE_SLUG>"
      }
    }
  }
}
Replace <YOUR_API_KEY> with your Plane API key and <YOUR_WORKSPACE_SLUG> with your workspace slug.

​
Local Stdio transport

Use this method to connect to a self-hosted Plane instance. The Stdio transport runs locally and communicates directly with your Plane API.

​
Prerequisites

  • Python: Version 3.10 or later
  • uvx: Comes bundled with uv
You can verify your installation by running: 
python --version
uvx --version

​
Configuration

{
  "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

VariableRequiredDescription
PLANE_API_KEYYesYour Plane API key
PLANE_WORKSPACE_SLUGYesYour workspace slug
PLANE_BASE_URLNoAPI URL for self-hosted instances (defaults to https://api.plane.so)

​
SSE transport (Legacy)

The SSE transport is maintained for backward compatibility. For new integrations, we recommend using the HTTP with OAuth transport.

​
Prerequisites

  • Node.js: Version 22 or later
  • npx: Comes bundled with npm

​
Configuration

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

​
Activating the Plane MCP Server

After setup, when activating the server with OAuth-based transports (HTTP with OAuth or SSE), you will be prompted in your browser to connect your Plane workspace to the MCP server. When prompted to authorize, click Approve. Next, choose the workspace you want to connect, review the permissions, and click Accept.

​
Troubleshooting

​
Common issues

Authentication errors If you encounter authentication issues with OAuth transports, clear saved auth tokens: 
rm -rf ~/.mcp-auth
Connection timeouts
  • Ensure you have a stable internet connection
  • Check if your firewall or proxy is blocking MCP connections
  • Verify your Plane instance is accessible
WSL on Windows If you’re using WSL on Windows and encountering errors with remote transports: 
{
  "mcpServers": {
    "plane": {
      "command": "wsl",
      "args": ["npx", "-y", "mcp-remote@latest", "https://mcp.plane.so/http/mcp"]
    }
  }
}
Node.js version Ensure you have Node.js 22 or later installed for remote transports. Python version Ensure you have Python 3.10 or later installed for the local Stdio transport.

​
Getting help

If you continue to experience issues:
  1. Verify your authentication credentials
  2. Contact support at [email protected] for Plane-specific issues
  3. Check the MCP community forums for general MCP issues

​
Congrats!

You have successfully connected your Plane workspace to the MCP server!