MCP support

Model Context Protocol is how AI assistants call tools safely. Cloxbi hosts a streamable HTTP MCP server — OAuth by default, no local install.

Cloxbi AI integration page showing MCP OAuth URL and optional API key

Hosted MCP

One URL. OAuth sign-in. No middleware.

Cloxbi runs MCP at https://app.cloxbi.com/mcp. Use Settings → Connectors in Claude or ChatGPT with OAuth. Optional mcp_… API keys work via the mcp-remote bridge for Claude Desktop's config file.

Claude Desktop config file

claude_desktop_config.json does not accept "type": "http" or a bare "url". Invalid entries are skipped on launch — you'll see a warning about cloxbi. Use Connectors in the app for OAuth, or the mcp-remote stdio bridge below for Edit Config.

Setup in three steps

  1. Log in as a manager at app.cloxbi.com and open AI integration (/manager/mcp).
  2. Add a connector in Claude or ChatGPT: URL https://app.cloxbi.com/mcp, Authentication: OAuth.
  3. Sign in when prompted with your Cloxbi staff account. Tools mirror your manager permissions.

Claude Desktop Edit Config (mcp-remote + OAuth)

{
  "mcpServers": {
    "cloxbi": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://app.cloxbi.com/mcp",
        "--transport",
        "http-only"
      ]
    }
  }
}

Requires Node.js 18+. On first connect, mcp-remote opens a browser for Cloxbi OAuth — sign in with your staff email or phone and password at app.cloxbi.com. Fully quit Claude (Cmd+Q) and reopen after editing the config file.

Troubleshooting

  • Claude: invalid config on launch — Remove "type": "http" / "url" from claude_desktop_config.json. Use Connectors in the app, or the mcp-remote block above for Edit Config.
  • Timed out or disconnected — Fully quit Claude (Cmd+Q), reopen, and reconnect. Reconnect after Cloxbi server updates too.
  • OAuth failed — Use a manager, scheduler, or location admin account. Employee-only logins cannot authorize MCP.
  • Tools missing — Start a new chat and confirm the Cloxbi connector is enabled for that conversation.

Bearer token (advanced)

{
  "mcpServers": {
    "cloxbi": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://app.cloxbi.com/mcp",
        "--transport",
        "http-only",
        "--header",
        "Authorization:${MCP_AUTH_HEADER}",
        "--header",
        "X-Location-Id:${MCP_LOCATION_ID}"
      ],
      "env": {
        "MCP_AUTH_HEADER": "Bearer mcp_YOUR_KEY_HERE",
        "MCP_LOCATION_ID": "123"
      }
    }
  }
}

Generate mcp_… keys in AI integration. Omit X-Location-Id for single-site teams.