plane-mcp-server
I use Plane for project management. Built this so the team and I could manage it from Claude Desktop instead of clicking through the UI. Create work items, manage cycles, update projects, run bulk ops — from Claude Code or Desktop. Works with any self-hosted Plane instance.
We run delivery on Plane rather than JIRA. It is a good tool, but the day-to-day of project management is a lot of clicking — open the cycle, find the work item, change the state, write the update, repeat across twenty engagements.
So I built an MCP server for it. Now the team and I manage Plane from Claude Desktop and Claude Code: create work items, manage cycles, update projects, run bulk operations. It works against any self-hosted Plane instance.
Why it matters
The interesting part isn’t the tool, it’s what it changes about the work. Once project state is reachable from the same place you’re already thinking, the overhead of keeping a board accurate drops close to zero — and a board that is cheap to keep accurate is a board people actually trust.
That’s the same argument I make to clients about AI in delivery: the win isn’t that the model writes your status report, it’s that the cost of good hygiene falls far enough that the team stops skipping it.