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 | |
| PLANE_WORKSPACE_SLUG | Yes | Your Plane.so workspace slug |
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
Server capabilities have not been inspected yet.
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-issueC | Create a new issue in a project |
| list-issuesC | List issues from a project |
| get-issueC | Get detailed information about a specific issue |
| update-issueC | Update an existing issue in a project, delete just update the issue title with 'delete' or 'remove' |
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 6 tools
Each tool has a clearly distinct purpose with no ambiguity: create-issue, get-issue, update-issue, and list-issues handle issues, while get-project and list-projects handle projects. The descriptions reinforce this separation, making misselection unlikely.
All tools follow a consistent verb_noun pattern with hyphen separation (e.g., create-issue, list-projects). This predictable naming scheme enhances readability and usability across the tool set.
With 6 tools, the server is well-scoped for managing issues and projects in a workspace. Each tool earns its place by covering essential CRUD operations without being overly sparse or bloated.
The tool set provides strong coverage for issues (create, get, list, update) and projects (get, list), but lacks explicit create-project, update-project, and delete operations. Agents can work around this with the update-issue workaround for deletion, but minor gaps exist.