agent-control-plane-mcp
Integrates with Coder to manage agent workspaces for Plane work items: starts workspaces for ready items, names them and configures branches/prompts, links them back to Plane, and stops them when items are merged or cancelled.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
agent_control_plane
Syncs Plane work items with Coder agent workspaces: starts a workspace for each ready item, writes the link back, stops it once the item is closed, and serves the agent's Plane tools over MCP. It is the only service holding a Plane API key.
Sync
Every 30 s it reads the project's work items and:
starts a workspace for each item in Todo carrying an
Agentlabel (Claude CodeorOpenCode) whose blockers are all Merged, lowest number first, while fewer thanMAX_RUNNING_WORKSPACESworkspaces run;names it
lyre-<n>, on branchlyre-<n>-<title slug>, with the item'sRepositorylabels (else its nearest ancestor's) and a prompt built for the item's scope (ResearchandSpecitems open no pull requests);adds a "Coder workspace" link on the item and moves it to In Progress;
moves an item from Waiting back to In Progress on the first comment not posted by this service after a question;
stops the workspace of an item moved to Merged or Cancelled, or deleted. Finished keeps it running for review feedback.
States and labels are found by the external_id Plane provisioning stamps
on them (todo, waiting, agent/claude_code, scope/spec, …), never by
name.
Related MCP server: Plane MCP Server
MCP tools
Workspaces reach
http://agent-control-plane-mcp.coder.svc.cluster.local/mcp (port 4331):
get_work_item {}returns the item as Markdown: description, parents with their comments, children, blockers and comments.add_comment { body }posts Markdown on the item.finish_work_item { summary }posts the summary and moves the item to Finished.
The caller is identified as in the gatekeeper: the running pod whose IP is
the TCP peer in WORKSPACES_NAMESPACE. A workspace not started from a work
item gets a plain answer saying so.
Internal API
On http://agent-control-plane.coder.svc.cluster.local (port 4332), reached
only by the gatekeeper's pods and the dashboard namespace:
Request | Answer |
| Comment on the item, state Waiting; |
|
|
|
|
|
|
Links and questions live in SQLite at DATABASE_PATH.
Develop
nix develop gives bun and node; Coder agent workspaces load the same
shell, as .#agent, on start.
bun install
bun run start
bun run checkbun run start runs node src/main.ts (Node strips the types, there is no
build). Without PLANE_URL the sync loop stays off and only the HTTP servers
run.
Build and push
A push to main runs .github/workflows/image-to-registry.yaml, which
pushes lyre/agent_control_plane:latest-amd64 and latest-arm64 to the
S3-backed registry. It needs an environment release holding
DOCKER_IMAGE_REGISTRY_BUCKET_REGION, DOCKER_IMAGE_REGISTRY_BUCKET_NAME,
DOCKER_IMAGE_REGISTRY_BUCKET_ACCESS_KEY_ID and
DOCKER_IMAGE_REGISTRY_BUCKET_ACCESS_KEY_SECRET, the gatekeeper's values.
By hand, from the lyre devShell, with the local registry proxy running:
cargo make registry-image
kubectl -n coder rollout restart deployment agent-control-planeEnvironment
Variable | Value |
| Port serving only |
| Port of the internal API, |
| SQLite file, on the data volume |
| Namespace of the workspace pods allowed on |
| In-cluster Plane URL; empty disables the sync |
| Plane URL used in links |
| Plane workspace, |
| Plane project, |
| Plane admin the API key is minted for |
| Its password |
| In-cluster Coder URL |
| Coder URL used in the workspace link |
| Template workspaces are created from, |
| Coder admin, from Coder's admin Secret |
| Its password, from the same Secret |
| JSON map of |
| Running workspaces above which none starts, |
| The ServiceAccount |
The Terraform module in .terraform-module/ sets all of them.
Traps
The Plane API key is re-minted on every start: the previous key labelled
agent-control-planeis revoked first.Workspaces are owned by Coder's
admin. Signed in to Coder as another user, they stay hidden unless that user is an owner.Plane allows 60 API requests a minute per instance, shared by the sync and the agents' tool calls. A
429skips the tick; raiseAPI_KEY_RATE_LIMITon Plane's API if it happens often.
License
MIT, see LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Start TODOs, send follow-ups and read agent results in your TODO for AI workspace.
1Your team's stories, acceptance criteria, designs and docs, for coding agents. Sign in with OAuth.
Agent-complete, permission-scoped product operations for Priorify workspaces.
Shared control plane for AI coding agents — tasks, memory, decisions, file locks. 12 tools.
Related MCP Servers
- AlicenseBqualityCmaintenanceConnect Claude to your Plane workspace to manage projects, work items, cycles, modules, and more directly from Claude.78115 npm4MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Plane project management APIs, offering tools for managing projects, work items, cycles, modules, initiatives, and more through MCP.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI models to interact with a self-hosted Plane workspace through MCP tools, supporting task, project, cycle, and module management.-
- FlicenseNot gradedqualityBmaintenanceEnables an LLM to act as a project manager across self-hosted Plane workspaces and projects, providing tools for work items, cycles, modules, states, labels, comments, members, and intake triage via Plane's REST API.-