A Model Context Protocol (MCP) server that enables LLMs to interact with Plane.so, allowing them to manage projects and issues through Plane's API. Using this server, LLMs like Claude can directly…
Plane Mcp Server is an MCP project maintained in the disrex-group/plane-mcp-server repository. The maintainer describes its purpose as “A Model Context Protocol (MCP) server that enables LLMs to interact with Plane.so, allowing them to manage projects and issues through Plane's API. Using this…”. Read the project documentation for the complete scope.
The documented npm package is @disrex/plane-mcp-server. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.
The example declares PLANE_API_KEY, PLANE_WORKSPACE_SLUG. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.
Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| per_page | optional): Number of items per page (default: 100, max: 100) |
| cursor | optional): Pagination cursor in format 'value:offset:is_prev' |
| project_id | ID of the project |
| description_html | HTML description of the sub-issue (optional) |
| priority | Priority of the sub-issue (urgent, high, medium, low, none) (optional) |
| state_id | ID of the state for this sub-issue (optional) |
| assignees | Array of user IDs to assign to this sub-issue (optional) |
| labels | optional): Updated array of label IDs to assign to this issue |
| assignee_id | optional): Filter by assignee ID |
| issue_id | ID of the sub-issue to convert to regular issue |
| group | optional): Updated state group |
| color | optional): Updated color code for the label (e.g., "ff0000") |
| module_id | ID of the module to remove issue from |
| start_date | optional): Updated start date of the cycle (YYYY-MM-DD format) |
| target_date | optional): Updated target end date of the module |
| status | optional): Updated status of the module |
| lead | optional): Updated user ID of the module lead |
| members | optional): Updated array of user IDs for module members |
| issues | Array of issue IDs to add to the cycle |
| cycle_id | ID of the source cycle to transfer issues from |
| owned_by | ID of the user who will own this cycle |
| end_date | optional): Updated end date of the cycle (YYYY-MM-DD format) |
| label_id | ID of the label to delete |
| comment_id | ID of the comment to delete |
| comment | The updated comment text |
| link_id | ID of the link to delete |
| title | optional): Updated title/name for the link |
| url | optional): Updated URL |
| file_name | Name of the file to upload |
| file_size | Size of the file in bytes |
| content_type | MIME type of the file (e.g., 'image/png', 'application/pdf') |
| activity_id | ID of the activity to retrieve |
| duration | optional): Updated time logged in hours |
| worklog_id | ID of the worklog to delete |
| type_id | ID of the issue type |
| property_id | ID of the property |
| display_name | Display name for the property (optional) |
| property_type | Type of property (TEXT, NUMBER, DATE, OPTION, MULTI_OPTION, BOOLEAN) |
| is_required | Whether this property is required (optional) |
| is_multi | Whether multiple values are allowed (optional) |
| sort_order | Sort order for the option (optional) |
| is_default | Whether this is the default option (optional) |
| option_id | ID of the option to update |
| parent_issue_id | ID of the parent issue |
| new_cycle_id | ID of the target cycle to transfer issues to |
{
"mcpServers": {
"plane": {
"command": "npx",
"args": [
"-y",
"@disrex/plane-mcp-server"
],
"env": {
"PLANE_API_KEY": "YOUR_PLANE_API_KEY",
"PLANE_WORKSPACE_SLUG": "your_workspace_slug_here"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| PLANE_API_KEY | Declared in the maintainer’s client configuration. | Check documentation |
| PLANE_WORKSPACE_SLUG | Declared in the maintainer’s client configuration. | Check documentation |
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.