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

> Get your first successful MCP tool call in under 5 minutes.

This guide gets you from zero to a working MCP connection with a successful tool call as fast as possible.

## Questions This Page Answers

* What is the fastest path to a verified OrgX MCP connection?
* Which calls prove connectivity, workspace context, and decision readiness?
* What does “healthy first run” look like before dispatching real work?

## Step 1: Connect

<Tabs>
  <Tab title="OpenClaw (Recommended)">
    The fastest path — handles auth and config automatically:

    ```bash theme={"dark"}
    openclaw plugins install @useorgx/openclaw-plugin
    ```

    Open `http://127.0.0.1:18789/orgx/live`, click **Connect OrgX**, approve in browser. Done.

    [Full OpenClaw setup guide →](/docs/guides/openclaw-plugin-setup)
  </Tab>

  <Tab title="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>

  <Tab title="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.
  </Tab>
</Tabs>

<Tip>
  Need client-specific instructions for ChatGPT, VS Code, or other MCP hosts?
  Use the full [MCP Client Setup guide](/docs/guides/cursor-mcp-setup).
</Tip>

## Step 2: Verify Connection

Run this safe, read-only call to confirm everything works:

```json theme={"dark"}
{
  "tool": "workspace",
  "args": { "action": "get" }
}
```

**Expected response:**

```json theme={"dark"}
{
  "workspace_id": "ws_abc123",
  "name": "My Startup",
  "plan": "team",
  "created_at": "2025-10-01T00:00:00Z"
}
```

If you get `workspace_not_set`, list available workspaces and set one:

```json theme={"dark"}
{ "tool": "workspace", "args": { "action": "list" } }
```

```json theme={"dark"}
{
  "tool": "workspace",
  "args": { "action": "set", "workspace_id": "ws_abc123" }
}
```

## Step 3: Explore Your Org

```json theme={"dark"}
{
  "tool": "orgx_recommend",
  "args": { "view": "summary" }
}
```

**Expected response:**

```json theme={"dark"}
{
  "workspace": "My Startup",
  "initiatives": { "total": 3, "active": 2, "completed": 1 },
  "pending_decisions": 4,
  "active_agents": 2,
  "recent_artifacts": 7
}
```

## Step 4: Check Pending Decisions

```json theme={"dark"}
{
  "tool": "orgx_search",
  "args": {
    "type": "decision",
    "status": "pending",
    "limit": 5
  }
}
```

**Expected response:**

```json theme={"dark"}
{
  "entities": [
    {
      "id": "dec_xyz789",
      "type": "decision",
      "title": "Campaign brief ready for Q1 launch",
      "status": "pending",
      "urgency": "high",
      "created_at": "2026-02-26T10:00:00Z"
    }
  ],
  "total": 4
}
```

`orgx_decide` still works as a compatibility alias, but new clients should prefer `orgx_search`.

If you have pending decisions, approve one:

```json theme={"dark"}
{
  "tool": "orgx_decide",
  "args": {
    "decision_id": "dec_xyz789",
    "note": "Looks good, ship it!"
  }
}
```

**Expected response:**

```json theme={"dark"}
{
  "decision_id": "dec_xyz789",
  "status": "approved",
  "artifact_id": "art_abc456"
}
```

## What's Next

<CardGroup cols={2}>
  <Card title="Agent Recipes" icon="book" href="/docs/agent-ops/agent-recipes">
    Common multi-tool workflows with exact sequences.
  </Card>

  <Card title="Failure Playbooks" icon="shield" href="/docs/agent-ops/failure-playbooks">
    Error recovery for common issues.
  </Card>

  <Card title="Tool Profiles" icon="users" href="/docs/agent-ops/tool-profiles">
    Reduce schema overhead with role-based profiles.
  </Card>

  <Card title="Full Tool Reference" icon="wrench" href="/docs/api/mcp-tools">
    Complete documentation for all 54 tools.
  </Card>
</CardGroup>