Legate Connect Docs

Hot-wallet demos and shared env-file credentials break down as soon as more than one operator, agent, or regulated review touches a permissioned network. You need a connection surface that agents can call under delegated authority — without parking long-lived write keys inside the model host.

Legate is Stratum’s production MCP envoy. The unit of record is channel-scoped shared ledger state: tools read that state and, when entitled, follow a prepare → external-sign → submit path for writes. This site answers one job: how to connect a client to Legate. It does not document how Legate scores, polices, or builds its internals. See Disclosure Boundary.

Who connects

You are…	What you need	Start here
Agent integrator (Cursor, Claude, custom MCP)	Point a client, authenticate, complete a first tool call	Connect → Quickstart
Stratum operator	Issue a connection without exporting signing material	Connect
Security or legal reviewer	Forwardable contract pages	Disclosure Boundary

What Legate gives you

Capability	What it gives you
Remote MCP (HTTPS)	Stateless Streamable HTTP for Cursor, Claude, and custom agents
Local stdio	Trusted-operator machines without a remote host
Connection tokens	Short-lived credentials from Stratum — no signing-material export
Capability packs	Scopes map to published packs such as legate.read and legate.write
Safe write sequence	simulate → prepare → external sign → submit_signed
Agent Card	Discovery for A2A clients at a well-known path
Liveness signals	/health (process up) and /ready (safe to send traffic)

Reading order

To answer	Read
What can I call today?	Integration Surfaces
How do I obtain a connection?	Connect
How do I complete a first tool call?	Quickstart
How does Bearer auth work at the interface?	Authentication
Who may act, and who signs writes?	Access Model
What do public errors look like?	Errors
What stays out of these docs?	Disclosure Boundary