Plane Workflow MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLANE_URL | Yes | Your Plane URL (including self-hosted Plane instances) | |
| PLANE_API_KEY | Yes | Your Plane API key | |
| PLANE_WORKSPACE | Yes | Your Plane workspace |
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_plane_workflow_setup_statusA | Check whether Plane Workflow is configured, without contacting Plane or revealing credentials. |
| list_configured_plane_workspacesA | List locally configured Plane workspaces and the project selected in each, without contacting Plane. |
| activate_plane_workspaceA | Switch to a configured Plane workspace profile without contacting Plane or exposing its API key. |
| get_active_plane_contextA | Show the active Plane workspace and project without exposing credentials or changing Plane. |
| list_plane_projectsA | List projects in the active Plane workspace so one can be selected without changing Plane. |
| activate_plane_projectB | Validate and select a project in the active stored workspace for future work-item operations. |
| get_project_workflow_contextB | Read a project's identifiers, active profile, modules, labels, and work-item count without changing Plane. |
| get_project_workflow_profileB | Read the merged workflow profile for a Plane project without changing Plane or local profile files. |
| get_workflow_optionsB | List the available state, cycle, assignee, and estimate choices for a project without changing Plane. |
| diagnose_plane_connectionA | Check local Plane configuration and, when given a project, read the available API capabilities without changing Plane. |
| validate_workflow_profileB | Validate a reusable workflow-profile override and return a representative title preview without saving it. |
| save_project_workflow_profileB | Preview or save a project-bound workflow-profile override locally. Set confirm=true to write the profile file. |
| create_standardization_planB | Create and save a read-only cleanup proposal. The plan does not change Plane until apply_standardization_plan is confirmed. |
| get_standardization_planB | Read a saved standardization plan without changing Plane. |
| apply_standardization_planA | Preview or apply a saved standardization plan. Set confirm=true only after reviewing its proposed actions. |
| find_duplicate_candidatesC | Find potentially duplicate Plane work items by title similarity without changing Plane. |
| find_work_itemsB | Find Plane work items by their title, UUID, or project reference such as PROJECT-12 without changing Plane. |
| list_work_itemsC | List project work items with cross-edition local filters and bounded pagination. |
| get_project_briefingB | Summarize project execution and identify overdue, stale, unassigned, and unplanned active work. |
| get_work_item_relationsA | Read one work item's dependency, duplicate, schedule, and related-work relationships. |
| add_work_item_relationA | Preview or create same-project work-item relations. Set confirm=true after reviewing the relation direction. |
| add_work_item_evidence_linksB | Preview or attach validated evidence links to one work item. Set confirm=true to create the links. |
| upload_work_item_attachmentB | Preview or upload one local file as a Plane attachment. Set confirm=true to upload the file. |
| create_standard_work_itemB | Create a structured Plane work item with labels, duplicate review, optional module/cycle assignment, and planning fields. Retrying a create with the same idempotency_key (or, without one, the same title) returns the item the first attempt made instead of creating a second one. Use distinct idempotency_keys with allow_duplicate=true to create intentionally separate items that share a title. |
| start_standard_work_itemB | Preview or start planned work using the project's configured started state and the actual start date. |
| complete_standard_work_itemC | Preview or complete started work after recording a factual, human-readable completion comment. |
| cancel_standard_work_itemB | Preview or cancel unfinished work after recording a factual reason and optional follow-ups. |
| update_standard_work_itemC | Preview or update a specific Plane work item while preserving labels and description unless a structured replacement is requested. |
| ensure_moduleC | Preview or find an existing module, then explicitly create or assign it when requested. |
| audit_work_itemsB | Audit Plane work items without changing them. Reports structural and quality gaps for a human-approved cleanup. |
| export_work_items_reportB | Export filtered Plane work items as a dynamic Word or PDF report without changing Plane. Example filters: {"state_names": ["Backlog", "In Progress"]}. Example layout: {"group_by": "state", "columns": ["identifier", "title", "state", "priority"]}. |
| plan_git_backfillA | Read local git history and propose Plane work items for it, without changing Plane. Commits are grouped by module_map path prefix (for example {"apps/web/": "Web"}), then by conventional-commit scope, then by top-level folder, and split when work pauses longer than max_gap_days. Start and target dates come from the commit dates, moved onto the project's business days. Review the items with the user, then call apply_git_backfill with the returned plan_id. |
| apply_git_backfillA | Preview or apply a saved git backfill plan: create, start, and complete each item with a commit-citing record. titles and modules override proposed values by item id; skip leaves items out. Committed work is completed with a comment listing its commits; uncommitted work is only started. Every step is idempotent, so re-running after an error resumes without duplicates. Plane sets completed_at to the time of this call; the real dates are kept in start_date, target_date, and the comment. |
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 33 tools
The core workflow actions (create/start/complete/cancel/update work items) and the git-backfill, reporting, relation, evidence, and attachment tools are clearly distinct. Several read-only status/context tools overlap around workspace, project, profile, setup, and diagnostic information, so an agent may need to inspect descriptions carefully to choose the right getter.
Tool names consistently use snake_case with a verb-first pattern such as get_, list_, create_, apply_, validate_, and add_. The few longer names remain predictable and readable, with no significant mixing of naming conventions.
At 33 tools, the set is heavy for a single MCP server even though the domain is broad. Many setup/status/profile helpers could likely be consolidated or grouped, making discovery and selection more burdensome than necessary.
The server covers workspace/project activation, workflow profiles, standardization planning, work-item lifecycle operations, relations, evidence links, attachments, reporting, auditing, and git backfill. Minor gaps remain around deletion/detachment operations and standalone comment management, but core workflows are well covered.