SEO Cartograph · MCP

SEO MCP: connect your AI to SEO Cartograph

Q: Which plan do I need to use the SEO Cartograph MCP connector?

The connector is available from the free plan. On Free, the AI accesses everything coming from your own crawl: technical audit, pages, issues, clusters, the on-page Editor, plus request_crawl and inspect_url. Performance tools (Search Console, Analytics), SERP tools (rankings, share of voice, keyword tracking) and the Netlinker (link map, internal-link proposals) are on the Pro and Agency plans. On the AI side, you need a Claude plan that allows connectors.

Q: Does the AI write to my site?

No. The AI drops proposals into the cockpit; you approve them, then apply in your CMS. Nothing is pushed to the site without you.

Your AI reads the cockpit directly, crawl, Search Console, clusters, rankings, and proposes internal links and on-page fixes on your real data. You approve inside the cockpit; nothing is written to your site without you. The intelligence is paid by your Claude subscription, at no extra AI cost from us.

Get started

What is MCP?

MCP (Model Context Protocol) is the open standard that lets an AI like Claude read data and call tools inside a third-party app. SEO Cartograph exposes its cockpit over MCP: instead of pasting exports into a chat, your AI queries your SEO data directly and acts inside the tool.

The intelligence is paid by your Claude subscription.

No extra AI cost on our side, no token meter, no “AI credits” to top up. You connect the AI you already pay for; SEO Cartograph provides the data and the tools. That’s the whole difference with SEO platforms that bill every AI request.

What the connector exposes

About thirty tools, in three families. The badge shows the required plan.

Free whatever comes from your own crawl, at no variable costPro Performance, Search Console, SERP and Netlinker

Reading data

get_crawl_data

The latest crawl and its technical issues, page by page.

Free

get_clusters_data

Semantic clusters and their coverage.

Free

get_search_queries

A page’s real Search Console queries (impressions, clicks, position).

Pro

get_serp

The real SERP for a keyword on its locale.

Pro

get_link_map

The cluster map and internal linking, menu/footer links excluded.

Pro

Proposals

propose_fix_value

An on-page fix: title, meta description, alt attribute, heading structure.

Free

propose_internal_link

An internal link: source page, target page, anchor, and the reason.

Pro

Actions

request_crawl

Relaunch a crawl of the site.

Free

inspect_url

Inspect a URL (status, indexing).

Free

organize_clusters

Reorganize clusters.

Free

track_keywords

Add keywords to rank tracking.

Pro

Connect your AI in 3 steps

On the user side, setup is three steps.

Add the SEO Cartograph connector in Claude (Claude.ai, Claude Desktop or Claude Code), using the MCP connector URL.

Authorize access on the consent screen: you pick the account, you see what is shared, and it is revocable anytime.

Ask your first question in plain language, the AI does the rest.

What the AI does next

It reads your real data through the read tools (crawl, Search Console, clusters, SERP).

It drops its proposals into the cockpit, links, fixes, each with its rationale.

You approve what fits; the change is applied in your CMS. On the next crawl, a resolved issue flips to “resolved”.

Netlinker · Let Claude propose links

Prioritize my clusters and propose internal linking, with the estimated impact.

Tools called

get_link_mapget_search_queriesget_serp

Projected linking impact · 12 weeks

+38 links ▲ clusters strengthened

Proposals awaiting approval

propose_internal_link

Source /guides/technical-audit/ → target /seo-cartograph/. Anchor: “SEO audit”. Estimated impact: +9 positions on the target cluster.

Proposed · to review

propose_internal_link

Source /blog/internal-linking/ → target /seo-cartograph/internal-linking/. Anchor: “internal linking tool”. Estimated impact: cluster coverage raised to 80%.

Proposed · to review

Netlinker preview, projected impact, to approve in the cockpit.

Compatibility

The connector follows the MCP standard. It is designed and validated for Claude; any MCP-compatible client can connect through the connector URL.

Client	Compatible	Detail
Claude.ai	Yes	Connectors on paid plans (Pro, Team, Enterprise).
Claude Desktop	Yes	macOS and Windows app.
Claude Code	Yes	In the terminal, to drive SEO from your scripts.
Other MCP clients	Yes	Any protocol-compliant client, via the connector URL.

MCP connector URL: provided in your SEO Cartograph workspace on activation.

Your data stays yours

The key point when you hand client data to an AI.

The AI proposes, it does not apply. Links and fixes land in the cockpit; you approve. The AI writes nothing to your site.

OAuth access, with a consent screen. You see what the connector can read before you authorize.

Data scoped to your account. The connector only exposes your workspace’s projects, not other people’s.

Revocable in one click. Cut access whenever you want, from Claude or from your workspace.

What it changes in your day

A few questions to ask your AI directly, once the connector is plugged in.

›_Which pages are stuck in positions 4 to 10 over the last three months?

›_Propose 5 internal links to strengthen my “technical audit” cluster.

›_Compare today’s SERP with last month’s on my tracked keywords.

›_List pages whose title falls outside 30–60 characters and rewrite them.

›_Which keywords get impressions but no clicks? Give me the pages to optimize.

What’s metered

The AI is free for you (it is your Claude subscription). On the SEO Cartograph side, only live SERP analyses are metered: 0 on Free, 30 per month on Pro, 300 on Agency. Cached re-reads are free. Crawl, audit and clusters use no credit, so on Free, the AI works on your crawl data without ever costing you anything variable.

FAQ

Which plan do I need to use the connector?

The connector is available from the free plan, with tools that depend on the plan. On Free, the AI accesses everything coming from your own crawl: technical audit, pages, issues, clusters, the on-page Editor, plus request_crawl and inspect_url. Performance tools (Search Console, Analytics), SERP tools (rankings, share of voice, keyword tracking) and the Netlinker (link map, internal-link proposals) are on the Pro and Agency plans. On the AI side, you need a Claude plan that allows connectors.

What data can the AI read?

Only the data of your workspace’s projects: crawl, Search Console, Analytics, clusters, rankings. Nothing outside your account, and only what you authorized on the consent screen.

Does the AI write to my site?

No, by design. The AI drops proposals into the cockpit; you approve them, then apply in your CMS. Nothing is pushed to the site without you.

How much extra AI does it cost?

Nothing. The intelligence is paid by your Claude subscription. SEO Cartograph does not bill tokens or “AI credits”.

Does it work with ChatGPT or other AIs?

The connector follows the open MCP standard. It is designed and tested for Claude; any MCP-compatible client can connect through the connector URL.

Ready-made workflows

The connector supplies the data, the SEO Cartograph skills supply the method. You ask for an agency task, the AI runs it end to end, and you approve the deliverable.

Reporting

Monthly SEO report

The AI reads Search Console, Analytics, rankings and clusters, then writes the client report: highlights, ranking gains, next actions.

Content

Landing page brief

From real queries and the SERP, it proposes a page structure: angle, headings, home cluster, inbound linking.

Linking

Quarterly linking plan

It prioritizes weak clusters and proposes an internal-linking schedule, page by page, with estimated impact.

Prospecting

Pre-quote express audit

Crawl, on-page issues and opportunities, summarized on one page ready for a prospecting meeting.

Get started for free