Browse the documentation
Authentication
MCP clients such as Claude and Codex sign in with your MentionBird.ai account. The REST API takes an API key, and so can any MCP client that doesn't sign in.
Sign in from an MCP client
Add https://mcp.mentionbird.ai/mcp to the app and sign in when it asks. On the sign-in screen you pick the workspace the app can read. Tick Allow changes if it should also be able to add, change, archive and permanently remove things in that workspace, and start agents that spend its credits.
- Claude (claude.ai, Claude Desktop, Cowork): open Settings → Connectors, click Add custom connector, paste the URL and click Connect. Keep the sign-in options Claude detects. On a Claude Team or Enterprise plan, an owner adds the connector under Organization settings → Connectors first, and each member then clicks Connect on it.
-
Claude Code: add the server, then sign in. If you set MentionBird up with an API key before, remove that entry first with
claude mcp remove mentionbird.claude mcp add --scope user --transport http mentionbird https://mcp.mentionbird.ai/mcp claude mcp login mentionbird -
Codex: add the server, then sign in. If you set MentionBird up with an API key before, remove that entry first with
codex mcp remove mentionbird.codex mcp add mentionbird --url https://mcp.mentionbird.ai/mcp codex mcp login mentionbirdCodex doesn't ask you to sign in again when it needs to make a change. If you didn't tick Allow changes, run
codex mcp login mentionbirdand tick it. If Codex still refuses the next change, ask again.
Each connection reads one workspace. To connect another, add the server again and pick the other workspace when you sign in. Name each one after its workspace, so you and the app can tell them apart. In Claude, call the second connector something like MentionBird Acme and give it the URL https://mcp.mentionbird.ai/mcp?workspace= with any label after the equals sign, because Claude doesn't allow two connectors with the same URL. In Claude Code and Codex, add it under a name like mentionbird-acme.
Your signed-in apps are listed under Connected apps on the API & integrations page. Disconnect one there and it stops working on its next request. Removing the connector in Claude or logging out in Codex stops that app from using it, but MentionBird isn't notified, so it stays listed until you disconnect it there or it goes unused for 90 days.
Signing in works on the MCP server only. The REST API below takes an API key.
Create an API key
Every REST endpoint except the OpenAPI spec itself needs an API key.
Open API & integrations in the app (MCP in the sidebar) and create one. Keys start with lmvz_live_.
The key is shown once, when you create it. We store only a hash, so if you lose it you create a new one.
A key belongs to one workspace and reads only that workspace's data.
Send the key
Pass it as a bearer token in the Authorization header. This is the only way to authenticate — there is no API key query parameter and no X-API-Key header.
curl -H "Authorization: Bearer lmvz_live_your_key_here" \
"https://api.mentionbird.ai/api/v1/brands/tracked"
Read keys and write keys
New keys are read-only. A read-only key can call every GET endpoint and gets a 403 on every POST endpoint, since those are the ones that change something.
Turn on write access per key when you create it. A write key can track and archive brands, add, change and archive prompts, change their AI platforms and tags, add, change and permanently remove tag definitions, competitors, aliases and owned domains in its workspace, and start ranking advice and YouTube video summaries, which spend the workspace's credits. Archiving a prompt or a brand keeps its history and can be undone. Removing a competitor, alias, owned domain or tag is permanent.
Plan access
API and MCP access is included on every paid plan. On a free plan, every endpoint returns 403, and the sign-in screen won't let you pick that workspace. You can see your plan on the billing page.