MCP Orchestro

What khaoss85/mcp-orchestro MCP server does

khaoss85/mcp-orchestro MCP server coordinates development work from product requirements through implementation. Product managers can submit user stories for technical task breakdown, while developers and Claude Code can inspect task context, dependencies, risks, and suggested implementation details. The system also keeps patterns, templates, and learnings so information can persist between sessions.

The project is designed for teams that want a single development record rather than separate notes across product and coding workflows. Its interface includes a visual Kanban board, progress tracking, dependency views, an event history, and Markdown export. The README also describes rollback support for undoing mistakes.

How it works

A typical workflow starts with a product story. Orchestro analyzes the story and creates related technical tasks, including their dependency relationships. Developers or Claude Code then work through a structured sequence described as prepare, analyze, implement, and learn. During that process, the system can analyze a codebase, identify patterns, track task status, and flag possible conflicts when tasks affect the same files.

The MCP layer exposes the orchestration functions to Claude Code as 60 tools. A dashboard runs separately and displays updates in real time through Socket.io. Supabase provides the project database and stores the information needed for tasks, code entities, events, metadata, and learned patterns.

Setup and configuration

To run khaoss85/mcp-orchestro MCP server from the published package, use Node.js 18 or newer and run npx -y @khaoss85/orchestro@latest. The documented configuration supplies DATABASE_URL to the MCP process. A manual installation can instead clone the repository, install npm dependencies, and run the migration script against a Supabase transaction-mode connection string.

The documented environment configuration also includes SUPABASE_URL and SUPABASE_SERVICE_KEY. The service key is intended for administrative operations and should remain secret. The README describes an interactive setup command, an automatic Claude configuration command, and a dashboard command that opens the local dashboard at http://localhost:3000.

Claude Code can be configured with the published npx command or with a local Node entry point. The README also shows a Claude Desktop configuration path and provides Claude Code plugin and project-addition options.

Tools and capabilities

The documented capabilities include:

• Decompose user stories into technical tasks.
• Track task dependencies and display dependency graphs.
• Analyze a codebase and provide implementation context.
• Retain templates, patterns, and learnings between sessions.
• Detect potential file conflicts between tasks.
• Show Kanban progress and real-time dashboard updates.
• Record decisions and changes in a history timeline.
• Export project information as Markdown reports.
• Roll back changes described by the project workflow.

Limitations and notes

The provided material does not list the individual names or schemas of all 60 MCP tools, so tool-level behavior should be verified in the project documentation or after installation. A Supabase project and database configuration are required for the documented setup; the README says the Supabase free tier can be used. The dashboard and MCP process are presented as separate setup concerns, and the excerpt does not specify deployment instructions for hosting the dashboard remotely.