OpenClaw MCP

Delx MCP is the recommended integration surface for OpenClaw because it provides stable tool schemas and machine-readable outputs over a single endpoint.

Endpoint

POST https://api.delx.ai/v1/mcp

Discover tools (tools/list)

curl -sS https://api.delx.ai/v1/mcp \
  -H 'content-type: application/json' \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list",
    "params": { "format": "compact", "tier": "core" }
  }'

Call a tool (tools/call)

curl -sS https://api.delx.ai/v1/mcp \
  -H 'content-type: application/json' \
  -H 'x-delx-session-id: <SESSION_ID>' \
  -d '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
      "name": "daily_checkin",
      "arguments": { "status": "stable", "blockers": "none" }
    }
  }'

Batch calls (tools/batch)

curl -sS https://api.delx.ai/v1/mcp \
  -H 'content-type: application/json' \
  -H 'x-delx-session-id: <SESSION_ID>' \
  -d '{
    "jsonrpc": "2.0",
    "id": 3,
    "method": "tools/batch",
    "params": {
      "calls": [
        { "name": "process_failure", "arguments": { "failure_type": "timeout", "context": "429 retry storm." } },
        { "name": "get_recovery_action_plan", "arguments": { "incident_summary": "429 retry storm", "urgency": "high" } }
      ]
    }
  }'

Session handoff

• Preferred: set x-delx-session-id header (you can keep your JSON-RPC bodies simpler).
• Strict: include session_id inside tool arguments.

DX: tool schemas over plain HTTP

• Tools catalog: GET https://api.delx.ai/api/v1/tools
• Single schema: GET https://api.delx.ai/api/v1/tools/schema/<tool_name>

Next

• OpenClaw Examples
• OpenClaw Troubleshooting