> ## 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.

# Agent Quickstart

> Establish an MCP connection and verify it with a safe, read-only call.

This guide gets you from zero to a working MCP connection with one safe,
read-only verification call. It does not create or approve work.

## Step 1: Connect

> [tab] OpenClaw
>
> Install the documented plugin, then complete browser pairing:
>
> ```bash theme={"dark"}
> openclaw plugins install @useorgx/openclaw-plugin
> ```
>
> Open the plugin's local dashboard, choose **Connect OrgX**, and approve in
> the browser.
>
> [Full OpenClaw setup guide →](https://docs.useorgx.com/docs/guides/openclaw-plugin-setup.md)

> [tab] Cursor
>
> Add to `~/.cursor/mcp.json`:
>
> ```json theme={"dark"}
> {
>   "mcpServers": {
>     "orgx": {
>       "command": "npx",
>       "args": ["mcp-remote", "https://mcp.useorgx.com/mcp"]
>     }
>   }
> }
> ```
>
> Restart Cursor. On first use, `mcp-remote` opens your browser for OAuth sign-in automatically.

> [tab] Claude
>
> In Claude or Claude Desktop, open **Settings → Connectors** and add a
> custom remote MCP connector using:
>
> ```text theme={"dark"}
> https://mcp.useorgx.com/mcp
> ```
>
> Then complete the OAuth flow in your browser.

> [!TIP]
>
> Need client-specific instructions for ChatGPT, VS Code, or other MCP hosts?
> Use the full [MCP Client Setup guide](https://docs.useorgx.com/docs/guides/cursor-mcp-setup.md).

## Step 2: Verify one permitted read

Ask the client to use only its discovered OrgX tools:

> Confirm the workspace and show one recent decision or initiative with a source link. Do not create or approve work.

If the profile exposes `orgx_bootstrap`, call it first:

```json theme={"dark"}
{ "tool": "orgx_bootstrap", "args": {} }
```

The public Claude Code plugin's `claude-directory` profile omits bootstrap and
write tools. Use its `orgx_search`, `get_initiative_pulse`, or
`get_operator_chronicle` readback. An empty workspace is a valid result.
For a wrong workspace, reauthorize the intended workspace in the client;
do not call the retired `workspace action=get/list/set` interface.

## Step 3: Continue from the same record

Open the returned link, then ask a new client session to retrieve that same
record. Check its workspace and source. This verifies useful continuity.

Creating work and approving decisions are separate, explicitly authorized
workflows. Use [Product quickstart](https://docs.useorgx.com/docs/quickstart.md) when ready to save a bounded
draft with a write-capable connection.

## What's Next

> [card] [Agent Recipes](https://docs.useorgx.com/docs/agent-ops/agent-recipes.md)
>
> Small, reviewable workflows with contract links.

> [card] [Failure Playbooks](https://docs.useorgx.com/docs/agent-ops/failure-playbooks.md)
>
> Error recovery for common issues.

> [card] [Tool Profiles](https://docs.useorgx.com/docs/agent-ops/tool-profiles.md)
>
> Reduce schema overhead with role-based profiles.

> [card] [Full Tool Reference](https://docs.useorgx.com/docs/api/mcp-tools.md)
>
> Complete documentation for the current MCP tool catalog.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.