Client guide · verified August 9, 2026

Connect OpenClaw to the public MCP server

Save the public endpoint under OpenClaw’s mcp.servers configuration, then probe the connection and inspect its read-only tools before relying on the integration.

1 · Configure

Use OpenClaw’s MCP command to add a remote server named ai-redteam with Streamable HTTP transport.

https://www.ai-redteam.com/mcp
Recommended CLI setup
openclaw mcp set ai-redteam '{"url":"https://www.ai-redteam.com/mcp","transport":"streamable-http"}'
Equivalent OpenClaw configuration
{
  "mcp": {
    "servers": {
      "ai-redteam": {
        "url": "https://www.ai-redteam.com/mcp",
        "transport": "streamable-http"
      }
    }
  }
}

This is OpenClaw’s current configuration shape. A top-level mcpServers object is used by some other MCP clients, but is not the OpenClaw Gateway configuration.

2 · Verify
Live connection check
openclaw mcp doctor ai-redteam --probe
  1. Confirm that the probe connects over Streamable HTTP and reports six tools plus resource and prompt support.
  2. Run a harmless search_insights or get_latest request and inspect the returned source links.
  3. OpenClaw normally hot-applies changes under mcp.*. Use openclaw mcp reload if an existing process still holds an older runtime.
  4. If the server connects but tools are absent from a sandboxed agent, allow bundle-mcp in tools.sandbox.tools.alsoAllow.

Older OpenClaw releases without doctor or probe can still confirm the saved entry with openclaw mcp show ai-redteam. Upgrade before depending on automated connection diagnostics. See the official OpenClaw MCP reference for the current command surface.

Security note: the endpoint is public and read-only. No credentials are required, and a client should not send private prompts, secrets, or local files to test connectivity.