What Synaxis is
The control plane for every account you hold: one connector URL, so Claude sees a single connector instead of a dozen.
Claude connects to MCP servers one at a time. Two Notion workspaces means two connectors, two consent flows, and two places to revoke access. Nothing is shared: not the audit trail, not the approval rules, not the token budget.
Synaxis sits in the middle. You register accounts with it, it holds the credentials, and it publishes one endpoint that aggregates every tool. Names are prefixed per account, so the same provider twice never collides.
What it gives you
- One connector URL in Claude, however many accounts sit behind it.
- Curated endpoints that expose a named subset of tools, so Claude reads a fraction of the context on every request.
- Approval gates on anything that writes or deletes.
- Guardrails on responses: redaction, size caps, and injection flagging.
- One audit trail across every account, with payload replay.
What it is not
- The Engine is not the hosted Platform. You can run the open Engine on your own infrastructure without a Synaxis account. A hosted workspace adds managed identity, billing, and lifecycle services around an isolated Engine.
- Not a registry. A registry lists what exists and hands you a file. Synaxis decides what a given agent gets at the moment it asks, and can stop giving it.
- Not an observability tool. Tracing tells you what an agent did after it did it. Synaxis sits in the request path, so a call that breaks a rule never reaches the provider.
This guide covers the self-hosted Engine. For managed workspaces, see Activate a hosted workspace.
See the flow first
For a visual overview of the hosted workspace, see how access becomes useful work. To run the Engine yourself, continue to Install.