Summary

Plane stops being a tab you switch to in order to answer a question about your own work.

The daily tools are shaped for an agent rather than mirrored from the REST API: assignees change one person at a time instead of resubmitting the list, count_work_items answers "how many urgent" without fetching the items, and complete_cycle exists because Plane has no complete action of its own. The far edges of the surface — estimate points, relation definitions, property options — only matter once you are automating Plane rather than using it. If your client has a tight tool budget, take the hosted OAuth endpoint: it is the same catalogue with credentials handled on connect.

What it is

A server over the Plane work-tracking API, covering projects, work items, cycles, modules, initiatives, milestones, intake, pages, estimates and workspace configuration. The current release groups them as one tool per resource with an action parameter; the per-operation names it used to advertise, such as create_work_item and list_cycles, still resolve.

What you get

Work items created, updated, archived, searched by text and related to one another, with a single assignee or label added or removed instead of replacing the whole list
Plane Query Language filtering on work item, cycle and module listings, and get_pql_reference to return the syntax while you are composing a filter
Counts grouped by state, priority, project or type, so distribution questions are answered without pulling full work item payloads
Cycle handling shaped around Plane's own model: complete_cycle closes a cycle by setting its end date to today, and manage_cycle_archive backdates a still-active cycle before archiving it
Intake triage with the status codes Plane uses, including snoozed with a date and duplicate pointing at another work item
Custom work item types and properties created, scoped and given values, with resolve_work_item_type finding or creating a type that is usable inside a project
Attachments listed, fetched from a public URL, handed back as a presigned download link, or read into the conversation as text up to 1 MB or an image up to 5 MB

Requirements

Locally, Python 3.10 or newer plus PLANE_API_KEY and PLANE_WORKSPACE_SLUG in the client config — the key comes from Workspace Settings → API tokens — with PLANE_BASE_URL added for a self-hosted Plane. Hosted instead: https://mcp.plane.so/http/mcp handles OAuth on connect and needs no credentials in your config, or https://mcp.plane.so/http/api-key/mcp takes a personal access token plus an X-Workspace-slug header. Initiatives are a workspace feature that has to be switched on before the initiative tools answer. MIT.

Setup effort

One command plus a key — uvx plane-mcp-server stdio, then supply credentials