MCP server
Query your AgentMention data from an AI client over the Model Context Protocol — brands, prompts, metrics, citations and audits as tools.
AgentMention exposes its data over the Model Context Protocol, so an MCP-capable AI client can read your visibility data directly. Instead of exporting a dashboard, you ask your assistant "which prompts did we lose this week, and what sources won them?" and it queries the account itself.
Connecting
- Open Settings → MCP.
- Follow the connection instructions for your client.
- Authorise the connection when your client opens the authorisation page.
- Restart the client fully. Most clients cache the tool list on connect, so a partial restart leaves them unaware of the new tools.
Connected clients and issued tokens are listed in the same tab, and either can be revoked at any time.
What a client can query
The tools mirror the tabs in the app, so what you can see you can ask for:
| Area | What you can ask for |
|---|---|
| Brands | Your brands and their configuration, and the competitors suggested for them |
| Topics & prompts | The groups you track and the prompts inside them |
| Visibility & reports | Visibility metrics, competitor comparison, citations, and individual reports |
| Site audits | Schema and technical results page by page, and the robots.txt audit |
The exact tool names are listed in Settings → MCP once you connect, and any MCP client will enumerate them for you on request.
Access is read-only: the tools query data, they do not change your configuration.
What it is good for
- Cross-cutting questions that would otherwise mean switching tabs — "compare our position against each competitor per topic, and list the sources that explain the gaps".
- Drafting from real data. A brief that cites the actual prompts you lose and the pages that beat you, rather than a summary of a summary.
- Recurring reporting. Let the client assemble the same weekly digest instead of exporting by hand.
Security notes
- Tokens carry your access. Anyone holding one can read what you can read. Revoke them when a device or client is no longer in use.
- Revoke rather than share. Issue a connection per client instead of reusing one token in several places, so revocation stays precise.
- Role limits apply. A viewer's connection is read-only in the same way their account is — see Team roles.
Troubleshooting
The client shows no tools. Quit it completely and reopen, then ask it to list available tools. Cached tool lists are the usual cause.
Authorisation fails or expires. Reconnect from Settings → MCP; the authorisation page must be opened while signed in to AgentMention.
A tool returns nothing. Usually a scope issue rather than a failure — check the brand and period the tool was called with, exactly as you would check the dashboard filters.
Related
- Settings — where connections are managed
- Team roles — what a connection can access
Updated 2026-08-03