View raw

OpenClaw#

Connect ClipKit to OpenClaw — the self-hosted, open-source personal AI assistant — whose built-in MCP client discovers and calls tools from configured servers.

ClipKit's connector is open (no key) and speaks Streamable HTTP at https://www.clipkit.dev/mcp.

Add the connector#

CLI:

openclaw mcp add clipkit --url https://www.clipkit.dev/mcp --transport streamable-http

Or in ~/.openclaw/openclaw.json (note the nested mcp → servers):

{
  "mcp": {
    "servers": {
      "clipkit": {
        "url": "https://www.clipkit.dev/mcp",
        "transport": "streamable-http"
      }
    }
  }
}

Verify#

openclaw mcp probe clipkit

It connects and reports the discovered tools. openclaw mcp status --verbose should also list clipkit as connected.

Notes#

  • The config is nested under mcp → servers → <name>, not a top-level mcpServers object.
  • The transport value must be exactly streamable-http (hyphenated) — not http, sse, or stdio.
  • Don't add --auth oauth — ClipKit is open, and an OAuth handshake it doesn't expect would fail the probe.

Heads up: OpenClaw moves fast — double-check these exact command and config-key names against OpenClaw's current docs. The connection details (open, no-auth, Streamable HTTP at https://www.clipkit.dev/mcp) are correct regardless of the wrapper syntax.

New to the tools? The MCP server overview has the full tool list and how projects work.