SEO Rocket MCP: Free SEO Guides and Tools Inside Claude

Most “free SEO MCP server” listings aren’t really free. Read the small print and you’ll usually find a capped trial of a paid API, a server that needs your own Ahrefs or DataForSEO key, or a GitHub repo you have to install and keep running yourself. The SEO Rocket MCP server is a different, deliberately smaller thing: a hosted, read-only Model Context Protocol server you can add to Claude by pasting one URL, with no account, no API key and no install. This guide covers what it does, how to connect it, and the limits most connector write-ups skip.

What the SEO Rocket MCP Server Is (and Isn’t)

The Model Context Protocol is the open standard that lets AI assistants call outside tools. A server publishes a list of tools, each with a name, a plain-language description and an input schema. The assistant reads those descriptions and decides when to call one. If the protocol itself is new to you, start with our Model Context Protocol explainer.

SEO Rocket’s server lives at https://app.seorocket.ai/mcp. The essentials:

Free, with no sign-in. No account, OAuth flow or API key.
Read-only. Every tool looks things up and returns text. Nothing writes to a site, a CMS or an account.
Remote, over Streamable HTTP. It’s hosted, so there’s nothing to run locally. It’s also stateless: each request stands alone.
Public data only. It searches SEO Rocket’s published guides and free tools, and reads the public XML sitemaps of any domain you name.

What it is not: it isn’t a keyword-volume database, a backlink index or a rank tracker. It doesn’t connect to your SEO Rocket projects, your Search Console or anything behind a login. For live third-party data, the paid connectors in our roundup of SEO MCP servers are the right tool. This one covers the knowledge layer: how-tos, definitions, quick tools, and a structural read of any site.

The Four Tools, and When Claude Reaches for Each

The server exposes four tools. Their descriptions are written to tell Claude when each is the right call, which is why a connector with only four tools still gets used at the right moments.

search_seo_guides

Searches about 1,900 SEO Rocket guides covering technical SEO, on-page and schema, keyword research, content, link building, local SEO, Search Console and AI search. It returns titles, one-line summaries and URLs, so Claude can cite a source instead of paraphrasing from memory. Ask how to read the page indexing report in Search Console and you get the three guides that cover it, with links.

find_free_seo_tool

Finds one of SEO Rocket’s 79 free, no-sign-up browser tools for a task: a SERP snippet preview, a schema or robots.txt generator, a hreflang or redirect check, a word counter, image compression, UTM links. Call it with no task and it lists every tool, grouped into six sections, from on-page and structured data to links, tracking and planning. The full set is also on the free SEO tools roundup.

define_seo_term

Gives a plain-English definition of an SEO term or abbreviation (DR, KD, canonical, orphan page, striking distance) plus the guides that explain it in depth. It’s useful for client-facing work. If a stakeholder asks what “striking distance” means, the answer comes back as “keywords ranking in positions 11 to 20, the fastest wins”, not a vague paragraph.

get_site_structure

Maps any website from the XML sitemaps it publishes. You get its sections (blog, products, locations, programmatic pages), roughly how many URLs each holds, example URLs, the top-level folder tree, and when each section was last updated. It’s the most practical of the four for competitive work, and the only one that touches a site other than ours.

How to Add the SEO Rocket MCP Server to Claude

In the Claude apps, a remote MCP server is added as a custom connector. Per Anthropic’s help article on custom connectors, the current flow on an individual plan is:

Go to Customize → Connectors.
Click + Add, then Add custom connector.
Name it “SEO Rocket” and paste https://app.seorocket.ai/mcp as the remote MCP server URL.
Choose No sign in under Authentication, since there’s nothing to authenticate, then click Add.

Then, in a conversation, open the + menu, go to Connectors, and toggle SEO Rocket on. Anthropic notes that Free plan users are limited to one custom connector, so a Free user who adds this one has used that slot. On Team plans, only Owners and Primary Owners can add a custom connector (Enterprise also allows a custom role with that permission). Members then connect and enable it individually.

One detail matters if you ever host your own server: Claude connects to custom connectors from Anthropic’s cloud, not from your laptop. A server must be reachable on the public internet. Ours is, which is why a single URL is all it takes.

Claude Code, Cursor and Other MCP Clients

Because it’s a standard Streamable HTTP server, it works in any MCP client that supports remote servers. In Claude Code, the Claude Code MCP docs give the syntax as claude mcp add --transport http <name> <url>:

claude mcp add --transport http seo-rocket https://app.seorocket.ai/mcp --scope user

The user scope makes it available across all your projects. Leave it off for the default local scope, or use project to share it with your team through the project’s .mcp.json.

In Cursor, per its MCP documentation, a remote server goes in ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project) with a url field:

{
  "mcpServers": {
    "seo-rocket": { "url": "https://app.seorocket.ai/mcp" }
  }
}

No headers block is needed, because there’s no key.

Check What It Does Before You Trust It

The MCP specification says clients “MUST consider tool annotations to be untrusted unless they come from trusted servers”, and that includes a server declaring its own tools read-only. Our tools carry read-only annotations. You shouldn’t take that on faith from us or anyone else. Check the tool list yourself:

curl -s https://app.seorocket.ai/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

The JSON that comes back lists every tool, its full description and its input schema. Four lookups, none taking anything beyond a query, a task, a term or a domain. A plain browser visit to the same URL returns a short description of the server. Make this a habit for every connector you add, paid or free: read the tool list before you click “Allow always.” Anthropic’s help article makes the same point, telling you to click “Allow always” only for a server and tool you trust to run unsupervised, and our guide to MCP security for marketing teams covers the wider risks, prompt injection included.

Prompts That Get Good Answers

Knowing how the tools work under the hood changes how you should phrase things.

Use concrete words, not clever phrasing. The guide search matches the words in your query against titles, focus keywords and summaries. It doesn’t use embeddings. “Hreflang errors on Shopify” beats “why is my international setup confusing Google.” When nothing matches closely, the server says it’s returning the closest partial matches rather than pretending they’re exact.
Name the server when it matters. Claude chooses tools from their descriptions, so it may answer from its own knowledge. Adding “use SEO Rocket” or “cite an SEO Rocket guide” makes the call far more likely.
Ask for citations. Every result carries a URL, and the server tells Claude to cite them. Asking for links in the answer gives you something you can check and forward.
Give a bare domain for mapping. “example.com” works, and so does a full URL. Very large sites can take up to a minute.

Three Workflows Worth Running

Size up a competitor’s content footprint

Ask Claude to “map competitor.com’s site structure with SEO Rocket and tell me where their content is concentrated.” You’ll see whether their weight sits in a blog, in location pages or in thousands of programmatic URLs, and which sections were updated recently. Run it for two or three rivals and ask Claude to compare. The XML sitemap guide explains what a healthy sitemap should look like when you turn the tool on your own domain.

Answer a client question with a source attached

When a client asks “should we noindex our tag pages?”, ask Claude to answer using SEO Rocket guides and include the links. You get a reasoned answer plus a reference the client can read, which beats an unsourced paragraph pasted into an email.

Go from diagnosis to fix

Combine the tools in one prompt: “Explain what FAQ schema is, find the guide on it, and give me a free tool to generate it.” Claude calls the definition, the guide search and the tool finder, then hands you a short explanation, a guide and a generator URL. That’s the actual benefit of MCP SEO work: the assistant does the joining. Our MCP for SEO guide covers that shift in depth.

The Limits You Should Know

The guide index is a snapshot. It’s bundled with the server and refreshed when we redeploy, so a guide published this morning may not show up yet.
Sitemaps aren’t the whole site. The structure tool reads only what a site lists in its XML sitemaps. It doesn’t crawl. Pages missing from the sitemap are invisible to it, and on very large sites the counts are estimates from a sample. The output says so when that happens.
Rate limits apply. Per-IP limits are generous for a normal conversation, but site mapping has a tighter cap of a handful of maps per ten minutes, because each map fetches many sitemap files.
No live metrics. No search volumes, no rankings, no backlink counts. If an answer contains those numbers, Claude got them somewhere else, or made them up.
What we log. To see what people actually ask, the server records which tool was called, the query text and the client’s user-agent name, not your IP address. Don’t put anything confidential in a query.

Where the Free Server Stops and the App Starts

The free server answers “how” and “what is.” The paid work, “what should I do on my site, with real numbers”, happens in the SEO Rocket app at app.seorocket.ai. That’s a chat-first workspace where the same conversational style runs on live data: keyword research on real Ahrefs data, competitor gap analysis, a technical audit from a real crawler with JavaScript rendering, rank tracking, Search Console and GA4 integrations, AI-visibility tracking, and an article writer with validation gates. It’s built on a playbook proven across 1,000,000+ ranking pages.

The split is deliberate. A public, no-login server can’t safely touch anyone’s private data. So the connector stays on public information, and anything tied to your own sites stays in the app, where it’s tied to your account. If you’d rather wire your own Search Console into Claude directly, our Search Console MCP walkthrough covers that route.

SEO Rocket MCP FAQ

Is the SEO Rocket MCP server really free?

Yes. There’s no account, no API key and no trial period. It’s rate-limited per IP to stop abuse, but normal use from a chat won’t hit the limits.

Does it work with ChatGPT or Gemini?

It’s a standard remote MCP server, so any client that supports remote Streamable HTTP servers can connect to it. We’ve documented Claude, Claude Code and Cursor above because their setup steps are confirmed in their own docs. For other assistants, check their current connector documentation.

Can it see my SEO Rocket projects or rankings?

No. It has no access to any workspace, project or connected account. It only reads SEO Rocket’s public guides and tools, and public sitemaps.

Is it safe to click “Allow always”?

All four tools are lookups that change nothing, and you can confirm that yourself with the tool-list check above. That’s the test to apply to any connector before granting standing permission.

The Bottom Line

The SEO Rocket MCP server isn’t trying to be an all-in-one data connector, and you shouldn’t treat it as one. It’s the free, no-account option among SEO tools in Claude: cited how-to guides, plain-English definitions, the right free tool for the job, and a quick structural read of any site from its sitemaps. Add it in a minute, read its tool list once, ask for citations, and pair it with a live-data source when the question needs numbers.