PlanWright
tools.planwrightPublished by planwright.toolsOfficial publisherv1.0.2Updated Oct 24, 2026
Control plane for autonomous software labor. Agents claim objectives over MCP with audit trail.
Overview
Planwright is a hosted planning board where humans set objectives and coding agents claim, plan, execute and report work over MCP with a signed audit trail.
- What you can do
- Set up the session: choose the active repo or project, list workspaces and projects, and read, push or list context files such as CLAUDE.md and specs.
- Manage initiatives: list, create, update and delete milestones for the workspace.
- Manage objectives: list by lane, read details with run history, create with acceptance criteria, update and schedule.
- Run agent workflow: claim objectives, post plans, check alignment, record diffs and test runs, request acceptance, add notes and flag clarity concerns.
- Review enrichment: list unenriched or unclassified objectives and list project bugs.
- When to use it
- Useful when you want coding agents such as Claude Code, Cursor or Codex to pick up work from a shared objective board rather than ad-hoc prompts, and you need a reviewable record of what each agent planned, changed and tested.
- Requirements
- A remote Streamable HTTP endpoint at mcp.planwright.tools; no self-hosting or local package. OAuth 2.1 with dynamic client registration, with a browser GitHub login on first connection; a static token from Settings for CI/CD or headless use. A GitHub-linked project.
Installation
In SourceWeft
- Open PlanWright in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/tools.planwright%2Fplanwright/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"planwright": {
"type": "http",
"url": "https://mcp.planwright.tools/mcp"
}
}
}README
Planwright
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.
Quick Start
Claude Code (recommended)
Your browser opens for GitHub login. That's it.
Other Agents
See the full agent setup guides for Cursor, Codex, Claude Desktop, and generic MCP clients.
How It Works
Key Features
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.
Documentation
Examples
See the examples/ directory for:
- Sample
CLAUDE.mdfiles for different project types - Example objective structures
- Context file templates
MCP Server
Planwright's MCP server is hosted and managed—no self-hosting required.
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.
Available Tools
Planwright exposes 30 MCP tools for agent orchestration:
Setup & Context
Initiatives
Objectives
Agent Workflow
Enrichment & Classification
Support
License
Planwright is a commercial product. The MCP integration examples in this repository are provided under the MIT License.
See LICENSE for details.
Source: README.md at commit a7b1106
Tools
0Version history
1- v1.0.2LatestSep 16, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.