OpenClaw

OpenClaw’s MCP OAuth support is still maturing. Until it is complete, use an API key as a Bearer token instead.

Step 1: Generate an API key

1. Log in to echosift.io.
2. Go to Settings > Integrations.
3. Click Create API key, give it a name (for example “OpenClaw”), and copy the full key. It is shown only once.

Keys follow the format es_<prefix>_<secret> and require a Pro subscription.

Step 2: Configure OpenClaw

In your OpenClaw MCP server config, set the server URL and pass the key as a Bearer token in the Authorization header:

{
  "mcpServers": {
    "echosift": {
      "url": "https://mcp.echosift.io/mcp",
      "headers": {
        "Authorization": "Bearer es_YOUR_KEY_HERE"
      }
    }
  }
}

Replace es_YOUR_KEY_HERE with the full key you copied in step 1.

Security note

Store the key in your secret manager or environment, not in a config file you commit to version control. Revoke it from Settings > Integrations at any time.

When OAuth is ready

Once OpenClaw ships stable OAuth 2.1 PKCE support, you will be able to remove the headers block and use the URL alone, just like Claude Code and Cursor.