I built Orchestro, an open-source MCP server + web dashboard for Claude Code. The short version:
“Trello for Claude Code” — with a built-in “scrum master” that keeps the board honest and agents that move cards from goal → tasks → code as work happens. Why - Hidden state in prompts, invisible dependencies, lossy handoffs goal→tasks→code. - PMs and devs don’t share the same live view of progress. What it does - Kanban that actually executes: plan on the board, MCP tools drive the flow. - Auto “scrum master”: decomposes stories, sets deps, enforces sane state transitions. - Agents prepare context-rich prompts for Claude and move cards across columns. - Realtime board (Socket.io), dependency graph, audit trail. - Local-first: your data lives in your Supabase project. MIT licensed. Quick start (~2 min) npx @orchestro/init npm run dashboard (opens http://localhost:3000) restart Claude Code, then ask: “Show me orchestro tools” (~60 tools) Tech TypeScript MCP server, Next.js dashboard (React Flow), Supabase (PostgreSQL + RLS). What I’m looking for - Heavy Claude Code users to test and tell me what hurts (missing tools, bad UX, slow paths). - Real-world feedback on the “agents move the cards” model. - PRs/issues welcome. A star helps discoverability if it’s useful. Links Website: https://www.orchestro.org/ Repo: https://github.com/khaoss85/mcp-orchestro |