MCP Orchestro logo

MCP Orchestro

by khaoss85

Orchestrates AI-assisted development with task decomposition, dependency tracking, persistent knowledge, and a live Kanban dashboard.

Install MCP Orchestro

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "khaoss85-mcp-orchestro": {
      "command": "npx",
      "args": [
        "-y",
        "@khaoss85/orchestro@latest"
      ],
      "env": {
        "DATABASE_URL": "YOUR_VALUE_HERE",
        "SUPABASE_URL": "YOUR_VALUE_HERE",
        "SUPABASE_SERVICE_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @khaoss85/orchestro@latest

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

khaoss85/mcp-orchestro MCP server provides 60 MCP tools for coordinating AI-assisted software development. It connects Claude Code workflows with a Supabase-backed system for decomposing user stories, tracking tasks and dependencies, retaining patterns, and recording progress. A separate dashboard presents Kanban status, risks, dependencies, history, and rollback options. Reach for it when product and development teams need a shared view of work across Claude Code sessions.

Use cases

  • Decompose product stories into implementation tasks
  • Track dependencies across development work
  • Retain coding patterns between Claude Code sessions
  • Review project progress on a Kanban board
  • Export development history for stakeholders

Key features

  • 60 MCP tools for orchestrated development
  • User story decomposition
  • Task dependency and conflict tracking
  • Persistent patterns and knowledge
  • Real-time Kanban dashboard
  • History, rollback, and Markdown export

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

5/5 checks healthy over the last 80d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · @khaoss85/orchestro@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars16Stargazers on the source repository.
npm downloads249Package downloads in the last 30 days.
Last commit1y agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Orchestro works

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.

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.

Claude Code can be configured with the published npx command or with a local Node entry point.

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.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Orchestro

With Node.js 18 or newer, run `npx -y @khaoss85/orchestro@latest`. The manual setup uses a cloned repository, npm dependencies, Supabase migrations, and Claude Code configuration.

Yes. The README provides a Claude Desktop MCP configuration using the server command and `DATABASE_URL`.

The documented configuration uses `DATABASE_URL`, `SUPABASE_URL`, and `SUPABASE_SERVICE_KEY`. The MCP configuration specifically shows `DATABASE_URL`.

Yes. The documented setup requires a Supabase project and connection string, and applies database migrations there.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Orchestro AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/khaoss85-mcp-orchestro?style=directory)](https://allmcps.com/mcp/khaoss85-mcp-orchestro)
HTML Embed
<a href="https://allmcps.com/mcp/khaoss85-mcp-orchestro"><img src="https://allmcps.com/api/badge/khaoss85-mcp-orchestro?style=directory" alt="MCP Orchestro on AllMCPs" /></a>