Skip to content

OpenClaw

Checked on 2026-11-06 against docs.openclaw.ai/cli/mcp, MCP transports, skills and the openclaw mcp source (release v2026.11.1). The --header flag is from the CLI source; the docs show headers in the config form. An API key header is supported.

OpenClaw has a built-in MCP client. Saved servers live under mcp.servers in ~/.openclaw/openclaw.json (JSON5).

Create a key (how). With the CLI (--header takes name=value and can repeat):

Terminal window
openclaw mcp add crossmart \
--url https://mcp.crossmart.io/mcp \
--transport streamable-http \
--header 'x-api-key=${CROSSMART_API_KEY}'

Or in ~/.openclaw/openclaw.json, which you can also set with openclaw mcp set crossmart '<json>':

{
mcp: {
servers: {
crossmart: {
url: 'https://mcp.crossmart.io/mcp',
transport: 'streamable-http', // without it OpenClaw assumes SSE
headers: { 'x-api-key': '${CROSSMART_API_KEY}' },
},
},
},
}

OpenClaw resolves ${VAR} in header values, so the key stays in the environment (export CROSSMART_API_KEY where the gateway runs). openclaw mcp doctor warns about literal tokens in the config, and header values are redacted in its output.

Keep x-api-key rather than Authorization: when a server later uses auth: "oauth", OpenClaw ignores a static Authorization header.

Terminal window
openclaw mcp probe crossmart
openclaw mcp tools crossmart
Terminal window
git clone --depth 1 https://github.com/crossmart-io/crossmart.git /tmp/crossmart
openclaw skills install /tmp/crossmart/skills/crossmart --as crossmart

Or copy the folder to <workspace>/skills/ or ~/.agents/skills/. The skill is not on ClawHub yet, and the repository is private for now; see the Crossmart skill.