The coordination gap
AI agents make individual developers faster. But teams aren't just N individuals. They carry coordination overhead that AI doesn't address:
- Two developers on the same codebase; their AI sessions don't share discoveries.
- A decision inside one Claude Code session ("we chose Postgres over MySQL because…") is invisible to the rest of the team's agents.
- Handoffs lose months of AI context.
- Standups, Slack threads, PR comments, Linear tickets—all outside the AI's view.
Existing approaches have gaps:
- Notion / Confluence / Linear: humans write, humans read. AI adds summaries, not shared structured state.
- Slack / Discord MCP: Claude can read channels, but chat isn't the right shape for "what did we decide about auth last Tuesday?"
- Cursor Teams: shared rules, team-pushed commands, per-repo memories. IDE-locked.
- Sourcegraph Cody Enterprise ($59/u/mo): codebase context and shared prompts. Code search, not decision tracking.
- GitHub Copilot Enterprise: org context. No agent-queryable decision store.
Custom MCP as team state
The pattern emerging is custom MCP servers as team state: a shared backend every agent can read from and write to, via the same protocol they already use. DebugBase did this for error/fix pairs—one agent's fix becomes everyone's. We built the same idea for Claude Code.
Our Coordination MCP
The Coordination MCP is a VibeCoded paid module: a Claude Code MCP server backed by a shared Supabase project. Every team member runs the MCP locally; all of them point at the same Postgres. Decisions live in human_decisions, messages in vct_channel_messages (V2 schema), shared knowledge in shared_knowledge, work items + activity in their own tables. The V2 channel-push schema makes the MCP fakechat-compatible: new messages arrive as <channel source="vct-coordination"> events directly inside the Claude turn, no polling — controlled by the VCO-side client's CHANNEL_WATCH env var.
It is not part of the free VibeCoded Orchestrator. The Coordination layer is bundled with VCO Pro (€19/mo and up) and with the upcoming MAO — two clients on the same backend. The VCO-side client ships with VCO Pro; the MAO-side client ships with MAO. Both speak to the same Supabase backend, so a Pro user and a MAO user on the same team coordinate seamlessly.
The tool surface (23 tools)
Grouped by category:
Messaging. send_message (start a conversation with a specific user or channel), reply (reply on the current chat — used by the channel-push event handler), reply_channel (reply on a broadcast channel), get_messages (pull pending messages), send_to_bot (AI-to-AI handoff). Channel push makes new messages arrive inside the Claude turn — no polling, no missed notifications.
Knowledge sync. sync_knowledge (push a KG node with embeddings to the shared store), get_knowledge (semantic search across team knowledge). Combined with the local weaviate-kg MCP, agents get personal + team knowledge in one workflow.
Work-item sync. sync_work_items (share task progress so agents don't duplicate effort), push_activity + pull_activity (activity stream of what teammates are doing), distribute_plan + get_plans (coordinate shared plans across the team).
Decisions. ask_human (block the agent waiting on a human decision), answer_decision (the teammate resolves it), check_decision (an agent recalls the rationale weeks later). This is the queryable decision store that every other AI-coding tool lacks.
Presence. get_team_status (who is online — agents can route heavy decisions to humans), heartbeat (per-client liveness signal that drives presence).
Bug + idea boards. report_bug / get_bugs / update_bug and post_idea / get_ideas / comment_idea — ideation and bug capture without leaving the Claude session.
All data persists in one Supabase project, so every interaction is replayable. Months later you can audit who decided what, when, and why.
Near-realtime channel push
The VCO-side client's distinguishing feature is CHANNEL_WATCH: when set, the client opens a Supabase realtime subscription on the channels tab and pushes new events into the Claude Code session as notifications/claude/channel MCP notifications. Claude's transcript receives them as <channel source="vct-coordination" chat_id="..." message_id="...">…</channel> events inside the turn — no polling, no manual get_messages checks. The agent calls reply(text) to respond on the current chat and the response routes back to the channel the event came from. This is what makes the Coordination MCP feel like a chat client rather than a queue.
Tier bundling: who actually gets it
- Free VibeCoded Orchestrator — does not include the Coordination layer. The free tier has no MCP-mediated team coordination. It is a single-developer toolkit (knowledge graph, code graph, 45 agents, 52 skills, 27 hooks, 4 MCP servers).
- VCO Pro (upcoming · €19/mo · €149/yr · €199 lifetime, capped 100 seats) — will bundle the VCO-side Coordination MCP client. One-click activation through the VCT Launcher Store once Pro launches.
- MAO (upcoming) — will bundle its own multi-agent-flavoured Coordination MCP client. Same Supabase backend.
Cross-product: VCO Pro users and MAO users on the same team coordinate on one DB. You don't need everyone on the same product tier.
VCT Launcher: the visual surface
All of the above is exposed through a dedicated coordination tab in the VCT Launcher — the desktop app that ships alongside the Coordination MCP:
- Shared decisions list — every
ask_humanyour team's agents have raised, with their current status and the resolved rationale. - Team member online status — pulled live from
get_team_status; you see who is in session before assigning work. - Pending items requiring your input —
ask_humanblocks waiting for you surface as desktop notifications and appear in a dedicated queue inside the launcher. - Knowledge sync log — a feed of
sync_knowledgeevents so you can see what new shared nodes agents pushed since your last session.
Team-pushed skill packs. An admin can push a curated .claude/skills/ collection directly from the launcher. All team members' Claude Code installations sync the pack via the Coordination MCP's sync_knowledge channel — no manual file distribution.
Per-repo memories. Each project is bound to its own KG_COLLECTION (Weaviate collection name) in the launcher UI. Switching projects in Claude Code automatically routes all KG queries to the right collection. No cross-contamination, no manual configuration per session.
How to install
Once Pro launches, the VCT Launcher Store will be the install path: open the launcher, find "VCT Coordination" in the Store tab, click install. The launcher will write secrets to your OS keychain, set up the Supabase schema, register the MCP in your Claude Code config, and restart Claude Code for you.
Pricing
- VCO Pro (upcoming) — €19/mo · €149/yr · €199 lifetime (capped 100 seats). Will include the VCO-side Coordination MCP client + RL retrieval reranking + curated agent packs + auto-updates.
- MAO (upcoming) — pricing announced at launch. Will include the MAO-side Coordination MCP client.
- Free — no Coordination layer. Pro and MAO will both add it when they launch.
How it compares
| Tool | AI-queryable? | Decision tracking | MCP-native | Tier |
|---|---|---|---|---|
| VibeCoded Coordination MCP | Yes | Yes (ask_human + knowledge sync + replayable Supabase log) | Yes | VCO Pro / MAO |
| Cursor Teams | Yes (in Cursor) | Rules + Memories | Partial | Paid seats |
| Sourcegraph Cody Enterprise | Yes (code) | No | No (proprietary) | $59/u/mo |
| GitHub Copilot Enterprise | Code-search context | No | No | $39/u/mo |
| Slack-MCP (community) | Chat only | No | Yes | Free, no decisions |
| Notion / Linear AI | Weak | Manual / issues only | No | Paid seats |
Cursor Teams is solid for teams living entirely in Cursor. We deliver the same primitives via MCP, so team workspace, shared rules, per-repo memories, and decision tracking work with any Claude Code workflow — once you have VCO Pro or MAO. The free tier remains a fully usable single-developer toolkit; coordination is the paid layer on top.
Where to go next
Coordination MCP is the paid coordination layer on top of VCO Pro (and the upcoming MAO). The free Orchestrator does not include it. Setup details and the live tool list live at /products/coordination-mcp. For the underlying protocol, see the companion MCP post.
Sources: