What Synaxis is

An open MCP Engine and a managed Platform, separated so the runtime remains capable on its own.

Claude, Codex, and other MCP clients normally connect to servers one at a time. Two Notion workspaces means two consent flows and two places to revoke access. Synaxis Engine sits in the middle: register independently authorized connections, organize them in connection namespaces, and publish their tools through the endpoint that fits the audience.

Synaxis Platform manages the hosted lifecycle around that Engine: registration, workspace membership, activation, provisioning, and the workspace URL. Each hosted workspace receives an isolated Engine.

Choose a delivery surface

/mcp is the shared aggregate. It excludes personal connections, and only a workspace owner or admin can authorize it.
/mcp/{slug} is either a shared endpoint bundle or a curated connector. Connectors can narrow tools and apply approvals and response guardrails.
/mcp/clients/{slug} is a subject-bound client endpoint. It exposes the connection namespaces granted to that exact workspace member and is the route to use for personal connections.

See the flow first

Want the shape of the product before setup? Open the Synaxis homepage and choose Watch demo for the short workspace, tool, and guardrail walkthrough.

The boundary

The Apache 2.0 Engine has no Platform profile, subscription, or billing model. In a hosted workspace, the Platform sends a short-lived signed assertion containing opaque workspace, member, and role identifiers. The Engine verifies that assertion and enforces its own connection, namespace, and MCP-client ownership rules. The Platform does not sit in the normal MCP tool-call path.