Connect over MCP

Kreel’s MCP server exposes your brand performance data to AI agents. Once connected, your agent can call Kreel’s tools directly from your chat client, for example to pull performance, compare periods, or check for anomalies. See Connect your agent for how MCP compares to the kreel CLI and the Claude Code plugin, and for what a connected agent can do once it’s in.

Before you start

You need:

A Kreel account with at least one connected brand.
An MCP-capable client: Claude (web, desktop, or Cowork), Claude Code, ChatGPT (Business or Enterprise, with Developer mode enabled), or another client that supports remote MCP connectors.

The MCP URL

Kreel’s MCP server is available at:

https://api.kreel.ai/mcp

Every client below connects to this same URL. It accepts either an OAuth login (recommended) or a workspace API key as a Bearer token.

Connect by URL (recommended)

This is the fastest path for clients that support remote MCP connectors. There is no config file to edit and no key to paste - you add the URL and approve a login popup.

In Claude, go to Settings → Connectors → Add custom connector.
Paste the URL: https://api.kreel.ai/mcp.
Click Connect.
A Kreel login window opens once. Sign in and approve access.
The Kreel tools appear in your chat.

In ChatGPT, go to Settings → Connectors → Advanced → Developer mode.
Add the URL: https://api.kreel.ai/mcp.
Sign in to Kreel when prompted and approve access.

Run:

claude mcp add --transport http kreel https://api.kreel.ai/mcp

Claude Code opens a login window and handles the OAuth flow for you. You don’t need an API key for this command.
Confirm it connected:
Terminal window
```
claude mcp list
```

What you’re approving

The login popup asks you to grant scopes to the agent:

Read - view your connected brands’ performance data. Always required.
Write - update the Brand Knowledge Base (profile, sections, competitors, learnings) and create drafts or report uploads. Optional, checked by default.

Uncheck Write if you want this agent limited to read-only access.

Connect with an API key instead

Use this path for stdio-only MCP clients, or when you specifically want to authenticate with an API key rather than the OAuth popup. It runs a small local bridge, @kreel-ai/mcp, that talks to your client over stdio and forwards each request to the same https://api.kreel.ai/mcp endpoint, using your key for authentication.

Claude Desktop
Claude Code

In Claude Desktop, go to Settings → Developer → Edit config.

Add Kreel to claude_desktop_config.json:

{
  "mcpServers": {
    "kreel": {
      "command": "npx",
      "args": ["-y", "@kreel-ai/mcp@latest"],
      "env": { "KREEL_API_KEY": "kreel_live_your_key_here" }
    }
  }
}

Save the file.
Fully quit Claude Desktop (Cmd+Q) and reopen it.

Run:

claude mcp add kreel \
  -e KREEL_API_KEY=<your-api-key> \
  -- npx -y @kreel-ai/mcp@latest

Confirm it connected:
Terminal window
```
claude mcp list
```

Verify it works

Ask your agent to list the brands you can reach:

List my Kreel brands.

If the connection works, your agent calls the list_brands tool and returns the brands your account can access. A logged-in connection reaches every brand across every workspace you belong to; an API key only reaches brands in the one workspace it was created in. If you can reach more than one, tell the agent which one you mean by name on each question.

From there, try a real question, for example:

What’s my 7-day MER, and which Meta campaign tanked yesterday?

Next steps

Browse the prompt library for ready-made prompts you can paste in.
Install the Claude Code plugin to run those prompts as /kreel:* slash commands.
See Data tools, Query, and Brand context tools for what each tool does.

Need help?

Email support@kreel.ai.