Semrush MCP Server
Connect AI agents to Semrush's live SEO, keyword, and competitive intelligence data via MCP.
Updated
What is Semrush MCP?
The Semrush MCP server is a Model Context Protocol server that lets AI agents query Semrush's SEO and competitive-intelligence data — keywords, domain analytics, backlinks, rank tracking, and traffic trends — in real time during a conversation or workflow.
It is an official, Semrush-hosted remote server reachable at https://mcp.semrush.com/v1/mcp. Authentication uses OAuth 2.0 by default: when you connect, the agent registers with Semrush's OAuth system and redirects you to the Semrush login to authorize. Agents that don't support OAuth can instead pass a Semrush API key in the Authorization header (Apikey YOUR_API_KEY).
Access is read-only — agents can retrieve Semrush data but cannot modify it — and every query consumes API units from your existing Semrush subscription. The server surfaces Semrush's Trends API, SEO API, and read-only Projects API methods, so an agent can pull the same intelligence available through the REST API without leaving its chat or workflow context.
Tools the Semrush MCP server exposes
| Tool | What it does |
|---|---|
| organic_research | Analyze a domain's organic search performance — rankings, organic keywords, and estimated traffic. |
| keyword_research | Pull keyword metrics: search volume, difficulty, intent, CPC, and related suggestions. |
| backlink_research | Inspect a domain's backlink profile, referring domains, and authority signals. |
| trends_research | Retrieve traffic and market-trends data (requires a Trends API subscription). |
| get_report_schema | Introspect a report's required parameters (e.g. domain, country, timeframe) before running it. |
| execute_report | Run a Semrush report and return the live data for the agent to analyze. |
Connect the Semrush MCP server
Claude Code
- 1
Add the remote server
Run: claude mcp add --transport http semrush https://mcp.semrush.com/v1/mcp
- 2
Authenticate with OAuth
On first use, Claude Code opens the Semrush login/authorization page. Approve access to link your Semrush account.
- 3
Verify the connection
Run /mcp in Claude Code to confirm Semrush is connected, then ask the agent for keyword or domain data.
Cursor
- 1
Open MCP settings
Go to Cursor Settings > MCP > Add new MCP server (or edit ~/.cursor/mcp.json).
- 2
Add the Semrush server
Add an HTTP server entry with url https://mcp.semrush.com/v1/mcp.
- 3
Authorize via OAuth
Cursor prompts you to sign in to Semrush; complete the OAuth flow to grant read-only access.
- 4
Use it
Confirm the server shows as connected in MCP settings, then query Semrush data from the Cursor agent.
Sample use cases
Weekly rank and keyword-movement report across tracked domains
A scheduled agent pulls keyword_research and organic_research data and summarizes changes automatically.
Competitive intelligence on a new competitor
The agent fetches the competitor's organic keywords and backlink profile and produces a gap analysis.
In-editor SEO research while drafting content
From Cursor or Claude Code, an agent surfaces live volume, difficulty, and intent for target keywords without leaving the workflow.
Security & permissions
Authentication is OAuth 2.0 by default — the agent is redirected to Semrush's login and you explicitly authorize access; an API key (Authorization: Apikey ...) is an alternative for clients without OAuth support. Access is read-only: the agent can retrieve Semrush data but cannot modify or delete anything in your account. Queries draw down API units from your existing Semrush subscription, so usage is bounded by your plan's allocation.
Using Semrush MCP with Gamut
In a Gamut agent workflow, Semrush becomes a connected tool an agent calls on a schedule or in response to an event — for example, a weekly run that pulls rank-tracking and keyword movement for your domains, or an event-triggered check that fetches a competitor's backlink and organic-keyword profile when a new page is published. Gamut manages the OAuth connection so the agent can call tools like keywordresearch, organicresearch, and backlink_research, then route the results into a report, alert, or downstream step. Usage is bounded by your Semrush plan's API units, and access stays read-only.
Frequently asked questions
What is the Semrush MCP server?
It's an official, Semrush-hosted Model Context Protocol server at https://mcp.semrush.com/v1/mcp that lets AI agents query live Semrush data — keywords, domain analytics, backlinks, and traffic trends — directly, with read-only access authenticated over OAuth.
Is the Semrush MCP server free?
There's no separate fee for the MCP server, but it requires an existing Semrush subscription with API access (such as an SEO, Semrush One, or Trends API plan). Each query consumes API units from your plan's allocation; there is no standalone free tier.
How do I connect the Semrush MCP server to Claude or Cursor?
Add the remote server URL https://mcp.semrush.com/v1/mcp as an HTTP MCP server in your client (e.g. `claude mcp add --transport http semrush ...` for Claude Code, or via MCP settings in Cursor). On first use you'll be redirected to sign in to Semrush and authorize access via OAuth.
Is the Semrush MCP server hosted or self-hosted?
It's officially hosted by Semrush as a remote server at https://mcp.semrush.com/v1/mcp — you don't run any infrastructure. (Community-built self-hosted Semrush MCP servers also exist, but the official one is the hosted remote endpoint.)