Moz Data MCP Server: Domain Authority and Keyword Data in Claude and ChatGPT

This information is correct as of September 2026. The Moz MCP server is in beta, so details may change; Growth Method has made every attempt to ensure the accuracy and reliability of the information provided.

Is there an official Moz MCP server? Yes. Moz Data is a hosted, read-only Model Context Protocol server for the Moz Data API. You add it to Claude, ChatGPT or Claude Code, sign in with your Moz account, and then ask for Domain Authority, Page Authority, Spam Score, linking domains, anchor text, ranking keywords, keyword volume and difficulty, SERPs and more in plain English. It exposes 28 tools, none of which can change anything in Moz, and it requires a Moz Data API subscription rather than Moz Pro.

That last sentence is the one that trips people up, and it tripped us up too. This article covers what the server does, how Moz’s row-based pricing translates into “how much does a question cost”, how it differs from Moz Pro, and what we did with it in the first afternoon, including a real campaign that came straight out of the ranking keyword data.

What Moz Data MCP is (and is not)

Moz is one of the oldest names in SEO software, best known for inventing Domain Authority. It now sells four things that are easy to confuse, and the naming does not help:

• Moz Pro is the web app. Campaigns, rank tracking, site crawls, competitive research, AI visibility tracking and scheduled reports. It uses the Moz data index behind the scenes, but it does not include the API or the MCP.
• Moz API (sometimes called Mozscape API or the Moz Data API) is the data layer, sold by the row. It is a JSON-RPC API with methods for site metrics, links, keywords and rankings.
• Moz Data is the name Moz gives to the MCP endpoint for that API, and to its custom data solutions business. When you search Claude’s connector directory, “Moz Data” is what you will find.
• Moz Local is a separate product for managing business listings, with its own MCP endpoint.

The official MCP server lives on the API side. In Moz’s own words from the MCP documentation:

“Instead of writing code against our API, you connect the MCP server to your AI client and ask questions in natural language; the client calls the appropriate Moz tools on your behalf.”

Moz, Getting Started with the Moz MCP Server

Before Moz shipped this, the only options were community wrappers such as metehan777/moz-mcp (whose author is explicit that “This MCP Server is not official”) and aggregator connectors from Composio and Apify. Those still exist, but there is now no reason to route your Moz API key through a third party.

If MCP itself is new to you, our introduction to MCP for marketers covers the basics. The one-line version: MCP is the open standard that lets an AI assistant call outside tools and pull their data into a conversation, so the assistant answers from Moz’s live index rather than its general knowledge.

What the 28 tools cover

Moz has not published a tool-by-tool reference for the MCP, which we have asked them to fix. What we can tell you from connecting it is that the Data endpoint exposes 28 tools, each named after the matching method in the Moz API documentation with the “Action” suffix dropped. So the API’s DataSiteMetricsFetchAction becomes the tool DataSiteMetricsFetch, and the docs page for the method doubles as the docs for the tool. The one place the mapping is not one-to-one is keyword metrics: the API’s five separate fetches (volume, difficulty, opportunity, priority, intent) collapse into a single DataKeywordMetricsFetch tool that returns all of them.

The full list, grouped the way Moz groups the API:

Two details from the method docs matter before you start prompting. Ranking keyword lists are capped at the top 50 positions, so “what does this page rank for on page 6” is not answerable. And search intent is opt-in until 1 October 2026, after which the keyword metrics call returns it by default and charges a row for it.

What it can’t do

The limits are mostly a consequence of what the API is, rather than choices made for the MCP:

• It cannot track anything over time. Every call is a snapshot of the index at the moment you ask. There are no saved campaigns, no rank tracking history and no scheduled checks. The metric histories tool gives you DA over time, but keyword positions are point-in-time only.
• It cannot generate reports. Moz Pro’s scheduled stakeholder reports are a Pro feature. With the MCP, the report is whatever you ask your assistant to write.
• It cannot see your Moz Pro campaigns. The two products do not share account data. Your tracked keywords, competitors and crawl results in Pro are invisible to the MCP.
• It cannot change anything. Every tool on the Data endpoint reads. The Moz Local endpoint is the exception, and it includes create, update, cancel and close tools for locations.
• Seated users cannot use it yet. During the beta, only the Moz account owner can connect.

We asked Moz support directly what a team would lose by moving from Moz Pro to the API to get the MCP. Their answer was clear:

“The Moz API doesn’t allow you to track things over the long term or generate reports for you, it just allows you to make requests to retrieve data at the time the request is made, and then it’s up to you how you treat that data.”

Moz customer support engineer, email to Growth Method, September 2026

Their suggestion was that the two products are complementary rather than either/or: keep Moz Pro for tracking, GEO monitoring and reports, and add an API plan for the MCP. Whether that makes sense depends on how much of the tracking you can now do elsewhere. In our case, Search Console and PostHog already cover positions and traffic, so the API alone was the better fit.

Pricing: what a question costs

Moz prices differently from the other SEO MCP servers we have covered, and the difference matters before you let an agent loose on it.

The Moz API is priced by the row. Moz’s definition: “one row typically corresponding to one object in the response for methods that return multiple objects, or one field in the response for methods that return a single flat object or report.” Every MCP tool call spends rows from the same monthly quota as direct API calls.

Free access also throttles you to one request every ten seconds. Fifty rows a month sounds like fifty questions. It is not, because different methods cost different amounts:

So “what does growthmethod.com rank for?” is a single tool call that can return 50 rows and empty the free tier in one go. A competitor link intersect across three domains costs three rows per result. An assistant answering a broad question such as “audit this domain’s backlink profile” will chain several calls without asking, which is the point of MCP but also how a Starter plan disappears in an afternoon.

Three habits keep this under control. Ask for the quota before and after a session (there is a tool for it). Tell the assistant to limit result counts when you only need a sample (“top 10 ranking keywords by volume”). And when you want the same data repeatedly, use Moz Pro or a warehouse, not the MCP, because there is no caching on Moz’s side.

Moz support’s advice on the free tier was blunt and, in our experience, right: it is “normally enough to get started and figure out what works for you before transitioning into a paid subscription”, but for real testing “it would be worth starting with a paid subscription then upgrading at a later date if need be”. The 20 dollar Starter plan is the sensible entry point.

Setting it up

The Moz MCP server supports two authentication methods, and which one you use depends on your client.

OAuth (recommended). The client sends you to a browser sign-in with your Moz account. No API key is stored anywhere, and the connection can be revoked from the client.

Bearer token. For clients without OAuth support, send your Moz API key from moz.com/api/dashboard as an Authorization: Bearer header. The same key works for both the Data and Local endpoints.

Claude Desktop

Moz Data and Moz Local are both published in Claude’s connector directory, so there is no URL to paste:

1. Open Settings, then Connectors.
2. Search for Moz.
3. Click Connect next to Moz Data and complete the OAuth sign-in.

ChatGPT Desktop and other clients

Add a new connector manually and enter the name moz-mcp-v1-data and the URL https://api.moz.com/mcp/v1/data. Moz suggests those exact labels; the name is only cosmetic, but using theirs makes their support docs easier to follow.

Claude Code

Add the server without an auth header, then run /mcp inside Claude Code to complete the OAuth sign-in when prompted:

claude mcp add moz-mcp-v1-data https://api.moz.com/mcp/v1/data \
  --transport http \
  --scope user

Or supply your API key directly:

claude mcp add moz-mcp-v1-data https://api.moz.com/mcp/v1/data \
  --transport http \
  --header "Authorization: Bearer $YOUR_MOZ_TOKEN" \
  --scope user

Swap the name and URL for moz-mcp-v1-local and https://api.moz.com/mcp/v1/local to add the Local endpoint instead.

Growth Method

We connected Moz Data to Growth Method as a custom integration using Sign in (OAuth) and the /data URL. The same browser sign-in came through, and the integration surfaced all 28 tools to the agents. It sits alongside Sitebulb, DataForSEO and SE Ranking in the technical SEO and search data group, so an agent planning a campaign can pull Domain Authority and ranking keywords the same way it pulls sessions from PostHog.

One thing to remember from the beta restriction: whoever connects must be the Moz account owner. If a seated user tries, the OAuth flow will fail, and the fix is to have the owner make the connection.

A real campaign from the ranking keyword data

The prompt library below is a menu, but the useful thing to know is what a session turns into. Here is the first campaign that came out of connecting Moz Data to Growth Method on this site.

The question was the obvious one for any content site: “Which of our pages are stuck on page 2 or 3 of Google for keywords with real volume?” The agent called the ranking keywords tool for growthmethod.com, filtered to positions 11 to 30, sorted by monthly search volume, and grouped by page. It found two candidates and picked one. The campaign it created, in its own words:

“Moz ranking data shows https://growthmethod.com/fixed-mindset/ is stuck on page 3 of Google for two related keywords: ‘fixed mindset’ at position 25, 4,519 monthly searches, difficulty 46; and ‘fixed mindset definition’ at position 27, 1,271 monthly searches, difficulty 44. That’s around 5,790 combined monthly search volume the page is currently missing out on, at a moderate difficulty level that should be reachable with a content push. There’s also a runner-up candidate, /status-quo-bias/ at position 22 for a single 1,252-volume keyword, but the fixed-mindset page has more upside for similar effort.”

Growth Method campaign observation, generated from Moz Data, September 2026

The proposed change was a refresh of the fixed mindset article: a clearer definition section near the top to target the “definition” query directly, expanded fixed-versus-growth contrasts, FAQ schema, and internal links from the related mindset and culture pages that already rank. The hypothesis it wrote follows the standard shape:

“Based on https://growthmethod.com/fixed-mindset/ ranking position 25 for ‘fixed mindset’ (4,519 searches/month) and position 27 for ‘fixed mindset definition’ (1,271 searches/month), both on page 3 of Google, we believe refreshing the page’s content depth, adding a clear definition section, FAQ schema, and internal links from related psychology/growth pages will result in the page climbing toward page one and capturing a meaningful share of the combined ~5,790 monthly searches. We’ll measure success through organic clicks and average position for these keywords, and monitor overall organic sessions to the page.”

Growth Method campaign hypothesis, September 2026

Three things stand out from that session. First, the data does the prioritisation: two candidates, one ranked above the other on volume against effort, with the runner-up recorded rather than discarded. Second, the measurement plan does not depend on Moz at all. Positions come from Search Console and sessions from PostHog, because the Moz MCP cannot track over time. Moz found the opportunity; other tools will measure the result. Third, the whole thing cost roughly 60 rows, most of them the ranking keywords list.

That division of labour, Moz for discovery and your analytics for measurement, is the right way to think about this server. The plan, launch, analyse loop needs a source of opportunities and a source of truth, and Moz Data is squarely the former.

Prompts worth stealing

Moz has not published a prompt library for the MCP. These are the ones that earned their rows in our first sessions, with the row cost in mind:

• Sanity check (1 row): “Using Moz Data, what’s the Domain Authority, Page Authority and Spam Score for growthmethod.com?”
• Quota check (1 row): “How many Moz API rows do I have left this month?”
• Page 2 opportunities (up to 50 rows): “List the keywords growthmethod.com ranks for between positions 11 and 30, sorted by volume, and group them by page.”
• Keyword triage (up to 5 rows per keyword): “Give me volume, difficulty, organic CTR and intent for ‘agile marketing’, ‘marketing sprint’ and ‘growth marketing framework’.”
• Competitor gap (1 row per result, times the number of domains): “Which domains link to competitor-a.com and competitor-b.com but not to us? Top 20 by Domain Authority.”
• Link hygiene (1 row per domain): “Which linking domains have we lost recently, and which of them had a DA above 40?”
• Directional check (1 row): “How has our Domain Authority moved over the last 12 months?”
• Cross-tool: “Take the top 10 pages by sessions from PostHog last month and fetch their Page Authority and ranking keyword counts from Moz.”

That last category is where the MCP earns its place for marketing teams rather than just SEO specialists. Moz Data only ever returns Moz data, but your assistant can reason across every tool you have connected. Pair it with the GA4 MCP or PostHog and “which of our high-traffic pages have the weakest authority” becomes a one-line question. Add Sitebulb and you can cross-reference technical issues with the pages that matter most for links.

A word on Domain Authority itself, since it is the metric most people reach for first. Moz’s own explainer is careful about what it is and is not:

“Domain Authority is not a Google ranking factor and has no effect on the SERPs.”

Moz, What is Domain Authority?

It is a comparative, predictive score. Use it to rank prospects against each other or to watch your own direction of travel, not as a target in itself. An assistant with the MCP will happily fetch DA for a hundred domains; make sure the question you are answering with those numbers is a real one.

Moz Pro vs Moz API: which do you need?

If you already pay for Moz Pro and want the MCP, this is the decision in front of you.

Moz’s position is that you can hold both, and for a large SEO team that is probably right. For a small B2B marketing team that already has Search Console, an analytics tool and an AI assistant with a memory, the API plan alone covers the discovery side of the job, and the tracking side moves to tools you already pay for.

Security: what a reviewer will want to know

Moz has not published a security overview specific to the MCP server, so the following is what the documentation and our own connection tell us. Verify with Moz before you rely on it.

• Read-only on the Data endpoint. All 28 tools report data and none can change your Moz account. The Local endpoint is not read-only.
• OAuth is the default. Sign-in happens in a browser against your Moz account. The AI client never sees your Moz password, and no API key is stored in the client.
• API keys are an option, not a requirement. The Bearer token path exists for clients without OAuth. If you use it, treat the key like any other long-lived secret: it grants full API access and spends your quota.
• Account owner only. During the beta, the OAuth grant is tied to the account owner, which limits who can create a connection but also means the owner’s credentials are the ones in play.
• Quota is the blast radius. Worst case, a connected assistant can read anything the Moz index holds and spend your monthly rows doing it. It cannot delete or modify anything on the Data endpoint. Overages are switched off on the Free and smaller Starter plan, so a runaway agent stops rather than bills you.
• What happens after the data lands in your chat is governed by Anthropic, OpenAI or whichever client you use, under your agreement with them, not by Moz.

Beta caveats

This is a beta and Moz says so. Things we hit or would flag:

• No tool reference. Moz has not published the list of MCP tools, their descriptions or their parameters, and there are no bundled Skills. Ahrefs publishes tool categories for its MCP, and Moz would benefit from the same; we have fed that back.
• Seated users cannot connect. If you manage a client’s Moz account as a seated user, you will need the owner to make the connection until Moz expands access.
• Rows go fast. The first hour of curiosity on a new connection can burn a Starter plan’s month. Start with the quota tool and set limits in your prompts.
• Search intent changes on 1 October 2026. It becomes a default (and billed) part of keyword metrics rather than opt-in.
• Moz Data and Moz Local are separate connections. Connecting one does not give you the other, and each requires its own subscription.

Getting started checklist

1. Sign up for the free Moz API plan to confirm the connection works, then move to Starter at 20 USD a month before doing anything real.
2. Make sure you are the Moz account owner, or ask the owner to make the connection.
3. Add Moz Data from Claude’s connector directory, or by URL in ChatGPT, Claude Code or Growth Method, using OAuth.
4. Run the three-prompt warm-up: check your quota, fetch site metrics for your own domain, list your top ranking keywords by volume.
5. Ask the page 2 question (“which pages rank between 11 and 30 for keywords with real volume”) and turn the best answer into a campaign.
6. Connect the tools that will measure the result (Search Console, GA4 or PostHog) to the same assistant, so Moz finds the opportunity and your analytics proves whether the change worked.

About Growth Method

The fixed mindset campaign above is what Moz data looks like once it has somewhere to go: a ranking gap becomes a campaign, gets prioritised against your goal, and is measured on organic clicks and sessions rather than on Domain Authority.

Growth Method is the agentic marketing platform for B2B teams. AI agents plan, launch and analyse marketing campaigns from your live marketing data, with your martech stack connected in minutes and Moz Data one input among many.

We are on-track to deliver a 43% increase in inbound leads this year. There is no doubt the adoption of Growth Method is the primary driver behind these results.

Laura Perrott, Colt Technology Services

If you would rather run more campaigns than manage row quotas, get started.

Further reading

Moz’s own documentation, in the order you will probably need it:

• Getting Started with the Moz MCP Server
• Moz API pricing
• Moz API: Getting Started (includes the pricing and quota definition)
• Fetch Site Metrics (the “Data” sidebar lists every method the MCP wraps)
• List Ranking Keywords
• Fetch Keyword Metrics
• What is Domain Authority?

Related reading from us:

• Sitebulb MCP server: chat with your crawl data in Claude and ChatGPT
• Firecrawl MCP server: pricing, free tier and SEO automation
• MCP vs API: what marketers need to know
• MCPs, CLIs and Skills: which AI interface fits your marketing workflow?
• An introduction to MCP for marketers

Frequently asked questions

What is the Moz Data MCP server?

Moz Data is Moz’s official, hosted Model Context Protocol server for the Moz Data API. It runs at https://api.moz.com/mcp/v1/data and exposes 28 read-only tools covering site metrics (Domain Authority, Page Authority, Brand Authority, Spam Score), links and linking domains, anchor text, ranking keywords, top pages, keyword volume, difficulty, opportunity, priority and search intent, related keywords, SERP data and your API quota. You connect it to Claude, ChatGPT or Claude Code, sign in with your Moz account, and ask questions in plain English.

Do I need Moz Pro to use the Moz Data MCP server?

No, and Moz Pro alone will not give you access. The Moz Data MCP endpoint requires a Moz Data API subscription, which is a separate product from Moz Pro. Moz Pro is the web app with campaigns, rank tracking and reporting. The Moz API is the data layer underneath it, sold by the row. You can hold both subscriptions, but neither includes the other.

Is there a free tier for the Moz Data MCP server?

Yes, a small one. Moz’s free API access allows one request every ten seconds and up to 50 rows per month. Because a single ranking keywords call can return up to 50 rows, the free tier is enough to confirm the connection works and not much more. Paid plans start at 20 US dollars a month for 3,000 rows, and every paid tier lists MCP access as beta enabled.

How does the Moz Data MCP server authenticate?

Two ways. The recommended path is OAuth: when you add the server in Claude, ChatGPT or Claude Code, the client walks you through a browser sign-in with your Moz account, so no API key is stored. If your client does not support OAuth, you can instead send your Moz API key as a Bearer token in the Authorization header. The same token works for both the Data and Local endpoints.

Is the Moz Data MCP server read-only?

Yes. Every tool on the Data endpoint reports data and none of them can change anything in your Moz account. The separate Moz Local endpoint is different: it includes tools that create, update, cancel and close business locations.

What does the Moz Data MCP cost per question?

Every tool call spends API quota measured in rows, and the cost varies by method. Fetching site metrics for one URL costs one row. Keyword metrics cost one row per returned value, up to five. A ranking keywords or linking domains list costs one row per result returned. Fetching a SERP costs 15 rows. An assistant answering a broad question may make several calls, so a single prompt can easily spend 50 to 100 rows.

Which AI clients work with the Moz Data MCP server?

Moz documents Claude Desktop (where Moz Data and Moz Local are both listed in the built-in connector directory), ChatGPT Desktop (added manually by URL) and Claude Code (via the claude mcp add command with either OAuth or a Bearer token). Because it is a standard remote MCP server, it also works in other clients that support remote connectors, including Growth Method’s custom integrations.

Why can’t my team members connect the Moz Data MCP?

During the beta, Moz restricts MCP access to Moz account owners. Seated users on the same account cannot connect yet. Moz says it is working to expand access to seated users.