Feature · Connect
Shipped · MCP + integrations + custodyGovern the tools you connect, custody intact.
Point your traffic at SynOI once. Existing LLM calls are governed by repointing one env var; everything else is governed with one SDK call. Credentials never leave your side of that connection.
What it does
The same checkpoint, whichever tool or agent is calling.
Whether the call is an existing LLM request, an MCP tool call, or a direct API action, it passes through the same governed checkpoint and produces the same signed receipt. Adding a new tool does not mean adding a new governance system.
How it works
Zero code for LLM traffic, one call for everything else.
Repoint ANTHROPIC_BASE_URL or OPENAI_API_BASE at your gateway and existing LLM traffic is governed with no code changes. For any other action, wrap the call with gate() from the SDK.
An MCP bridge lets agents call tools across other agents through the same governed path, so cross-agent tool use gets a receipt too, not just direct calls.
Status
Shipped core, one early-phase piece, one roadmap direction.
The MCP bridge, 23+ verified tool integrations, and custody-preserving connect flow are shipped and running today. An agent-to-agent (A2A) relay has merged and is early-phase: it works, but does not yet have a conformance vector behind it. Portable identity across gateways you do not run, letting your context follow you to any gateway, is a roadmap direction: the resolver library is published, but the hosted lookup service is not deployed yet.
Folded in from the former catalog
- Gateway
- MCP Gateway
- MCP Server
- @synoi/sdk
- @synoi/guard
- Connect
- OpenClaw router
- LangChain interceptor
- Quickstart
- A2A relay
Connect the tools you already use.
Most setups take one environment variable for LLM traffic and one SDK call for everything else.