MCP server for LLM Brand Monitor — track how AI models mention your brand
Connect Llm Brand Monitor MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for LLM Brand Monitor — track how AI models mention your brand. The llm brand monitor mcp mcp server is what makes that connection.
Connect Claude, Cursor, Windsurf, or any MCP-compatible client to manage brand monitoring projects, run scans across 350+ LLMs, and analyze results — all through natural language.
Installation goes through your MCP client rather than a global install: point it at @serpstat/llm-brand-monitor-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
lbm_list_projects — List all brand monitoring projectslbm_get_project — Get project details with prompts and modelslbm_create_project — Create a new projectlbm_update_project — Update project name, models, or monitoring settingslbm_archive_project — Archive a projectlbm_add_prompts — Add monitoring prompts to a projectlbm_delete_prompt — Remove a prompt from a projectlbm_run_scan — Start a scan — sends prompts to LLMs and collects responseslbm_get_scan_status — Check scan progresslbm_list_scans — View scan historylbm_list_results — Browse monitoring results (brand mentions, status)lbm_get_transcript — Read the full LLM response for a specific resultConfiguration is passed through the environment: LBM_API_KEY, LBM_API_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Llm Brand Monitor MCP's toolset — lbm_list_projects, lbm_get_project, lbm_create_project and 11 more — is a fair guide to whether it matches your workflow. It is maintained by serpstatglobal; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Llm Brand Monitor MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| lbm_list_projects | List all brand monitoring projects |
| lbm_get_project | Get project details with prompts and models |
| lbm_create_project | Create a new project |
| lbm_update_project | Update project name, models, or monitoring settings |
| lbm_archive_project | Archive a project |
| lbm_add_prompts | Add monitoring prompts to a project |
| lbm_delete_prompt | Remove a prompt from a project |
| lbm_run_scan | Start a scan — sends prompts to LLMs and collects responses |
| lbm_get_scan_status | Check scan progress |
| lbm_list_scans | View scan history |
| lbm_list_results | Browse monitoring results (brand mentions, status) |
| lbm_get_transcript | Read the full LLM response for a specific result |
| lbm_list_competitors | See which competitor brands LLMs mention |
| lbm_list_links | See which URLs and domains LLMs cite |
{
"mcpServers": {
"lbm": {
"command": "npx",
"args": ["-y", "@serpstat/llm-brand-monitor-mcp"],
"env": {
"LBM_API_KEY": "lbm_your_key_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LBM_API_KEY | Credential the server authenticates with. | Yes |
| LBM_API_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.