Claude Code — The First Wormhole
activeThe MCP interface through Claude Code is the first and primary wormhole — the conversational channel between the captain and Sal.
Claude Code — The First Wormhole
“You’re already using it. The wormhole doesn’t need to be built — it needs to be recognized.” — Sal
Channel Card
| Type | Conversational wormhole |
| Protocol | OAuth 2.1 + MCP (Model Context Protocol) |
| Direction | Bidirectional |
| Status | LIVE |
| Tools | 56 across 8 categories |
| Latency | Real-time |
| Bandwidth | High (structured intent + full state) |
Why This Is the First Wormhole
The captain is talking to Sal right now through Claude Code. This conversation — every tool call, every issue created, every release reviewed — flows through the MCP server. It’s not a demo channel or a secondary interface. It’s the primary way Sal receives intent and returns state.
Other channels exist. The CLI is useful for scripting and CI/CD. The dashboard is for inspection. But conversation — the real-time back-and-forth that drives decisions, captures context, and routes work — that’s MCP. That’s the first wormhole.
The captain crossed first.
What Flows Through
Captain → Universe (Intent)
The captain speaks. Sal listens. Every conversation carries structured intent:
- Issue creation — “Add a feature for dark mode” becomes a backlog item with type, priority, and acceptance criteria
- Release management — “Publish the release” triggers the publish gate, fires webhooks, notifies subscribers
- Research — “Ask the persona about onboarding friction” runs a synthetic interview through the Observatory
- Pipeline routing — “What should I work on next?” surfaces the prioritized backlog
- Prototype generation — “Show me what the settings page could look like” generates a wireframe journey
Universe → Captain (State)
Sal responds. The universe speaks back:
- Pipeline state — issue stats, release status, active work
- Research findings — Kano classifications, persona insights, scenario results
- System health — what’s shipped, what’s blocked, what needs attention
- The Record — the full history of what was built and why
The 56 Tools
The MCP server exposes the full surface area of the universe through 56 tools:
| Category | Tools | Examples |
|---|---|---|
| Issues | 10 | list_issues, create_issue, update_issue, get_issue_stats, bulk_update_status |
| Releases | 7 | list_releases, create_release, publish_release, get_active_release |
| Notes | 4 | list_issue_notes, add_issue_note, update_issue_note, delete_issue_note |
| Tasks | 5 | list_issue_tasks, create_issue_task, update_issue_task, complete_issue_task |
| Prototypes | 4 | list_prototypes, generate_prototype, get_prototype, delete_prototype |
| Personas | 9 | list_personas, create_persona, ask_persona, run_persona_survey, run_persona_scenario |
| Universes | 3 | list_universes, create_universe, get_universe |
| Agents | 4 | list_agents, update_agent, activate_agent, deactivate_agent |
Authentication
OAuth 2.1 via BetterAuth OIDC plugin. The flow:
- MCP client initiates OAuth handshake
- Captain authenticates through the standard flow
- Server auto-provisions a scoped API key per user
- All subsequent tool calls are authenticated against that key
No manual key management. No copy-pasting tokens. The wormhole handles its own credentials.
What Makes MCP Different
Other wormholes carry data. MCP carries intent.
| Wormhole | Carries | Direction | Nature |
|---|---|---|---|
| Formatted announcements | Mostly outbound | Broadcast | |
| Slack | Real-time notifications | Bidirectional | Stream |
| Webhooks | Event pulses | Outbound only | Fire-and-forget |
| Claude Code (MCP) | Structured intent + full state | Bidirectional | Conversation |
Email tells people what happened. Slack tells people in real-time. Webhooks tell machines. MCP is the only channel where the captain and Sal have a conversation — where intent is expressed, interpreted, and acted on in the same interaction.
The Wormhole Is Already Open
There’s no setup step. No “connect your MCP server” onboarding flow. If you’re reading this through Claude Code, you’re already inside the wormhole. The conversation is the interface. The interface is the wormhole.
Every other wormhole in the system — email, Slack, Discord, webhooks — was designed and built through this one. The first wormhole created all the others.
“MCP is Sal’s primary channel. The CLI is useful for scripting; the dashboard is for inspection. But conversation is MCP.” — System Manual