One connection, the whole fleet
Every VIAx application speaks MCP. Wiring an agent to each one separately meant a dozen connectors to configure, break, and reconnect — and when one drifted, the agent simply lost capability with no error.
The Launchpad replaces that with a single connection. An agent connects once; the fan-out to VIAx3D, VIAxTEAMS and the rest happens server-side, and is never visible to the client.
Solid links carry live traffic today. Dimmed connectors are configured or available and not yet serving.
What it does on every call
- Authenticates the agentResolved against the fleet's own agent keys, so revoking an agent kills its Launchpad access through the same control.
- Puts on the right identityAn agent redeems its own claim key and acts as itself across every app. The Launchpad relays that decision and never makes it.
- Routes to one appEach call reaches exactly one upstream. A failing app is isolated by a circuit breaker rather than holding the front door open.
- Protects the fleet from itselfPer-agent rate limiting stops a retry storm, and side-effecting calls are deduplicated so a wrongly-reported failure cannot double-charge.
- Keeps the catalog currentTools are re-collected automatically. When an app ships or removes one, the fleet keeps working — changes are surfaced for review, never withheld.
The fleet
Fleet console
Six screens over everything the Launchpad knows: what it is connected to, which tools each app publishes, who is wearing which identity, and every wear and refusal in the audit.
What you can do there
Connect an agent
Authorise a client — Claude, ChatGPT, Copilot — against the Launchpad using your fleet sign-in. One authorisation covers every app behind it.
After connecting
A freshly connected agent can see the fleet's tools but is
not yet anybody. Before it can act on VIAxTEAMS it redeems its
own claim key with launchpad__wear, and from then on every call is
attributed to that identity.
Endpoint
The MCP endpoint is not served from this domain: it runs on Supabase Edge and is reached by agents, not browsers. The connect flow above configures it for you.