MCP: Claude (Code & Desktop)

Connect Claude to your workshop so it can read your sources of truth and propose new ones. Claude Code (the CLI) and the Claude Desktop app are set up differently.

Prerequisites

• A token: APIs -> API Keys (scope to least privilege; see Auth & Tokens).

Claude Code (CLI)

Fastest - fai mcp install configures Claude Code (and your other detected agents) in one command:

fai mcp install https://openx.fathym.com/oi-api/mcp --name openx --auth "YOUR_TOKEN"

Or use Claude Code directly:

claude mcp add --transport http openx https://openx.fathym.com/oi-api/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"

Either writes ~/.claude.json with an mcpServers.openx entry (type: http, your URL, the bearer header). Browse the tools with fai mcp preview openx.

Claude Desktop (app)

The Claude Desktop app doesn't take a remote HTTP server with a bearer header directly, so point it at the endpoint through the mcp-remote bridge. Edit claude_desktop_config.json (macOS ~/Library/Application Support/Claude/, Windows %APPDATA%\Claude\):

{
  "mcpServers": {
    "openx": {
      "command": "npx",
      "args": [
        "mcp-remote@latest",
        "--http",
        "https://openx.fathym.com/oi-api/mcp",
        "--header",
        "Authorization: Bearer YOUR_TOKEN"
      ]
    }
  }
}

Restart Claude Desktop.

Verify

Look for the OpenX tools (a tools/hammer indicator): list_data_connections, run_warm_query, run_adhoc_warm_query, tail_telemetry, get_workspace_flow, and manage_proposals.

Use it

Ask in plain language: "What were the average signups per hour today?" Claude calls run_warm_query against your saved source of truth. To build, it proposes via manage_proposals; you accept in the portal - there is no accept tool over MCP.

Notes

• Every call is recorded in your workshop's change history.
• Token expired? Regenerate under APIs -> API Keys and re-run the install (or update the header).