All clients
OpenClaw
OpenClaw speaks MCP over streamable HTTP, save the Creatorland server with `openclaw mcp add` and run `openclaw mcp login` to authenticate.
Setup
OpenClaw
Loading setup…
- Who it’s for
- Anyone running OpenClaw, the self-hosted personal AI assistant that wires Telegram, WhatsApp, and Discord to autonomous agents.
- Compatibility
- OpenClaw stores outbound MCP servers under `mcp.servers` in its config (`~/.openclaw/openclaw.json`), added with `openclaw mcp add` or edited from the Control UI `/mcp` page. Use `transport: "streamable-http"` with `auth: "oauth"`; `openclaw mcp login` runs the MCP OAuth flow and OpenClaw registers itself through Dynamic Client Registration, so no manual allowlisting is needed.
- Verify the connection
- After you sign in with your Creatorland account, your tools appear in the client, scoped to your account. If the list comes back empty, that signals the email you signed in with has no Creatorland account yet, create one (or sign in with the right one) at creatorland.com and reconnect. An empty list still confirms the OAuth handshake succeeded and you’re pointed at the right server.
Troubleshooting
- After `openclaw mcp add ... --auth oauth`, run `openclaw mcp login creatorland`; it prints an authorization URL, approve it in your browser, then rerun with `openclaw mcp login creatorland --code <code>`. Confirm with `openclaw mcp doctor creatorland --probe`.
- Use `transport: "streamable-http"` (the canonical spelling); a bare `type: "http"` is normalized to the same thing, but streamable-http is what OpenClaw’s runtimes consume directly.
- If you briefly saw an “Unrecognized client” page, that is a stray authorize call with no client_id; re-run the login and OpenClaw self-registers via DCR.
- An empty tool list after sign-in means the email has no Creatorland account yet, create one free and reconnect.
