@project-orchestrate/mcp
v0.4.1
Published
MCP server and hook helper that give Claude Code, Codex and OpenCode sessions the Project Orchestrate tools.
Maintainers
Readme
@project-orchestrate/mcp
The agent-facing side of Project Orchestrate, a local-first project control tool for agent-heavy software development. It lets Claude Code, Codex and OpenCode sessions read and change a project's tickets, documents and session records under the same validation the desktop app uses.
What it installs
Three commands:
orchestrate-mcpis a Model Context Protocol server over stdio with eight tools:create_ticket,update_ticket,describe_schema,query_tickets,read_document,log_session,set_active_ticketandsearch.orchestrate-agentis the headless helper that agent hooks call: the orientation digest at session start, the guard that stops direct edits to ticket files, presence heartbeats, the session-record check at stop, and the planning subcommands the agent commands use.orchestrate-hostis the request handler the desktop app spawns. Agents do not call it.
Requirements
Node 22 or newer, and a repository that already has a .orchestrate/ directory.
Configuration
Point an agent at the server through its MCP configuration, for example a Claude Code .mcp.json:
{
"mcpServers": {
"orchestrate": {
"command": "npx",
"args": ["-y", "-p", "@project-orchestrate/mcp", "orchestrate-mcp"],
"env": { "ORCHESTRATE_ROOT": ".", "ORCHESTRATE_ACTOR": "claude" }
}
}
}ORCHESTRATE_ROOTis the repository root holding.orchestrate/. It defaults to the working directory.ORCHESTRATE_ACTORis the actor id from the project'sactors.yamlthat the session acts as. When it is unset, the server acts as the first actor ofkind: agentin that file.
The desktop app installs this configuration, the hooks and the agent commands for you when you onboard a repository.
Licence
AGPL-3.0-only. This is a derived work; NOTICE carries the attribution. The TypeScript source ships in src/ alongside the compiled dist/.
