MentionsAPI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MENTIONSAPI_KEY | Yes | Your MentionsAPI API key (looks like lvk_live_...) | |
| MENTIONSAPI_URL | No | The base URL of the MentionsAPI server | https://api.mentionsapi.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mentions_checkA | Check whether a brand is mentioned across AI search surfaces. 8 shippable modes: mode:quick ($0.39 fresh, $0.02 on cache hits) queries 4 LLM engines in parallel; mode:perplexity_live ($0.25), mode:chatgpt_live ($0.10), mode:gemini_live ($0.10), mode:ai_overview ($0.05), mode:ai_mode ($0.10), mode:bing_copilot ($0.05) each hit one live UI surface for ground-truth citations + fan-out queries; mode:all_live ($0.50) bundles all 6 live surfaces in one call. Returns mentions, ranks, citations, fan-out queries, and brand entities per surface. |
| mentions_watchB | Set up a persistent monitor that webhooks you when brand mentions, ranks, or citations change. |
| mentions_discoverB | Suggest queries to track for a given brand. Returns ~50 candidate queries spanning informational, commercial, and comparison intents. |
| mentions_compareC | Compute the delta between two queries OR two brands. Useful for competitor analysis. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: checking mentions, comparing queries/brands, discovering queries, and setting up persistent monitors. No overlap in functionality.
All tool names follow a consistent 'mentions_verb' pattern, making it predictable and easy to understand the action each tool performs.
Four tools appropriately cover the core functionality of the MentionsAPI server: query, compare, discover, and monitor. Neither too few nor too many.
The tool set covers the main use cases, but lacks a tool to manage or delete existing watches, which is a minor gap.