Plane

Allows LLMs to manage Plane projects and issues via MCP with a local stdio runtime

javascript

37

GitHub Stars

javascript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "kelvin6365-plane-mcp-server": {
      "command": "node",
      "args": [
        "path/to/plane-mcp-server/build/index.js"
      ],
      "env": {
        "PLANE_HOST": "OPTIONAL_HOST",
        "PLANE_API_KEY": "YOUR_PLANE_API_KEY",
        "PLANE_WORKSPACE_SLUG": "YOUR_WORKSPACE_SLUG"
      }
    }
  }
}

You can use the Plane MCP Server to let LLMs safely interact with Plane.so, enabling workflows that create, list, and update projects and issues through Plane’s API while keeping you in control of permissions and security.

How to use

You interact with Plane through an MCP client. Run the Plane MCP Server locally or remotely, then configure your MCP client to connect via the provided runtime setup. Once connected, you can ask the MCP-enabled assistant to list all projects, examine project details, create new issues with customized properties, filter and list issues, get detailed issue information, and update existing issues. The server handles API calls to Plane and returns structured results that your client can present in your UI or chat flow. Always approve operations that modify data, and supply your Plane API key and workspace context where required.

How to install

Follow these concrete steps to install the Plane MCP Server and prepare it for use with your MCP client.

Additional setup and notes

Prerequisites ensure the MCP server can communicate with Plane. You need Node.js 22.x or higher, a Plane.so API key, and access to a Plane workspace. When you run the server, you may need to set environment variables for authentication and routing. The server supports both local runtime (stdio) and remote configuration (http) methods depending on how you choose to deploy and connect.

Security considerations

Handle your Plane API keys with care. Use secure environment variables, restrict permissions to required planes/workspaces, and require explicit user approval for any operation that changes data.

Available tools

list-projects

Lists all projects in your Plane workspace.

get-project

Gets detailed information about a specific project by its ID.

create-issue

Creates a new issue within a specified project with customizable fields.

list-issues

Lists issues from a project with optional filters such as state, priority, or assignee.

get-issue

Retrieves detailed information about a specific issue.

update-issue

Updates an existing issue in a project with new values like title, description, priority, and assignees.