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 edits the config file by hand; Option B does the same thing in one command.

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",
        "transport": "streamable-http",
        "headers": {
          "x-api-key": "open_xxxxx"
        }
      }
    }
  }
}

Keep transport as streamable-http; OpenClaw falls back to sse when it is omitted. Replace open_xxxxx with your key. Please make an account at openfinance.tech to get your keys.

Reload

Run openclaw mcp reload to refresh MCP connections, or restart OpenClaw.

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" --transport streamable-http --header "x-api-key: open_xxxxx"

Every request needs the header, market data included.

Verify

openclaw mcp list
openclaw mcp doctor --probe

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

Getting started

Coding agents

Chat clients

Help

Option A, edit `openclaw.json`

Option B, CLI

Verify

Option A, edit openclaw.json

Option B, CLI

Verify

Option A, edit `openclaw.json`