MCP SEO Tools for Claude: An Agency Playbook

MCP SEO tools for Claude are hosted servers that let Claude call live SEO data during a conversation: SERPs, keyword volume, backlinks, Google Business Profile details and Maps rankings. DFY Hub's SEO MCP gives Claude 93 of these tools through one URL and a browser sign-in, billed in credits. For an agency, connecting is the easy part. What decides whether it pays off is how you run it across a client roster: one shared credit balance, a repeatable routine per client, somewhere to keep the results (the server stores nothing), and a person who checks Claude's read before a client sees it.

Last updated: October 2026

Everyone knows the first half. Agencies trip on the second.

The well-known part is true. Connect an SEO MCP server and Claude stops estimating search volume from memory and starts pulling real numbers. Ask it who's in the map pack for "emergency plumber" in Tulsa and it runs a live search instead of recalling one.

The little-understood part: Claude with SEO tools is an analyst seat, not a reporting system. It doesn't remember last month's numbers. It doesn't know which client a question belongs to unless you tell it. And it spends from the same credit balance whether you're working on your biggest retainer or a prospect you'll never hear from again.

That's fine for one site. Across 20 clients, that's why budgets vanish and findings get lost.

Connect once

Setup takes about a minute. In Claude.ai, Claude Desktop or the mobile apps, add a custom connector (Customize, then Connectors, then Add custom connector), paste https://mcp.yourdfyhub.com/seo and sign in with your DFY Hub account. On Claude Team or Enterprise, an owner adds the connector under Organization settings first. In Claude Code, it's claude mcp add --transport http dfyhub-seo https://mcp.yourdfyhub.com/seo.

There's no API key to paste. For teams: a DFY Hub account has one sign-in today, with no separate staff seats, so everyone who connects Claude uses that account's sign-in and draws from the same credit balance.

The tools that answer local client questions

Most agency questions for local service clients map onto a handful of tools. Credit costs below are DFY Hub's published Growth Engine rates; other plans differ.

Client question	Tool Claude calls	Credits
Who's in the map pack for our main service?	Google Maps Local Results	12
Who else competes past the top three?	Google Local Finder Results	12 for the first 20
What does a competitor's Google profile look like?	Google Business Profile Info	14
What are customers saying in their reviews?	Google Business Reviews	14 for the first 10
Where do we rank across the service area?	Local Rank Grid, 5x5	300
Who ranks organically for this term?	Google Organic Search Results	8 for the top 10
What does ChatGPT say when asked about us?	ChatGPT Response	18

You don't call tools by name. You describe the outcome and Claude picks. But knowing the price of what it'll pick keeps a "full analysis" request from turning into a dozen grid scans.

Budget credits per client, because the balance is shared

SEO MCP credits are counted per account, not per client. Every client draws from the same pool, credits reset monthly with no rollover, and there are no top-ups; if you run out, you move up a plan. DFY Hub's MCP terms also say credits are deducted when the call runs, even if the result comes back empty.

So give each client a standing monthly allowance. A worked example at Growth Engine rates:

• DFY Hub's published local SEO audit workflow: about 74 credits
• One 5x5 grid scan for the client's main service term: 300 credits
• Organic checks on 10 priority keywords: 80 credits

That's about 454 credits per client per month. Twenty clients come to roughly 9,080 credits, a small slice of the plan's 200,000 monthly credits. The surprises come from open-ended prompts. "Compare backlinks across all eight competitors" or a grid scan on every keyword can eat a month's allowance for one client in an afternoon.

My advice: put the allowance in the prompt. "Use no more than 500 credits for this client this month, and tell me your plan before running anything" is a sentence Claude can follow.

The server forgets. Your process can't.

DFY Hub's SEO MCP is a stateless proxy: it doesn't store your queries or the responses. That's good for client confidentiality. It also means next month's Claude has no idea what this month's numbers were.

So save each client's output somewhere you control, such as a shared doc per client, dated, with the raw numbers next to Claude's summary. For rankings you need to trend week over week, use something that checks on a schedule. In the DFY Hub platform, keyword rank tracking takes weekly snapshots and keeps the history, from Local Dominator at $99/mo per client. The Local SEO Audit Tool: The 3 Checks That Matter post covers which local checks belong in that recurring set.

Deliver analysis, not data feeds

This one catches agencies out. Under DFY Hub's MCP Terms, you can use the data for your own analysis, but you can't resell raw data feeds or make automated bulk calls designed to mirror the data sources.

In practice, that means your client gets your read of the numbers: what moved, why you think it moved, and what you'll do about it. They don't get a nightly export piped into their own dashboard. If a client wants a self-refreshing data product, that's a job for an API, and the SEO Data API Alternative post covers when to keep one.

Where a person signs off

Live data fixes the inputs. It doesn't fix the interpretation. Claude can read a seasonal dip as a decline, or credit a ranking change to whatever happened to change that week.

I wouldn't send a Claude summary to a client unless someone has opened at least one tool call behind it. Most MCP clients, Claude Desktop included, show which tools ran, so you can check the raw output against the sentence that's going in the email. It takes two minutes and it's the difference between an analyst and a guess with good grammar.

Two practical limits to plan around. Access tokens last 24 hours with no refresh token, so expect to sign in again about once a day. And this is SEO data only. DFY Hub's Jobber MCP server is built for DFY Hub's conversational agent, which isn't available yet, so Claude can't read a client's job records through it today. Jobber MCP Tools: What Agencies Can Actually Automate covers what that server contains.

What it costs to start

The free plan includes 1,000 credits once you sign up and verify your email, with no credit card. Paid plans are $99/mo for 50,000 credits, $199/mo for 200,000 and $399/mo for 1,000,000, priced per account rather than per user. All 93 tools are on every plan. Run your own agency's site through it first, where you'll spot a wrong answer immediately.

Frequently asked questions

What are MCP SEO tools for Claude?

They're SEO data tools exposed through a Model Context Protocol server, which Claude can call during a conversation. Instead of estimating search volume or rankings from training data, Claude pulls live results. DFY Hub's SEO MCP gives Claude 93 tools across 12 categories, including SERPs, keywords, backlinks, Google Business Profile data and a geo-grid scan, through one hosted URL and an OAuth sign-in.

Are SEO MCP credits shared across an agency's clients?

Yes. DFY Hub's SEO MCP credits are counted per account, not per client, so every client's research draws from one monthly balance. Credits reset each month without rolling over, and there are no separate top-ups; you move up a plan for more. Credits are also deducted when a call runs, even if it returns an empty result, so a per-client allowance helps.

Does the SEO MCP keep a history of past results?

No. DFY Hub's SEO MCP is a stateless proxy that doesn't store your queries or the responses, so Claude can't compare against last month unless you saved last month's output. For rankings you want to trend over time, DFY Hub's platform rank tracking takes weekly snapshots and keeps the history, from Local Dominator at $99/mo per client.

Can I send SEO MCP data straight to clients?

You can share your analysis. DFY Hub's MCP terms let you use the data for your own analysis but not resell raw data feeds or make automated bulk calls designed to mirror the data sources. So a client report built on what Claude found is fine; an automated export feed into a client's own dashboard isn't what the service is licensed for.