Plane MCP Server
Plane.so projects and issues management for LLM-based project workflows.
Data last scanned 2 days ago · Reviewed 2 days ago
Overview
The Plane MCP Server provides a bridge between AI models and Plane.so, allowing users to automate task management directly from their LLM interface. It supports core operations including listing workspaces, managing project details, and creating or updating project issues with customizable properties. Designed for integration with platforms like Claude for Desktop, the server requires a Plane API key and workspace slug for authentication. It functions by translating natural language requests into API calls, enabling LLMs to interact with your specific Plane workspace environment.
Our verdict
With a security score of 34/100, this tool carries a high risk level for users. This rating stems from the fact that it is community-maintained rather than official, and lacks independent editorial review for its authentication and read-only implementations. Due to these factors, users should exercise caution and avoid using this server in environments where project management data sensitivity is a primary concern.
- Supports direct creation and updating of project issues
- Uses only two direct dependencies for lower supply-chain risk
- MIT licensed for open-source flexibility
- Community-maintained without official vendor support
- Not yet undergone formal editorial security review
- Last code update occurred over 200 days ago
Setup
{
"mcpServers": {
"plane-mcp-server": {
"args": [
"-y",
"plane-mcp-server"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Tools
| Tool | Description | Risk |
|---|---|---|
| list-projects | Lists all projects in your Plane workspace. | low |
| get-project | Gets detailed information about a specific project. | low |
| create-issue | Creates a new issue in a specified project. | medium |
| list-issues | Lists issues from a specified project with optional filtering. | low |
| get-issue | Gets detailed information about a specific issue. | low |
| update-issue | Updates an existing issue in a project. | medium |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›What are the prerequisites for running the Plane MCP server?
You must have Node.js 22.x or higher, a valid Plane.so API key, and your Plane.so workspace.
›Can I use this server with platforms other than Claude for Desktop?
Yes, you can use the Smithery CLI to install the server for supported clients including Cline, Windsurf, Roo-Cline, Witsy, Enconvo, and Cursor.
›Is the PLANE_HOST environment variable mandatory?
No, the PLANE_HOST environment variable is optional.
›How should I provide the assignees parameter when creating an issue?
The assignees parameter must be an array of user ID strings; providing a dictionary or object instead can cause errors.
›Are there specific formatting requirements for issue descriptions?
Yes, the Plane API requires that the description be provided in HTML format using the description_html field.
›Does the server use underscores or hyphens for tool names?
While the API may use different formats, the server tools are accessed using hyphens, such as list-projects.
Alternatives
Badge
Maintain this server? Add the live badge to your README.