Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Planwright add objective: implement OAuth login"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Control plane for autonomous software labor.
Planwright is the objective-native planning board for agent-led software development. Humans define outcomes at the Objective layer; coding agents (Claude Code, Cursor, Codex, and others) claim work, decompose tasks, execute, and report back via native MCP—with every state change captured in a hash-chained, Ed25519-signed audit trail.
claude mcp add planwright https://mcp.planwright.tools/mcpYour browser opens for GitHub login. That's it.
See the full agent setup guides for Cursor, Codex, Claude Desktop, and generic MCP clients.
Related MCP server: agent-orchestrator
┌─────────────────────────────────────────────────────────────────┐
│ │
│ PLANNING (Humans) EXECUTION (Agents) │
│ │
│ "Add OAuth login" ───────┐ │
│ │ │
│ create_objective() ──────┤ │
│ ▼ │
│ ┌──────────────┐ │
│ │ BACKLOG │ │
│ └──────┬───────┘ │
│ │ │
│ schedule_objective() ────┤ │
│ ▼ │
│ ┌──────────────┐ │
│ │ SCHEDULED │◀── list_objectives() │
│ └──────┬───────┘ │
│ │ │
│ │── claim_objective() ──────────────▶│
│ ▼ │
│ ┌──────────────┐ │
│ │ IN PROGRESS │◀── append_plan() │
│ │ │◀── record_diff() │
│ └──────┬───────┘ │
│ │ │
│ │── request_acceptance() ───────────▶│
│ ▼ │
│ ┌──────────────┐ │
│ │ ACCEPTANCE │ │
│ └──────┬───────┘ │
│ │ │
│ Human reviews ───────────┤ │
│ (web UI) │ │
│ ┌──────┴───────┐ │
│ │ DONE │ │
│ └──────────────┘ │
│ │
│ Every step: hash-chained + Ed25519 signed audit trail │
│ │
└─────────────────────────────────────────────────────────────────┘Objective-Native, Not Task-Based No story points. No velocity charts. No capacity planning. Agents decompose objectives into tasks themselves—you manage outcomes, not effort.
Immutable Audit Trail Every state change produces a hash-chained, Ed25519-signed audit record. Know exactly what the agent planned, what it changed, and when.
Native MCP Integration Agents connect via the Model Context Protocol—no custom API clients needed. Works with any MCP-compatible agent.
Multi-Agent Support Claude Code, Cursor, Codex, Factory, Amp—if it speaks MCP, it can work from your Planwright board.
Context Files Push CLAUDE.md, architecture docs, and specs to Planwright. Agents read them before starting work.
See the examples/ directory for:
Sample CLAUDE.md files for different project types
Example objective structures
Context file templates
Planwright's MCP server is hosted and managed—no self-hosting required.
Endpoint | Protocol |
| Streamable HTTP |
Authentication is handled via OAuth 2.1 with Dynamic Client Registration (RFC 7591). Your agent opens a browser for GitHub login on first connection.
For CI/CD and headless environments, generate a static token in Settings → MCP Tokens.
Planwright exposes 30 MCP tools for agent orchestration:
Tool | Description |
| Set active project for the session (by GitHub repo or project ID) |
| List workspaces you have access to |
| List projects with IDs and linked GitHub repos |
| List CLAUDE.md, specs, architecture docs for the project |
| Read a specific context file |
| Upload or update a context file |
| Get pending documentation gap suggestions |
| Dismiss a doc suggestion |
| Get the Planwright board URL |
Tool | Description |
| List initiatives (milestones) for the workspace |
| Create a new initiative |
| Update initiative metadata |
| Delete an initiative |
Tool | Description |
| List objectives by lane (backlog, scheduled, in_progress, acceptance, done) |
| Get full objective details including agent run history |
| Create a new objective with acceptance criteria |
| Update objective metadata |
| Move objective from backlog to scheduled |
Tool | Description |
| Claim a scheduled objective and start an agent run |
| Post the agent's decomposition plan |
| Verify work aligns with claimed objective (drift detection) |
| Record diff summary and test results |
| Submit acceptance criteria verification results |
| Move objective to acceptance lane for human review |
| Record task completion in the agent run log |
| Flag objective as having clarity concerns |
| Human override for clarity flags |
Tool | Description |
| List objectives/initiatives missing intent summaries |
| List objectives missing strategic classification |
| List bugs for this project |
Planwright is a commercial product. The MCP integration examples in this repository are provided under the MIT License.
See LICENSE for details.
This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Coordinate multiple AI agents over MCP: atomic claims, leases, shared ledger, handoffs, tasks.
Cross-agent artifact workspace with provenance across Claude Code, Codex, Cursor, LangGraph.
A paid remote MCP for OpenAI Codex agent coordination MCP, built to return verdicts, receipts, usage
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Planwright/planwright'
If you have feedback or need assistance with the MCP directory API, please join our Discord server