Install for OpenClaw

OpenClaw stores outbound MCP server definitions under mcp.servers in its config. Embedded runtimes (Pi, Codex, Gemini, and others) consume that registry when they need remote tools.

1. Mint a token

Open API tokens, create a token, copy the value (shown once).

Starter abilities for inbox triage:

forms:read, submissions:read, submissions:write, webhooks:read.

* * *

2. Add Formspring

Option A - CLI (recommended)

openclaw mcp set formspring '{"url":"https://formspring.io/mcp-server","transport":"streamable-http","headers":{"Authorization":"Bearer YOUR_TOKEN"}}'

Verify:

openclaw mcp list
openclaw mcp show formspring

Option B - edit config

Add to ~/.openclaw/openclaw.json:

{
  "mcp": {
    "servers": {
      "formspring": {
        "url": "https://formspring.io/mcp-server",
        "transport": "streamable-http",
        "headers": {
          "Authorization": "Bearer YOUR_TOKEN"
        }
      }
    }
  }
}

Use streamable-http (OpenClaw's canonical spelling for remote HTTP MCP). openclaw mcp set also accepts CLI-native type: "http" and normalizes it.

* * *

3. Reload

Restart the OpenClaw runtime or start a fresh agent session so it picks up the new server definition. These commands only write config; they do not prove the endpoint is reachable until a runtime connects.

* * *

4. Test

Ask your OpenClaw-backed agent:

List my Formspring forms.

If tools are missing, confirm the token abilities include forms:read and that the gateway/runtime you use supports HTTP MCP transports.

* * *

Related

• MCP overview →
• Setup wizard → - generates the paste-ready JSON and CLI one-liner
• Authentication →