The Semrush MCP server connects Semrush data directly to AI assistants such as Claude and ChatGPT, so SEO research can be run in plain language. Built on the Model Context Protocol, an open standard from Anthropic that gives AI models a universal way to connect to external data sources, files, and tools, the server turns Semrush metrics into answers an assistant can return inside a conversation. This guide groups sixteen Semrush MCP use cases by workflow: keyword strategy, competitive intelligence, content optimization, and diagnostics, with copy-paste prompts ready to adapt.
How do you set up the Semrush MCP?
Setup takes four steps. First, check the plan: MCP access comes with Semrush One Starter, Semrush One Pro+, SEO Classic Pro, and SEO Classic Guru, each including 50,000 API units. Traffic Market reports need a separate Trends API subscription, which matters when the Traffic Analytics prompts come up.
Second, connect from inside the AI client. In Claude, go to Settings, then Connectors, click Add, then Browse Connectors, search for Semrush MCP, and approve the permissions. In ChatGPT, go to Settings, then Apps, find Semrush, and click Connect. Both clients use OAuth, so there is no key to paste.
Third, use the endpoint for other clients. Cursor, VS Code, Gemini, Perplexity, and custom agents connect to https://mcp.semrush.com/v2/mcp with an API key in the Authorization header. The developer docs list the config for each one. For terminal work, Claude Code with Semrush applies the same idea with more automation on top.
Fourth, confirm the connection by asking something cheap, like the Semrush Rank for a domain in the US database. If a number comes back, the connection is live. If there is an error, ask the AI to walk through fixing it.
Every prompt below sits in the Semrush MCP prompt library, where each use case is a workflow of three or four chained prompts. The first prompt in each workflow is featured here because it pulls the data; the full workflow link covers the follow-ups. To use one, paste it, swap in the relevant domain, country, and keywords inside the brackets, run it, and read the output before acting on it.
The MCP pulls live Semrush data on demand and does not monitor anything or send alerts. Anything that needs watching over time, such as rank tracking or competitor alerts, gets set up inside Semrush itself. The MCP is also read-only, so it retrieves data but never changes it.
What keyword strategy workflows does the Semrush MCP unlock?
These search-demand and keyword-strategy prompts uncover where demand in a niche actually sits, which keywords competitors own that a site does not, and which gaps deserve effort first.
Spot shifts in search demand
This prompt maps the niche’s biggest keyword clusters by combined volume before the full workflow layers rising, declining, and SERP-opportunity views on top. Use it when planning a quarter and need to know where demand lives before deciding what to build.
Using Semrush keyword data for {country}: Identify the top 8 keyword clusters for {niche} by combined monthly search volume. Return ONE table: Columns: cluster_name, combined_monthly_volume, example_keywords (up to 5). Limit: 8 clusters exactly.
The output is a table of eight clusters ranked by combined volume. The workflow’s trend prompts then show which clusters are growing.
Turn keyword gaps into roadmaps
This prompt finds keywords competitors rank for that the site does not, plus the ones where the site ranks far behind. The full workflow then clusters them and plans pages. Reach for it when traffic is going to competitors but not through obvious doors.
If {competitor-domains} are provided, use them directly (up to 5). If not, first find {your-domain.com}’s top organic search competitors (limit 5); exclude domains with Competitor Relevance = 0.00 and organic traffic above 10M (e.g., YouTube, Reddit, Wikipedia). Use Semrush data for {country} to analyze {your-domain.com} against its top organic competitors. Find and prioritize two opportunity types: Missing keywords (competitors rank, but {your-domain.com} does not) and Weak shared keywords (both rank, but {your-domain.com} ranks much lower than the strongest competitor). Prioritize low-hanging fruit that look actionable through content or on-page improvements. Return ONE table (up to 50 rows): Columns: keyword, opportunity_type, monthly_volume, intent, top_competitor_domain, competitor_rank, your_rank, rank_gap, recommended_action, rationale.
The result is a 50-row table splitting gaps into missing and weak shared, with a recommended action per row. The workflow’s next prompts cluster the list into themes.
Prioritize gaps by demand and intent
This prompt estimates the search intent mix inside each gap cluster so gaps can be sequenced by business value rather than raw volume. The full workflow carries it through competitor difficulty checks into a six-week sprint plan. Run it as a follow-up once a gap list exists.
Using Semrush keyword data for {country}: For the 8 gap clusters, estimate intent distribution. If gap clusters already exist in this conversation, use them. If no gap clusters are available, first identify keyword gaps for {your-domain.com} against up to 5 competitor domains, then cluster them into exactly 8 themes. Return ONE table: Columns: cluster_name, informational_share_pct (est), commercial_share_pct (est), transactional_share_pct (est), top_intent_keywords (up to 5). Limit: 8 rows. If intent labels are unavailable, infer from SERP/page types and label as estimate.
The output is an eight-row table of estimated intent shares per cluster. Spot-check a SERP or two before trusting the roadmap, since the intent figures are model-generated estimates.
How does the Semrush MCP support competitive intelligence?
These competitive-intelligence prompts identify who a site actually competes with in search, how traffic splits, who is growing, and how to watch them without living in dashboards.
Identify true search competitors
This prompt ranks the domains sharing keywords by Semrush’s Competitor Relevance score rather than by assumed competitors. The full workflow maps overlap clusters and SERP feature wins next.
Using Semrush data for {country}: Identify the top 10 organic competitors of {your-domain.com}, excluding high-traffic generic domains (Competitor Relevance = 0.00 or organic traffic above 10M, e.g., YouTube, Reddit, Wikipedia). Return ONE table: Columns: competitor_domain, estimated_organic_traffic, ranking_keywords, keyword_overlap_with_{your-domain.com}, overlap_pct (if available). Limit: top 10 competitors.
The output is a 10-row table with traffic, keyword counts, and overlap per domain. Those names feed the next four prompts.
Prioritize strengths, gaps, and attacks
This prompt finds clusters where the site is strong and competitors are weak, so the focus is on defending strengths before chasing new ones. The full workflow ends in a defend-versus-attack map.
Using Semrush data for {country}: Identify keyword clusters where {your-domain.com} has relatively strong visibility but the top 5 competitors have weaker presence. If a previous competitor focus or cluster analysis exists in this conversation, use it as a starting point. Return ONE table: Columns: unique_cluster, why_unique (1 sentence), example_keywords (up to 5), suggested_defense_action. Limit: 8 clusters.
The output lists up to eight clusters where the site leads, each with a defense action. The workflow’s next prompts then show where competitors outrank the site.
Size traffic share across competitors
This prompt pulls each domain’s traffic and engagement and computes market share. It calls Traffic Analytics, which needs a Trends API subscription; the full workflow continues into channel and geography splits.
For each competitor domain ({competitor-domains}) in {country}, use Semrush Traffic Analytics to retrieve each domain’s overall traffic summary (visits, unique visitors, engagement). It accepts multiple domains per request. If {competitor-domains} are not provided, use competitor domains identified earlier in this use case as top organic/search competitors, market competitors, or strongest keyword-overlap competitors. Combine, dedupe, and limit to 5. Request columns: target, rank, visits, users, pages_per_visit, bounce_rate, time_on_site. Build a single comparison table: Domain, Rank, Visits, Unique Visitors, Pages/Visit, Bounce Rate, Avg Duration (s), Traffic Share %. Derive: total_market_traffic (sum of all visits), market_leader (domain with highest visits), traffic_concentration (combined traffic share of top 2).
The result is a share-of-market table with total market traffic, the market leader, and top-two concentration. On a plan without the Trends API, the MCP reports the gap and falls back to organic estimates, so a low_data engagement column usually means the plan, not a broken prompt.
Find competitors gaining organic traffic
This prompt pulls 12 months of traffic history per competitor and ranks them by absolute growth. The full workflow turns the winners’ patterns into playbooks.
Using Semrush data for {country} over the last 12 months, identify the top 10 competitors of {your-domain.com} by organic traffic growth. Process: find the top organic competitors, select top 10 by keyword overlap or competitive relevance (exclude domains with Competitor Relevance = 0.00 and Organic Traffic above 10M). For each competitor, pull its organic traffic trend over time. Extract traffic_12m_ago and traffic_now. Compute traffic_change_abs and traffic_change_pct. Flag any competitor where traffic_12m_ago is below 100 as low_data, since percentage growth from a tiny base is misleading. Determine the top_growth_cluster driving traffic growth. Return ONE table: Columns: competitor_domain, traffic_change_abs, traffic_change_pct, top_growth_cluster. Limit: top 10 by traffic_change_abs.
The output is a growth leaderboard with the cluster driving each gain. The low_data flag matters, because percentage growth from a tiny base will otherwise top the table.
Track competitor visibility shifts
To track visibility shifts, set the watch list first. This prompt builds a monitoring table of the 10 most relevant competitors and the cluster each competes on. The full workflow establishes the baseline that shifts are measured against.
Using Semrush data for {country}: Identify the top 10 organic competitors of {your-domain.com} to monitor. Sort by competitor relevance (Cr) descending. Return ONE table: Columns: competitor_domain, estimated_organic_traffic, keyword_overlap (if available), primary_competing_cluster. Limit: 10 competitors.
The result is a compact watch list. Regenerate the list monthly and hand it to the alerts prompt below.
Build alerts and response plays
This prompt produces alerts for when a competitor gains rankings or when the site loses them. The MCP writes the rules but cannot create alerts; the output goes into Semrush, for example as Position Tracking campaigns. The full workflow adds response playbooks.
Create a competitor monitoring alert ruleset for {your-domain.com} in {country}. Do NOT generate alerts for {your-domain.com} gains; the purpose is early warning, not reporting success. Cover two signal categories: competitor_gain (a monitored competitor gains organic traffic, rankings, or visibility above threshold in clusters overlapping with {your-domain.com}) and own_loss ({your-domain.com} drops in rankings, traffic share, or keyword visibility in a monitored cluster). Return ONE table: Columns: alert_name, signal_type (competitor_gain / own_loss), metric, threshold, cadence, action_owner_role, what_to_investigate. Include at least 8 alert rules: minimum 5 of type competitor_gain, minimum 2 of type own_loss.
The result is a rules table with thresholds, cadences, and owners. If the prompt runs in the same conversation as the earlier competitive prompts, the AI calibrates against real baselines in the conversation and every threshold carries both a percentage and an absolute floor instead of a generic number. Backtest it against a prior year’s data before accepting the output.
FAQ
What is the Semrush MCP server?
The Semrush MCP server connects Semrush data directly to AI assistants such as Claude and ChatGPT, so users can run real SEO research in plain language through the Model Context Protocol (MCP), an open standard created by Anthropic that lets AI models connect to external data sources, files, and tools.
Which Semrush plans include MCP access?
MCP access comes with Semrush One Starter, Semrush One Pro+, SEO Classic Pro, and SEO Classic Guru, each including 50,000 API units. Traffic Market reports need a separate Trends API subscription.
Which AI clients support the Semrush MCP endpoint?
Claude and ChatGPT connect through their built-in connectors using OAuth. Cursor, VS Code, Gemini, Perplexity, and custom agents connect to https://mcp.semrush.com/v2/mcp with an API key in the Authorization header.
Does the Semrush MCP monitor or send alerts?
No. The MCP pulls live Semrush data on demand and does not monitor anything or send alerts. Anything that needs watching over time, such as rank tracking or competitor alerts, must be set up inside Semrush itself.
Try the rank tracker

The rank tracker runs a full technical audit of a site and shows the measured result behind every check. Open the rank tracker.
This article summarizes reporting from semrush.com.