I run Websites2Know almost entirely on a stack of AI tools now, and Semrush has been my keyword and competitor research backbone for years. When Semrush quietly rolled out its own MCP server, I connected it to Claude the same week and started running actual content research through it instead of tab-switching between a dashboard and a chat window all day.

This guide walks through every connection method that currently exists, what each one actually costs, where the setup breaks (because it did, more than once, for me), and the prompts I use every week to pull keyword gaps and competitor traffic data straight into a Claude conversation.

What Semrush MCP Actually Does Inside Claude

MCP, short for Model Context Protocol, is the open standard that lets Claude call out to live external tools mid-conversation instead of only working from its training data. Semrush built a remote MCP server on top of that standard, sitting at https://mcp.semrush.com/v2/mcp, that exposes its keyword, traffic, and backlink data as callable tools.

Once it’s connected, you type a normal question — “which keywords did my top three competitors gain this month that I’m not ranking for” — and Claude quietly queries the Semrush API in the background, pulls back real numbers, and writes its answer around them. No CSV exports. No copy-pasting rows into a spreadsheet formula. That’s the whole pitch, and in my experience it holds up for a solid majority of the research I used to do by hand.

Here’s the part most write-ups on this topic gloss over: there isn’t one single “Semrush with Claude” setup. There are four distinct paths, and picking the wrong one for your workflow is the single biggest reason people get stuck.

The Four Ways to Connect Semrush and Claude

Here’s how the official route stacks up against the community and third-party options, based on what each actually requires and who it fits.

My honest take: unless you’re already deep into building custom agent tooling, skip the community servers. They work, and the independently maintained projects do a solid job wrapping the raw Semrush API, but you’re taking on someone else’s side project as a dependency. The official connector removed that headache for me entirely, and it’s the one I’d point a fellow blogger toward first.

Step-by-Step: Connecting Semrush to Claude (Web and Desktop App)

This is the path most people reading this actually want. No terminal, no config files, no code.

1. Open Claude and find the connector

In Claude, go to Settings → Customize → Connect your apps, then search “Semrush.” You can also jump straight to it through the Claude connector directory.

2. Click Connect and review permissions

Claude redirects you to a Semrush permission screen listing exactly what it wants access to. It’s read-only — Claude can pull your Semrush data, but it can’t edit projects, delete tracked keywords, or touch your billing.

3. Approve, then log into Semrush if prompted

Click Approve. If you weren’t already logged into Semrush in that browser, you’ll get a normal login screen first. It’s the same OAuth flow you’d go through connecting Google Drive or Notion, nothing unusual.

4. Tag @Semrush in a new chat

Start a fresh conversation and type @Semrush followed by your question. You don’t strictly need the tag on every message once it’s used once in a thread, but I still add it out of habit — it’s a visual reminder the answer is pulling live data, not Claude guessing.

Step-by-Step: Connecting Semrush MCP to Claude Code

If you’re building anything more involved — a live rank-tracking dashboard, a content-gap script, an automated weekly report — you’ll want the CLI route instead.

1. Register the MCP server

Open your terminal in the project you’re working in and run this command:

2. Authenticate from inside Claude Code

Open Claude Code, run the /mcp command, select Semrush MCP from the list, and choose Authenticate. This opens the same OAuth screen as the web app version.

3. Confirm the tools loaded

Run /mcp again. Semrush should now show as connected with a list of available tools underneath it. If it shows connected but zero tools listed, that’s the exact bug I hit myself, and I’ll walk through the fix in the troubleshooting section below.

4. Prefer an API key instead of OAuth?

Some agent setups don’t support OAuth redirects. In that case, pass your Semrush API key as an authorization header instead, formatted as Authorization: Apikey YOUR_API_KEY. You’ll find your key under your Semrush profile’s API section.

What It Actually Costs

This is where most guides get vague, so let’s be blunt: Semrush MCP is not a free add-on, and it doesn’t run on your Claude subscription. It runs on your Semrush plan, and every query pulls from a separate pool called MCP API units.

A few things worth flagging that the pricing page won’t spell out plainly:

• 50,000 units sounds generous until you ask Claude something broad like “all keywords globally” — vague, unscoped prompts burn through units far faster than specific ones like “top 50 US keywords for [domain].”
• If you need Traffic Analytics or broader market data through MCP, that’s gated behind a separate Trends API plan, not included in the base SEO plans above.
• There’s no extra charge from Anthropic’s side for using the Semrush app inside Claude — you just need a Claude plan that supports connectors, which currently means a paid tier, not the free plan.

My Experience Actually Running This Setup

I test every tool I write about the same way: I connect it to a live project — usually this site — and run it through a week of the actual work I’d normally do by hand, not a cherry-picked demo prompt.

The web app connector was genuinely painless. I had it live in under two minutes, and my first prompt — asking which keywords a competitor in the AI-tools-review space had picked up in the past 30 days that I wasn’t targeting — came back with a clean, sourced list I could act on right away. No hallucinated numbers, because Claude wasn’t inventing them; it was reading them straight off Semrush.

The Claude Code side is where I hit friction. After registering the server and authenticating, my first /mcp check showed Semrush connected but with zero tools listed underneath it. Restarting Claude Code fixed it once, but the same thing happened again after my terminal session sat idle for a while, which tells me the OAuth token refresh isn’t always seamless on longer coding sessions.

The other rough edge: vague prompts eat units fast. I asked for “organic keywords for my whole niche” early on and watched a noticeable chunk of my monthly unit allowance disappear on that single query. Scoping every prompt with a specific database, country, and result count fixed that completely, but it’s the kind of lesson you only learn by burning through units once.

Bottom line from someone who actually ran it: the official connector is solid enough to replace a meaningful chunk of manual Semrush dashboard time, but it’s not “set it and forget it.” You have to write disciplined prompts, and if you’re on Claude Code, budget for the occasional reconnection.

Where It Delivers vs. Where It Falls Short

Prompts I Actually Use Every Week

A blank cursor is the biggest barrier to actually using this. Here’s my running list, adapted from Semrush’s prompt suggestions plus the ones I’ve refined through trial and error:

• “@Semrush — pull the top 30 keywords [competitor domain] gained in the US database in the last 30 days, sorted by search volume.”
• “@Semrush — find keywords [competitor domain] ranks for that I don’t, filtered to volume above 500 and difficulty under 60.”
• “@Semrush — which of my published posts rank between position 8 and 20, and what would it take to push them into the top 5?”
• “@Semrush — pull the top 20 referring domains for [competitor], flag which ones look like editorial mentions rather than directories.”
• “@Semrush — summarize this month’s organic traffic change for [my domain] vs. [competitor domain] in three bullet points.”

Setup Time by Method

A quick visual of how the four connection paths compare in minutes, based on my own timed setup runs.

Fixing the Most Common Setup Errors

“Semrush shows connected, but no tools appear”

This is almost always a stale OAuth session in Claude Code. Run claude mcp remove semrush, then re-add it with the original command and re-authenticate. If it persists, close Claude Code completely rather than just starting a new session — a full restart clears the cached handshake, which is what worked for me.

“API calls return no data” or empty results

Check that your Semrush plan actually includes API/MCP access — the Pro-level Classic plan below Guru and the free tier don’t. Then confirm your API key is active under your Semrush profile’s API section, since a regenerated or revoked key can fail silently in some clients rather than throwing a clear error.

“You’ve hit your API unit limit”

MCP units are consumed per request and reset on your subscription renewal date, not the calendar month. If you’re burning through them fast, tighten every prompt with an exact result count, database (like “US” or “UK”), and filter, and keep related questions in the same chat thread so Claude can reuse context instead of firing a fresh broad query each time.

Claude won’t stay connected between sessions

In the web app, connectors are tied to your Claude account and shouldn’t drop on their own. In Claude Code, they’re tied to your local project configuration, so if you’re switching machines or clearing your terminal environment, you’ll need to re-run the claude mcp add command on each new setup.

Semrush MCP vs. Doing It Manually vs. Other AI Rank Tools

If you’re deciding whether this is even worth setting up, here’s the honest comparison. Manually running the Keyword Gap tool, exporting a CSV, and filtering it in a spreadsheet is a process that typically eats well over an hour for a single competitor comparison. The same task through Claude and Semrush MCP took me under fifteen minutes, prompt to finished summary, in my own testing.

Compared to AI-visibility-specific tools I’ve tested for this site, like Rankscale or dedicated Perplexity rank trackers, Semrush MCP isn’t trying to compete on AI-answer-engine visibility. It’s still fundamentally a traditional SEO and traffic dataset wearing a conversational interface. If your priority is tracking whether ChatGPT or Perplexity cite your brand, you’ll want one of those purpose-built tools alongside it, not instead of it.

Where Semrush MCP wins outright is speed on the research you’re already doing in Semrush anyway. It doesn’t replace your SEO strategy, but it does remove a lot of the friction between having a question and getting a data-backed answer.

FAQ

Is Semrush MCP free to use?

No. You need a paid Semrush plan that includes MCP access — SEO Classic Pro or Guru, or any Semrush One tier — starting at $139.95 per month. There’s no standalone free MCP plan.

Does connecting Semrush cost extra on top of my Claude subscription?

No additional fee from Anthropic. You just need a paid Claude plan that supports connectors, and the query cost is deducted from your Semrush API unit balance, not billed separately.

Can Claude edit or delete my Semrush projects?

No. The connection is read-only by design. Claude can retrieve data but cannot modify, delete, or create anything inside your Semrush account.

Which is better: the Claude app connector or Claude Code?

Use the app connector if you just want to ask questions in chat. Use Claude Code if you’re building something persistent, like a dashboard or an automated report, since it gives you scripting control the chat interface doesn’t.

Can I use Semrush MCP with more than one AI assistant?

Yes. The same Semrush account can be connected separately to Claude, ChatGPT, Cursor, VS Code, and Gemini CLI at the same time, each using the same underlying credentials.

Will Semrush MCP alert me the moment a keyword drops?

Not on its own. Claude’s native scheduling still runs on a clock, so you’ll get movement summarized in your next scheduled digest rather than an instant push notification the second a ranking changes.

Final Thoughts

If you already pay for Semrush, connecting it to Claude is one of the easier upgrades you’ll make to your workflow this year. The web app route takes two minutes and genuinely replaces a chunk of manual dashboard digging. The Claude Code route takes a bit longer and occasionally needs a reconnect, but it unlocks real automation — dashboards, scheduled reports, scripted competitor audits — that the chat interface alone can’t touch.

What it isn’t is a replacement for a Semrush subscription itself, and it won’t get you instant alerts the second something changes. Go in expecting a faster, more conversational way to query data you’re already paying for, not a brand-new tool, and it’ll earn its place in your stack the same way it earned one in mine.

If you’re building out a broader AI-assisted SEO stack, it’s worth pairing this with a look at the wider field of AI SEO tools, how SEO strategy is shifting for AI visibility, and whether Claude’s accuracy compares to ChatGPT’s for the kind of data-grounded work this connector enables. And if Claude Code is new to you, my breakdown of what Claude Code can do that Cursor can’t is a good next stop.