Skip to main content
Tool profiles reduce MCP discovery to the tools a client needs. Authorization still comes from OAuth scopes, workspace roles, confirmation policy, and the server.

Start with the default

Use the bare endpoint for most clients:
It selects the supported v2 surface. Call orgx_bootstrap first to confirm the workspace and receive routing guidance.

Choose a focused profile

Append ?profile=NAME only when the workflow benefits from a smaller tool set. For example:
Unknown profile names fall back to v2. Reconnect the client after changing a profile URL so it refreshes tools/list.
A smaller discovery surface is not automatically read-only. Each tool’s annotations describe observable side effects, and server authorization is enforced on every call.

Connect a client

Follow the setup path for your client.

Browse MCP tools

Inspect the current public tool contracts.