plane-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLANE_API_KEY | Yes | Your Plane.so API key for authentication. | |
| PLANE_WORKSPACE_SLUG | Yes | Your Plane.so workspace slug found in the URL. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-projectsA | List all projects in the workspace |
| get-projectB | Get detailed information about a specific project |
| create-projectB | Create a new project |
| update-projectC | Update a project |
| delete-projectC | Delete a project |
| list-issuesB | List all issues in a project |
| create-issueC | Create a new issue |
| get-issueB | Get an issue by its ID |
| update-issueD | Update an issue |
| delete-issueC | Delete an issue |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool clearly targets either an issue or a project with distinct actions. There is no overlap or confusion between tools.
All tools follow a consistent hyphen-separated verb-noun pattern (e.g., create-issue, delete-project), making the naming predictable and easy to parse.
10 tools provide full CRUD coverage for both issues and projects. The count is balanced and appropriate for the domain.
The toolset covers all basic lifecycle operations (create, read, update, delete, list) for both issues and projects, leaving no obvious gaps for a minimal project management server.