SE Ranking MCP vs API (2026): What’s Different, What’s Shared, Costs

Reviewed September 2026. SE Ranking now ships both a classic REST API and a remote MCP server so AI assistants (Claude, Cursor, Codex, and others) can query SEO/GEO data in natural language. This guide explains what MCP is, how it relates to the Data API and Project API, what is similar vs distinct, and how pricing/credits work – checked against SE Ranking’s official API docs and pricing pages.

BoostPlanner is reader-supported. If you buy through a link on my site, I may earn an affiliate commission.

If you already use SE Ranking in the browser, think of MCP as “SE Ranking inside your AI client,” and the REST API as “SE Ranking inside your code, dashboards, and automations.” Most teams will use one path as primary and keep the other as a fallback. For plan context, see SE Ranking pricing; for AI SEO tooling more broadly, see AI SEO tools.

What is the SE Ranking MCP server?

MCP (Model Context Protocol) is an open standard for connecting AI apps to external tools and data. SE Ranking hosts an official remote MCP server at:

https://api.seranking.com/mcp

Per SE Ranking’s MCP docs, that server exposes 160+ tools covering keyword research, backlinks, domain analysis, website audits, AI search visibility, SERP analysis, and project management – with more on the way. You connect from Claude, Cursor, Codex, VS Code (via mcp-remote), Windsurf, Gemini CLI, and other MCP-capable clients.

Important: this is a centrally hosted remote server (Streamable HTTP). You do not have to run a local SE Ranking MCP process for the official path. Older/self-hosted MCP wrappers may still exist in GitHub ecosystems, but the documented production endpoint for clients is the remote URL above.

What is the SE Ranking API?

SE Ranking’s HTTP API is split into two jobs (official “Getting API access” guide):

• Data API: pull research datasets (keywords, backlinks, domain overview, SERP, AI Search, website audit data, and more). Usage is measured in API credits.
• Project API: automate account/project work (projects, keywords, audits, rank tracking, competitors, prompts, etc.). Usage draws on your subscription limits (projects, keywords/day, audit pages), not the credit wallet.

One API key authenticates both. Generate keys in the API Dashboard inside your SE Ranking account. Example auth style from the docs: Authorization: Token YOUR_API_KEY on REST calls.

MCP vs API at a glance

SE Ranking’s own product copy puts it cleanly: the API is for programmatic access and automations; MCP is for conversational access inside an AI assistant. Both can sit on the same account.

What is similar

• Same underlying SE Ranking data platform: keywords, backlinks, audits, AI Search, projects.
• Same commercial door: Core/Growth (and Enterprise), API standalone/wallet/add-on paths, and trial access include MCP in current marketing.
• API key can power MCP headless mode: docs show X-Api-Key (and Bearer) so CI/agents can skip browser OAuth.
• Data vs project split still matters: research pulls consume Data API credits; project automation still respects plan limits either way.
• Official docs + dashboard: API Dashboard is the home for keys; MCP docs live under API → Integrations.

What is distinct

MCP-specific

• Agent-native UX: tools appear inside Claude/Cursor/etc.; you prompt instead of wiring each endpoint.
• OAuth-first desktop/IDE flow: browser approve on first connect; refresh handled by the client.
• Client setup recipes: Claude connectors, Cursor mcp.json, Codex mcp add, VS Code/Windsurf via npx mcp-remote.
• Sub-account caveat: official MCP docs: shared-workspace sub-accounts cannot use “Sign in with SE Ranking” until sub-account API keys ship; workaround is pasting a master-account API key manually.
• Optional SEO Skills pack: SE Ranking publishes open-source Claude Skills that wrap MCP into deliverables (AI Search share of voice, backlink gap, content briefs, clusters, etc.).

API-specific

• Deterministic integrations: exact endpoints, pagination, error codes, credit-per-endpoint control.
• Automation stacks: Make, n8n, Looker Studio, custom backends, scheduled ETL.
• Credit forecasting: Data API costs are documented per endpoint/record; you can model bulk jobs before running them.
• Standalone / wallet / add-on SKUs: buy data access without (or beyond) the full SEO web app seat.
• Documented credit math per endpoint: forecast before bulk jobs using the Data API cost table.

Pricing, credits, and options (checked September 2026)

Always re-verify on SE Ranking subscription and API pricing. Current public framing:

Included with Core / Growth (web app plans)

• Core: $129/mo ($103.20/mo annual): includes 25K API credits/mo and MCP access.
• Growth: $279/mo ($223.20/mo annual): includes 100K API credits/mo and MCP access.
• Enterprise: custom limits; contact SE Ranking for volume/RPS.

There is no separate MCP add-on fee in current marketing – MCP is bundled with API-capable access paths.

Need more Data API credits?

• Pay-as-you-go wallet: from $50 for 250K credits; top up anytime; purchased credits never expire (best for burst or unpredictable volume).
• API add-on (on Core/Growth/Enterprise) – from $540/year (~$45/mo) for 3M credits; annual billing only; Data API + Project API; unused cycle credits don’t carry over (wallet top-ups on top still never expire).
• Standalone Data API: from about $179/mo billed annually (docs also cite from $2,148/year for 12M credits); volume discounts; Data API oriented; no web-app subscription required; MCP included.
• Enterprise API: custom high-volume pricing (marketing cites as low as ~$30/1M credits), custom RPS, custom integrations.

Official “Getting API access” still lists legacy Essential/Pro/Business credit rows for older accounts. New buyers should treat Core = 25K/mo and Growth = 100K/mo as the current web-app purchase lineup.

Trial notes

• SE Ranking’s product trial is 14 days, no credit card, with starter UI limits (projects/keywords/AI prompts) – details on our free trial guide.
• API pricing pages: the 14-day trial includes 100K API credits, full API + MCP from day one, and access to test endpoints. Trial credits expire when the 14-day window ends – don’t assume they equal ongoing Core/Growth monthly allowances.

How to connect MCP (practical)

Minimal Cursor example (project or user mcp.json):

{"mcpServers":{"se-ranking":{"url":"https://api.seranking.com/mcp"}}}

Claude Code (OAuth):

claude mcp add --transport http se-ranking https://api.seranking.com/mcp

Then run /mcp and complete browser login. For headless: pass X-Api-Key from the API Dashboard. Full client recipes (Desktop, Codex, VS Code, Windsurf, Gemini) are on SE Ranking’s MCP documentation.

Claude SEO Skills on top of MCP

SE Ranking publishes open-source SEO Skills (MIT) that wrap MCP into finished deliverables instead of one-off tool calls. Official examples include:

• AI Search share of voice heatmaps
• Backlink gap analysis
• Content briefs with an AI Search angle
• Keyword clusters
• Paid-search intelligence
• Content / technical audits and SERP-fit (SXO) analysis

Repo: github.com/seranking/seo-skills. Skills still consume the same underlying API/MCP access – they organize the work; they don’t bypass credits or plan limits.

Credit burn example (why forecasting matters)

From SE Ranking’s Getting API access guide: if a keyword report costs 10 credits per keyword (record), pulling 1,000 keywords × 50 domains is 500,000 credits in one workflow. That is why conversational MCP use feels “cheap” for spot checks and expensive for naive bulk research – same meter either way.

When to choose which

• Choose MCP first if you live in Claude/Cursor and want keyword, SERP, backlink, audit, or AI Search answers without writing HTTP clients.
• Choose REST API first if you need scheduled jobs, multi-tenant apps, warehouse loads, or deterministic credit control.
• Use both if strategists explore via MCP while engineering productionizes the same workflows via Data/Project API.
• Wallet/standalone if you need SE Ranking datasets without buying a full SEO seat – still confirm MCP inclusion on the SKU you pick.

Cost & ops gotchas

• MCP is not “free unlimited data.” Conversational calls that hit Data API tools still spend credits / respect limits.
• Forecast bulk pulls: one wide keyword×domain matrix can burn hundreds of thousands of credits (SE Ranking’s own example math in the access guide).
• Project actions ≠ credits: creating projects or loading keywords still hits plan caps.
• Sub-accounts: MCP OAuth may require master-key workaround today.
• Auth hygiene: never commit API keys; prefer OAuth for interactive IDEs; rotate keys if leaked.
• Connection troubleshooting: MCP docs mention clearing ~/.mcp-auth and Node updates if connectors error.

Try SE Ranking

If you want to test MCP + API on a live account, start with the 14-day SE Ranking free trial (no card; starter limits apply), then compare Core vs Growth on our pricing guide or official plans page.

FAQs

Is MCP a replacement for the API?

No. MCP is a client protocol layer for AI assistants. The REST API remains the right interface for engineered systems. They complement each other.

Do I pay extra for MCP?

Current SE Ranking pricing presents MCP as included with Core/Growth and with API wallet/standalone/add-on paths – not as a separate line item. You still pay for the plan/credits that fund the data.

Data API vs Project API – which does MCP use?

Both, depending on the tool. Research-style MCP tools map to Data API credit usage; project/rank-tracker/audit management tools map to Project API / subscription limits. Official MCP copy states the API key powers Data/Research and Project Management tools.

Can agencies use MCP for clients?

Yes for workflows, with caution: prefer dedicated keys, respect client data boundaries, and watch credit burn on bulk competitive pulls. Sub-account OAuth limitations may apply on shared workspaces.

Where are the official docs?

• MCP server docs
• Getting API access
• Data API reference
• API pricing
• SE Ranking SEO Skills (GitHub)

Checked September 2026 against SE Ranking MCP docs, Getting API access, API pricing, and subscription cards.