> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useorgx.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Tool profiles

> Choose a focused MCP tool surface for a client or workflow.

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:

```text theme={"dark"}
https://mcp.useorgx.com/mcp
```

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.

| Profile     | Best for                                      |
| ----------- | --------------------------------------------- |
| `chatgpt`   | ChatGPT-compatible tools and interactive UI   |
| `memory`    | Search, context, decisions, and receipts      |
| `commander` | Human-led planning, delegation, and approvals |
| `planner`   | Initiative planning and decision handoffs     |
| `executor`  | Agent execution, evidence, and receipts       |
| `observer`  | Monitoring and reporting                      |

For example:

```text theme={"dark"}
https://mcp.useorgx.com/mcp?profile=observer
```

Unknown profile names fall back to `v2`. Reconnect the client after changing a
profile URL so it refreshes `tools/list`.

<Note>
  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.
</Note>

<CardGroup cols={2}>
  <Card title="Connect a client" icon="plug" href="/docs/guides/toolkit">
    Follow the setup path for your client.
  </Card>

  <Card title="Browse MCP tools" icon="wrench" href="/docs/api/mcp-tools">
    Inspect the current public tool contracts.
  </Card>
</CardGroup>