OpenClaw connection guide

These steps follow the OpenClaw MCP documentation as of November 4, 2026; they have not been run against a live OpenClaw install. Check the current OpenClaw MCP transport reference for syntax supported by your installed version.

Add a remote server entry to the OpenClaw configuration, substituting your deployment origin. Keep transport set as shown, because OpenClaw uses SSE when it is omitted. Do not paste a real key into a committed configuration file:

{
  "mcp": {
    "servers": {
      "agenticmailcenter": {
        "url": "https://YOUR_AGENTICMAILCENTER_ORIGIN/mcp",
        "transport": "streamable-http",
        "headers": {
          "Authorization": "Bearer ${AGENT_API_KEY}"
        }
      }
    }
  }
}

Set AGENT_API_KEY in the environment OpenClaw runs in; header values support ${ENV_VAR} references. Start with a read-scoped key and discover tools before enabling writes. Grant only the scopes and identity mode needed for the workflow. send_with_policy requires approval and passing policy checks; the separately gated send_direct mode can send before review when enabled by the server. The endpoint is tenant-bound.

Verification is non-production and read-only: run openclaw mcp probe agenticmailcenter --json against a test tenant, then revoke the short-lived test key. Do not send outbound email as part of setup verification.