MCP (Model Context Protocol) is an open standard that lets AI assistants such as Claude, Cursor, and ChatGPT connect directly to outside data sources. LiveMentions runs its own MCP server, so you can ask your AI assistant about your brand's AI visibility — visibility scores, competitor comparisons, cited sources, optimization recommendations, and more — straight from the tool you already use for work, without opening the LiveMentions dashboard.

Under the hood, your AI assistant connects using a personal access token instead of your normal LiveMentions login, so it only ever gets access to your own account's data, scoped exactly the same way the dashboard is.

Who has access

MCP / API access is available to any account with an active, paid LiveMentions subscription, on any plan. It is not available on a free trial or a beta-access account. If your account is not eligible yet, the MCP / API tab in Settings will show an upgrade prompt instead of the token screen described below.

Creating a personal access token

1. In the LiveMentions dashboard, go to Settings, then open the MCP / API tab.
2. Under Personal access tokens, click Create token.
3. Give it a name you will recognize later, for example “Claude Desktop” or “Work laptop”.
4. Choose how long the token should last — 7, 30, 60, or 90 days, or Never.
5. Click Create token to confirm.

Your new token is shown once, in full. Copy it immediately and store it somewhere safe, like a password manager — LiveMentions never shows the complete token again after you close that dialog. If you lose it, you cannot recover it; revoke it on the MCP / API tab and create a new one instead.

Connecting Claude Desktop

Claude Desktop connects to remote MCP servers through its configuration file. Open Claude Desktop’s settings, find the option to edit its MCP configuration (Settings → Developer → Edit Config), and add an entry like this, replacing YOUR_TOKEN with the token you copied above:

{
  "mcpServers": {
    "livementions": {
      "url": "https://api.livementions.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Save the file and restart Claude Desktop. LiveMentions should now appear as a connected tool the next time you start a chat.

Connecting Claude Code

From a terminal, run:

claude mcp add --transport http livementions https://api.livementions.com/api/mcp --header "Authorization: Bearer YOUR_TOKEN"

Replace YOUR_TOKEN with your personal access token. Claude Code will confirm the server was added, and it will be available in your next session.

Connecting Cursor

Cursor reads MCP servers from an mcp.json file (either a global one for your user, or a .cursor/mcp.json file inside a specific project). Add an entry in the same shape as Claude Desktop’s:

{
  "mcpServers": {
    "livementions": {
      "url": "https://api.livementions.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Save the file, then reload Cursor’s MCP servers from its settings panel (or restart Cursor).

Connecting ChatGPT or other MCP clients

Any MCP client that supports a remote HTTP server with a custom header can connect the same way: set the server URL to https://api.livementions.com/api/mcp and add an Authorization header with the value Bearer YOUR_TOKEN. Exact steps vary by app, and change over time as these tools evolve, so check that app’s own documentation for adding a custom or remote MCP server if what you see does not match the examples above.

What you can ask your AI assistant

Once connected, your AI assistant can look up:

• Which projects (brands/domains) are tracked on your account
• A visibility report for a project — overall score, share of voice, sentiment, and the visibility trend over time
• The actual prompts being tracked and the most recent AI answer for each, including which sources were cited
• Which domains and pages AI models cite most often for a project
• A prioritized list of recommendations and citation-gap opportunities for improving AI visibility
• How a project compares against its tracked and organically-mentioned competitors
• Every competitor record for a project, tracked or not
• Gap analysis: the websites and pages AI relies on without naming your brand, and the questions where another brand is named instead (the get_gap_analysis tool)
• Crawlability: which AI crawlers your robots.txt lets in, bot by bot, with the rule that decides each one (the get_crawlability tool)
• What you wrote in Brand Context for a project: tone of voice, positioning, claims to make and avoid, glossary and competitor notes, plus the knowledge base passages that match a question

It can also make a small set of safe changes on your behalf:

• Rename a topic, or change its status
• Pause, archive, or reactivate a tracked prompt
• Mark a competitor as tracked or untracked

Your AI assistant cannot create new topics or prompts through MCP. Creating those still happens in the LiveMentions dashboard, since it also triggers a new round of AI tracking on your account.

Gap analysis and Crawlability through MCP

Two read-only tools give your AI assistant the same numbers as the Gap analysis and Crawlability pages. They use no AI credits and have the same access as the other MCP tools: an active paid subscription, with no new setup. The connection is the same one you already created.

get_gap_analysis

Returns the same numbers as the Gap analysis page. Your assistant can choose:

• The list: websites, pages or questions.
• A date range, the last number of days you ask for. With no range it uses all time, which is read as the last 365 days, the same as on the page.
• One AI engine.
• Only the rows that name at least a chosen number of your tracked competitors.
• A question status filter for the questions list, such as questions with a gap.

It can also return the detail for one website: its uses over time, its top pages and the questions it helped answer. The tool only reads results that LiveMentions has already stored. It never starts reading pages.

get_crawlability

Returns the same information as the Crawlability page: how many of the main-list AI bots are fully open, partly restricted or blocked, every bot with its type, its status and the rule that decides it, the pages checked from your sitemap, and the last results for your tracked competitors. The tool only reads.

Example questions

• Which websites leave my brand out of AI answers?
• Which questions name a competitor and not my brand?
• Which pages name two or more of my competitors and not me?
• For ChatGPT only, where am I left out?
• Is any AI search bot blocked on my site?
• Which AI bots does my robots.txt shut out, and by which rule?
• What does a competitor's robots.txt allow?

Your assistant answers from stored results. A project that has never been opened on the Crawlability page has no stored check yet, and the assistant says so.

Managing and revoking tokens

The MCP / API tab lists every active token on your account, when it was last used, and when (if ever) it expires. You can create as many tokens as you like — a separate one per device or app is good practice, since it lets you revoke access for a single tool without affecting the others.

Revoking a token takes effect immediately: the next request made with it is rejected, whether that request comes a second later or after the token has been sitting unused for weeks. A token also stops working on its own once it reaches its expiration date, with no action needed from you.

Keep your token safe

Treat a personal access token exactly like a password. Anyone who has it can read your account’s AI-visibility data through MCP, and use the handful of write actions listed above. Do not share it, and do not paste it into a public repository, chat, or document. If you think a token may have leaked, revoke it right away from the MCP / API tab and create a new one.

Troubleshooting

My AI assistant says it cannot connect. Double-check that the token was pasted in full, with no extra spaces, and that the header is written exactly as Authorization: Bearer YOUR_TOKEN (capital "Bearer", one space before the token).

I get an error about my plan. MCP / API access requires an active, paid subscription. Trials and beta-access accounts are not eligible — upgrade from Settings to unlock it.

It worked before but stopped. The token may have expired or been revoked. Open the MCP / API tab in Settings to check its status, and create a new one if needed.