MCP clients

Use the dedicated client URL

Create a client registration, grant the connection namespaces it may use, and paste its URL into Claude, Codex, or another OAuth-capable MCP client:

https://your-engine.example.com/mcp/clients/{slug}

That route is subject-bound. An owner, admin, or operator can authorize it only as the exact member assigned to the client; personal connections are included only when that member owns them.

OAuth binds the client

The first successful Dynamic Client Registration consent binds the MCP registration to this Synaxis client. Changing namespace grants, resetting the OAuth binding, or revoking the client advances its epoch and invalidates previously issued access tokens. Synaxis stores the opaque member subject, not a copy of the member's Platform profile.

Shared endpoints are different

The root /mcp endpoint and shared /mcp/{slug} endpoints are workspace surfaces. Only an owner or admin can consent to them, and personal connections are omitted. Use a dedicated client endpoint when access must follow an individual member.