Connect
Get a client pointed at Legate without tribal knowledge and without exporting signing material.
Maturity for install wizard and BFF tokens is Early Access / by arrangement until Integration Surfaces marks them Live.
Prerequisites
- A Stratum peer deployment where Legate is entitled for your tenant
- Operator access to the Stratum dashboard
- An MCP client (Cursor, Claude, or a custom Streamable HTTP / stdio client)
Obtain a connection
| Path | What you receive | Notes |
|---|---|---|
| Dashboard install / deeplink | Client config that points at your Legate HTTPS endpoint | Prefer this when the install wizard is Live for your environment |
| Short-lived connection token | Bearer credential minted by Stratum (BFF) | Audience-bound to your Legate resource URI; rotates; not a wallet export |
| Agent Card URL | Discovery document for A2A clients | See Agent Card |
| Local stdio config | Command + env for a trusted operator machine | Remote multi-user traffic should use HTTPS + JWT |
If the install wizard is not yet Live for your network, your BlockSkunk contact can issue a by-arrangement connection. Do not copy signing material into Cloud Functions, laptops, or chat transcripts.
Transports
| Transport | When to use |
|---|---|
| Remote MCP over HTTPS (Streamable HTTP) | Default for Cursor / Claude / agents against a peer-hosted Legate |
| Local stdio | Trusted operator workstation for smoke tests and local demos |
Remote MCP is stateless: replicas do not require sticky sessions for ordinary tool calls. Point the client at the MCP URL issued for your deployment — not at an inventable hostname.
Agent Card
A2A-capable clients discover Legate skills from the well-known path on your Legate base URL:
https://<your-legate-host>/.well-known/agent-card.json
The card advertises high-level skills that map to published capability packs. It is a discovery contract, not an admin API dump.
Liveness
| Endpoint | Meaning for callers |
|---|---|
GET /health | Process is up |
GET /ready | Safe to send traffic (dependencies the operator cares about are available) |
Use /ready for load-balancer and client retry gates. Exact dependency lists stay out of public docs.
What never leaves the peer
- Long-lived write private keys / signing material
- Wallet or identity archives for export into Cloud Functions or laptops
- Production JWTs pasted into public tickets or docs examples
Next: authenticate and complete a first tool call in Quickstart.