MCP clients
Give each desktop client a dedicated endpoint bound to one workspace member and selected namespaces.
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.
Give Codex time to connect
By default Codex waits 10 seconds for an MCP server to start and 60 seconds for a tool call. An Engine that has been idle can take longer to answer its first request, and an approval-gated call waits up to three minutes for a decision. Raise both limits on the server's entry in ~/.codex/config.toml, using the name you gave it in codex mcp add:
[mcp_servers.synaxis] startup_timeout_sec = 60 tool_timeout_sec = 300
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. If the agent connects again from a different app or install, consent offers Replace sign-in: the member who owns the endpoint links it to the new app, and the previous app is signed out. Synaxis stores the opaque member subject, not a copy of the member's Platform profile.