Connect Eklow to an AI assistant

Connect an AI assistant such as Claude, and you can ask it questions like “Which campaign has the best reply rate?” or “Which of my mailboxes are not ready to send?”.

The assistant can only read. It cannot send email, start or pause campaigns, or change anything.

To let it in, you give it an API key: a password that lets another app read your Eklow data. Each key reads one workspace.

Set it up in 3 steps

1. 1

   Open Settings → AI assistant (MCP), or AI assistant in the sidebar. You need to be a workspace admin or owner.

2. 2

   Under Create a key, press Create key. Press Copy key: it is shown only once. The key is named “AI assistant” and expires in one year.

3. 3

   Under Add it to your assistant, pick Claude, Claude Code, Gemini, ChatGPT or Other MCP client and follow the steps. Your key is already filled in. Eklow tests the connection for you under Test connection.

Add Eklow to Claude

These steps work on the Claude website and in the Claude desktop app.

1. 1

   In Claude, open Customize → Connectors.

2. 2

   Press + Add, then Add custom connector.

3. 3

   Enter the name Eklow and paste your Server URL. Press Continue.

4. 4

   Under Authentication, choose No sign in.

5. 5

   Under Request headers, add a header named Authorization with the value Bearer followed by your key, for example Bearer sc_….

6. 6

   Press Add.

On a Claude Team or Enterprise plan, an owner adds the connector under Organization settings → Connectors. Everyone who uses it then shares that one key, so they all read the same workspace.

Gemini

Antigravity CLI

Antigravity CLI replaced Gemini CLI for free and Google One accounts on June 18, 2026. Add Eklow to ~/.gemini/config/mcp_config.json, then run /mcp in Antigravity CLI to check the connection.

{
  "mcpServers": {
    "eklow": {
      "serverUrl": "https://app.eklowlab.com/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Antigravity CLI has no mcp add command, and it reads serverUrl, not httpUrl.

Gemini CLI (paid accounts)

Run this in your terminal, then /mcp in Gemini CLI to check the connection.

gemini mcp add -s user --transport http eklow https://app.eklowlab.com/api/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Or add it to ~/.gemini/settings.json:

{
  "mcpServers": {
    "eklow": {
      "httpUrl": "https://app.eklowlab.com/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Gemini's app connects with sign-in, which isn't available yet.

ChatGPT

ChatGPT's app connects with sign-in, which isn't available yet. Codex works: see “For developers” below.

What happens next

Ask your assistant a question about Eklow. It looks up what it needs and answers in plain words.

Good questions to start with: “Summarize this week's replies”, “Which campaigns are active and how are they doing?”, “Is acme.com verified?”, “What do we know about [email protected]?”.

What your assistant can read

• Your campaigns and their status.
• The numbers for one campaign: sends, opens, clicks, replies, bounces and unsubscribes.
• Your latest replies: who sent them, the subject and the first part of the message.
• Your connected mailboxes, their warmup and whether they are ready to send. Never their passwords.
• Your sending domains and whether they are verified.
• One contact, looked up by email address.

Keeping your data safe

• It can only read. Nothing your assistant does can send, change or delete anything.
• One workspace per key. The assistant reads only the workspace the key belongs to.
• Your sign-in stays private. The assistant uses the key, never your own Eklow sign-in.
• You can cut it off. Revoke the key in Settings → API keys and the assistant loses access straight away. A key also stops working when the person who created it leaves the workspace, is removed or is suspended.
• Where the data goes. What your assistant reads goes to the company that runs it, under its terms. Connect only assistants you trust with campaign and contact data. Use a separate key for each one.

Test the connection

Right after you create a key, Eklow tests it for you. To test another key, paste it under Test connection and press Test connection. The key is used for that one check and never stored.

Troubleshooting

AI assistant access is being switched on workspace by workspace. If yours is not on yet, the test says so. Contact support to turn it on.

Disconnect an assistant

Revoke its key in Settings → API keys. The assistant loses access straight away.

For developers

Eklow runs a read-only remote MCP (Model Context Protocol) server over Streamable HTTP. It accepts only an Eklow API key as Authorization: Bearer sc_…, never the dashboard session cookie. In Settings → AI assistant (MCP), each assistant under Add it to your assistant shows the steps below with your URL and key filled in.

Claude Code

claude mcp add --transport http eklow https://app.eklowlab.com/api/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Run /mcp in Claude Code to check the connection.

Claude Desktop config file

Instead of Customize → Connectors, you can add Eklow to the config file. This needs Node.js. Open Settings → Developer → Edit Config, add the block below, then quit and reopen Claude Desktop.

{
  "mcpServers": {
    "eklow": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://app.eklowlab.com/api/mcp", "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer YOUR_API_KEY" }
    }
  }
}

Codex

Add the server to ~/.codex/config.toml, then set the key in your shell before starting Codex.

[mcp_servers.eklow]
url = "https://app.eklowlab.com/api/mcp"
bearer_token_env_var = "EKLOW_API_KEY"

export EKLOW_API_KEY=YOUR_API_KEY

Responses API

[
  {
    "type": "mcp",
    "server_label": "eklow",
    "server_url": "https://app.eklowlab.com/api/mcp",
    "headers": { "Authorization": "Bearer YOUR_API_KEY" },
    "require_approval": "never"
  }
]

Any other MCP client

• Transport: Streamable HTTP (remote server).
• URL: https://app.eklowlab.com/api/mcp.
• Header: Authorization: Bearer YOUR_API_KEY.

Tools

Logging, limits and error codes

• Every tool call is logged against the key: the tool, the outcome, a fingerprint of the arguments, the number of rows and the time taken. Never the arguments or results themselves.
• 60 requests a minute per key and 300 per workspace.
• Reply, contact and campaign text is marked untrusted, with links and images removed.
• Error codes: unauthorized, api_key_expired, api_key_owner_inactive, mcp_not_enabled, plan_feature_unavailable, feature_unavailable, workspace_unavailable, rate_limited, origin_not_allowed.