MCP Orchestro MCP Server

Your AI Development Conductor - Intelligent task management for Claude Code

Local serverstdioTypeScript

What is the MCP Orchestro MCP server?

Your AI Development Conductor - Intelligent task management for Claude Code. The mcp orchestro mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

Transform product ideas into reality with an intelligent orchestration system that bridges Product Managers, Developers, and AI. Orchestro conducts the entire development symphony: task decomposition, dependency tracking, pattern learning, and real-time progress visualization.

Its toolset

Everything the assistant can do here goes through one of these:

  • get_project_info — Project metadata and status
  • get_project_configuration — Complete project configuration
  • initialize_project_configuration — Setup default tools and guardians
  • create_task — Create with assignee, priority, tags, category
  • list_tasks — Filter by status/category/tags
  • update_task — Modify any field with validation
  • delete_task — Safe deletion with dependency checks
  • get_task_context — Full context with dependencies (deprecated, use prepare_task_for_execution)
  • get_execution_order — Topological sort by dependencies
  • safe_delete_tasks_by_status — Bulk delete with safety checks
  • prepare_task_for_execution — Generate codebase analysis prompt
  • save_task_analysis — Store analysis results

Configuration

You will need 4 environment variables: DATABASE_URL, SUPABASE_URL, SUPABASE_SERVICE_KEY, ANTHROPIC_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

The server ships on npm as @khaoss85/orchestro, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

When to reach for it

Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Orchestro's toolset — get_project_info, get_project_configuration, initialize_project_configuration and 11 more — is a fair guide to whether it matches your workflow. It is maintained by khaoss85; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against MCP Orchestro's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP Orchestro.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp orchestro mcp server does with a few real requests.

Available tools

ToolWhat it does
get_project_infoProject metadata and status
get_project_configurationComplete project configuration
initialize_project_configurationSetup default tools and guardians
create_taskCreate with assignee, priority, tags, category
list_tasksFilter by status/category/tags
update_taskModify any field with validation
delete_taskSafe deletion with dependency checks
get_task_contextFull context with dependencies (deprecated, use prepare_task_for_execution)
get_execution_orderTopological sort by dependencies
safe_delete_tasks_by_statusBulk delete with safety checks
prepare_task_for_executionGenerate codebase analysis prompt
save_task_analysisStore analysis results
get_execution_promptEnriched implementation context
decompose_storyAI-powered story → tasks decomposition with automatic analysis (autoAnalyze=true default)

How to install the MCP Orchestro MCP server

**Or add to Claude Code config**:
```json
{
  "mcpServers": {
    "orchestro": {
      "command": "npx",
      "args": ["-y", "@khaoss85/orchestro@latest"],
      "env": {
        "DATABASE_URL": "your-supabase-connection-string"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
DATABASE_URLEndpoint or connection string the server talks to.Yes
SUPABASE_URLEndpoint or connection string the server talks to.Yes
SUPABASE_SERVICE_KEYCredential the server authenticates with.Yes
ANTHROPIC_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP Orchestro to get project info.
  • Use MCP Orchestro to get project configuration.
  • Use MCP Orchestro to initialize project configuration.

Frequently asked questions

It connects MCP Orchestro to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (get_project_info, get_project_configuration, initialize_project_configuration, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Orchestro directly.