TL;DR
I rebuilt my workflow again (third AI-based project). Orchestro is an open-source MCP server + web dashboard for Claude Code.
Think Trello for Claude Code — but with a (auto) Scrum Master that keeps the board honest and agents that move the cards from goal → tasks → code.
Looking for real users (heavy Claude Code folks) to kick the tires.• Website: orchestro.org
• Repo: github.com/khaoss85/mcp-orchestro
The itch
Great agent UX, still the same frictions:
- intent and decisions buried in prompts
- dependencies invisible until too late
- goal → tasks → code drops context during vibe coding
- PMs and devs don’t see the same reality in real time
I wanted a thin, no-drama layer that keeps the plan visible and the execution honest.
What it is (one line)
Orchestro = Trello for Claude Code.
Plan on a board. The MCP server executes the plan. The (auto) Scrum Master keeps flow tight. Agents move cards as work happens.
How it feels to use
You write a user story.
The built-in Scrum Master decomposes it into technical tasks, sets dependencies, and guards the workflow.
Agents prepare context-rich prompts for Claude Code, nudge the right tools, and move cards across the board as things progress.
You and your PM both watch the same board update in real time.
Less prompt soup, more visible, auditable progress.
What you get after install
- A live Kanban that actually mirrors what Claude is doing
- ~60 tools available inside Claude Code (ask: “Show me orchestro tools”)
- A clean goal → tasks → deps → code path you can point stakeholders to
Quick start (one command)
npx @orchestro/init
npm run dashboard # http://localhost:3000
(restart Claude Code, then ask: "Show me orchestro tools")
That’s it. You’ll see the tools in Claude, and a live board in the browser.
Who this is for
- heavy Claude Code users who want fewer invisible steps
- builders doing vibe coding but needing a clean map
- teams that want the PM and Dev view to finally be the same thing
Local-first & trust
Your data lives in your Supabase. No hardcoded secrets. Full history if you need to audit or roll back.
Why open-source (and my first MCP)
I shipped my first MCP here because I want real usage, not another demo.
If you live in Claude Code daily, your feedback will shape the next iteration.
Kick the tires
Repo & docs: github.com/khaoss85/mcp-orchestro
Website: orchestro.org
If it helps, drop a star.
If it hurts, open an issue and tell me where.
PRs and brutal feedback welcome.
Top comments (0)