Plane MCP Server

# Plane MCP Server [![Trust Score](https://archestra.ai/mcp-catalog/api/badge/quality/kelvin6365/plane-mcp-server)](https://archestra.ai/mcp-catalog/k

Local serverstdioTypeScript

What is the Plane MCP server?

Plane MCP server exists for a simple reason — assistants are far more useful when they can act on Plane directly instead of describing what you should do. # Plane MCP Server Trust Score [![smithery.

What you get

  • List all projects in your Plane workspace
  • Get detailed information about specific projects
  • Create new issues with customizable properties
  • List and filter issues from projects
  • Get detailed information about specific issues
  • Update existing issues with new information

What the assistant can call

Once Plane is connected, these are the calls the assistant has available:

  • macOS — ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows — %APPDATA%\Claude\claude_desktop_config.json

Configuration and credentials

You will need 3 environment variables: PLANE_API_KEY, PLANE_WORKSPACE_SLUG, PLANE_HOST. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Node.js 22.x or higher - A Plane.so API key - A Plane.so workspace

Setting it up

@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Plane's toolset — macOS, Windows — is a fair guide to whether it matches your workflow. It is maintained by kelvin6365; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the plane mcp server does with a few real requests.

Available tools

ToolWhat it does
macOS~/Library/Application Support/Claude/claude_desktop_config.json
Windows%APPDATA%\Claude\claude_desktop_config.json

How to install the Plane MCP server

{
  "mcpServers": {
    "plane-mcp-server-kelvin6365": {
      "command": "npx",
      "args": ["-y", "@smithery/cli"],
      "env": {
        "PLANE_API_KEY": "your-value",
        "PLANE_WORKSPACE_SLUG": "your-value",
        "PLANE_HOST": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Node.js 22.x or higher - A Plane.so API key - A Plane.so workspace
VariableDescriptionRequired
PLANE_API_KEYCredential the server authenticates with.Yes
PLANE_WORKSPACE_SLUGConfiguration value read at startup.Optional
PLANE_HOSTEndpoint or connection string the server talks to.Optional

Example prompts to try

  • Use Plane to macOS.
  • Use Plane to Windows.

Frequently asked questions

Node.js 22.x or higher, a Plane.so API key, and a Plane.so workspace are required.