OpenClaw

OpenClaw supports MCP servers natively. Remote streamable HTTP endpoints like OpenFinance can be added to OpenClaw’s config and invoked through any of its interfaces (TUI, messaging channels, or sub-agents).

Option A, edit `openclaw.json`

Open the config

Open ~/.openclaw/openclaw.json (create it if it does not exist).

Add the server

Add OpenFinance inside the mcp.servers object:

{
  "mcp": {
    "servers": {
      "openfinance-tech": {
        "url": "https://api.openfinance.tech/agent/mcp",
        "headers": {
          "x-api-key": "open_xxxxx"
        }
      }
    }
  }
}

Drop the headers object if you only need public tools.

Restart

Restart OpenClaw, or run the reload command to refresh MCP connections.

OpenClaw uses mcp.servers, nested under a top-level mcp key. This is different from Claude’s flat mcpServers structure.

Option B, CLI

openclaw mcp add openfinance-tech --url https://api.openfinance.tech/agent/mcp

For wallet tools, set the header during registration as documented in the OpenClaw CLI reference for your version.

Verify

openclaw mcp list

openfinance-tech should appear in the output with a connected status.

Getting Started

Coding Agents

Chat Clients

Reference

Option A, edit `openclaw.json`

Option B, CLI

Verify

​Option A, edit openclaw.json

​Option B, CLI

​Verify

Option A, edit `openclaw.json`

Option B, CLI

Verify