MentionBird

npx add-mcp 'https://mcp.mentionbird.ai/mcp'

Most AI apps connect to MentionBird by signing in: you give the app one address, sign in with your MentionBird login, and choose a workspace. There's no key to create or paste. That's how Claude, Claude Code and Codex connect.

The address is the same for everyone:

https://mcp.mentionbird.ai/mcp

MentionBird has the same steps with your workspace's name already filled in: click MCP in the sidebar and open the Connect an AI app tab. ChatGPT has its own article — see Connecting MentionBird to ChatGPT.

The first time you connect, your app opens a MentionBird sign-in page in your browser. Sign in, then:

1. Choose the workspace. The connection reads that one workspace and nothing else. A workspace whose plan doesn't include MCP access is shown greyed out.
2. Decide on Allow changes. Ticked, the app can add brands and prompts. Unticked, it can only read. Either way it can never edit or delete anything.
3. Click Allow.

You're sent back to your app, which stays signed in from then on and renews its access in the background.

Claude

This works in Claude on the web, in the desktop app and in Cowork.

1. Open Settings → Connectors and click Add custom connector.
2. Name it MentionBird — add the workspace name if you'll connect more than one — and paste the address above. Keep the sign-in options Claude detects.

On a Claude Team or Enterprise plan, an owner adds the connector first under Organization settings → Connectors. Each member then clicks Connect on it and signs in with their own MentionBird login.

Claude Code

Run these two commands:

claude mcp add --scope user --transport http mentionbird https://mcp.mentionbird.ai/mcp

The Connect an AI app tab has the same commands with your workspace in the name — copy from there if you'll connect more than one. If Claude Code later says MentionBird needs authentication, run /mcp, pick the MentionBird entry and choose Authenticate.

Codex

codex mcp add mentionbird --url https://mcp.mentionbird.ai/mcp

If Codex says MentionBird's tools are unavailable, codex mcp login mentionbird signs you back in.

Letting the app make changes later

If you left Allow changes unticked, you can add it whenever you need it:

• Claude and Claude Code ask you to sign in again the first time they need to add something — tick it then.
• Codex keeps the access you chose at sign-in. Run codex mcp login mentionbird again and tick it. If Codex still declines the next change, ask again.

Connecting more than one workspace

Each connection reads one workspace. To connect another, switch to it in MentionBird and follow the steps on its own Connect an AI app tab, where the names are that workspace's. Naming each entry after its workspace — mentionbird-acme, mentionbird-globex — lets you and your assistant tell them apart.

Claude keeps one connector per address, so for a second workspace in Claude, use the address with the workspace added on the end, like https://mcp.mentionbird.ai/mcp?workspace=globex. The Connect an AI app tab shows the exact address for each workspace.

Already connected with an API key?

Remove the old entry before adding the new one, or MentionBird's tools show up twice. In Claude Code that's claude mcp remove mentionbird, and in Codex codex mcp remove mentionbird — or whatever name you gave it. Then revoke the key on the Manage access tab if nothing else uses it.

Cursor and other clients

Cursor, and other MCP clients not listed above, connect with an API key: the same address, with the key sent as a bearer token.

In Cursor, create .cursor/mcp.json in your project — or ~/.cursor/mcp.json to use it everywhere — containing:

{"mcpServers": {"mentionbird": {"url": "https://mcp.mentionbird.ai/mcp", "headers": {"Authorization": "Bearer YOUR_API_KEY"}}}}

Replace YOUR_API_KEY with your key, restart Cursor, and look for the green status dot under Settings → MCP.

Any client that reads a configuration file wants the same two values: the address, and an Authorization: Bearer header carrying your key. Keep those files out of repositories and screenshots — a key is a password to your data.

Claude can connect with a key too, and the Connect an AI app tab has those steps. Signing in is simpler, though, and keeps the secret out of a configuration file.

Checking it works

Ask something only your account could answer. "Which brands am I tracking?" is the simplest test.

If it doesn't connect

Work through these in order:

1. Check the workspace. If it was greyed out on the sign-in screen, its plan doesn't include MCP access — the pricing page shows which plans do.
2. Sign in again. In Claude, click Connect on the connector. In Claude Code, /mcp then Authenticate. In Codex, codex mcp login.
3. Check it wasn't disconnected. A connection ends when someone disconnects it, when you're removed from the workspace, or after a long stretch unused. Signing in again starts a fresh one. See Seeing and disconnecting connected apps.
4. Restart the app. Most read their connector list at startup.

With an API key, an authentication error means the key is incomplete, revoked, or not sent as Bearer. A truncated paste is the most common cause — copying from a wrapped line often loses the end.

A note on app versions

AI apps change their settings screens fairly often, so if a screen doesn't look like you expect, your app's own MCP documentation is the more reliable guide. The address you need from us stays the same.