MCP

Connect MCP clients

Use Clerk OAuth for the hosted server or the npm stdio package for local and break-glass operation.

Hosted OAuth setup

The production MCP endpoint uses Streamable HTTP and Clerk OAuth. Add this configuration:

json
{
  "mcpServers": {
    "liveprobe": {
      "url": "https://liveprobe.tryastrea.tech/mcp"
    }
  }
}

Select Login in the MCP client, authenticate in the browser, and choose an active Clerk organization. The client stores and refreshes the OAuth token. LiveProbe does not ask users to copy a human API key.

Cursor workflow

  1. Open Cursor settings and add the MCP server configuration.
  2. Refresh MCP servers and complete the browser login.
  3. Ask Cursor to run ping_broker.
  4. Select a project and environment, then run list_services.
  5. Create or inspect catalog resources before issuing a runtime credential.

Local stdio fallback

The npm package is intended for local development and the shared-key break-glass path. It requires Node.js 20+.

shell
LIVEPROBE_API_KEY="<operator-key>" \
npx -y @doomslayer2945/liveprobe-mcp@0.4.0 \
  --broker-url https://liveprobe.tryastrea.tech
json
{
  "mcpServers": {
    "liveprobe": {
      "command": "npx",
      "args": [
        "-y",
        "@doomslayer2945/liveprobe-mcp@0.4.0",
        "--broker-url",
        "https://liveprobe.tryastrea.tech"
      ],
      "env": {
        "LIVEPROBE_API_KEY": "<operator-key>"
      }
    }
  }
}

Authentication errors

ErrorMeaningAction
unauthorizedMissing, expired, invalid, or revoked tokenReconnect hosted OAuth or replace the local bearer key
organization_requiredClerk session has no active workspaceSelect the invited Clerk organization and reconnect
clerk_session_pendingOrganization enrollment is incompleteComplete the pending workspace enrollment
forbiddenThe identity cannot perform that operationConfirm workspace membership and operation scope
scope_mismatchA service key targeted another scopeUse the project/environment used when issuing the key