SE Ranking SEO Data API MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SE Ranking SEO Data API MCP Server get keyword rankings for example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Server
Installation
Getting a copy of the project
Save a copy of the project to a local directory, for example /path/to/seo-data-api-mcp-server.
Set up environment variables
The SE Ranking Data API access key is set via an environment variable, which can be done globally or through the Claude Desktop configuration.
export SERANKING_API_TOKEN=your-token-hereOption 1: Installation as an NPM package
Prerequisites
Node.js 18+
cd /path/to/seo-data-api-mcp-server
npm install
npm run build
# Check that the build starts successfully and press Ctrl+C to stop it.
npm startOption 2: Build the Docker Image
Prerequisites
Docker, Docker Compose
cd /path/to/seo-data-api-mcp-server
docker compose build
# Check that the image is built and named `se-ranking/seo-data-api-mcp-server`:
docker image lsConnect to Claude Desktop
Claude Desktop reads its configuration from claude_desktop_config.json.
Click on the Claude menu and select “Settings…”.
In the Settings window, navigate to the “Developer” tab in the left sidebar.
Click the “Edit Config” button to open the configuration file. This action creates a new configuration file if one doesn’t exist, or opens your existing configuration.
The file is located at:
macOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json
Windows: %AppData%\Claude\claude_desktop_config.json
Linux: ~/.config/Claude/claude_desktop_config.json
Example of Claude Desktop configuration for MCP server, running via Node:
{
"mcpServers": {
"se-ranking/seo-data-api-mcp-server": {
"command": "node",
"args": ["/path/to/seo-data-api-mcp-server/dist/index.js"],
"env": {
"SERANKING_API_TOKEN": "your-token-here"
}
}
}
}Example of Claude Desktop configuration for MCP server, running via docker image:
{
"mcpServers": {
"se-ranking/seo-data-api-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SERANKING_API_TOKEN",
"se-ranking/seo-data-api-mcp-server"
],
"env": {
"SERANKING_API_TOKEN": "your-token-here"
}
}
}
}After saving claude_desktop_config.json, restart Claude Desktop. You should see the server under MCP Servers/Tools.
Available Tools
25 toolsbacklinksAllBacklinks AllA
Fetch backlinks pointing to a single target with sorting, limits, rank filters, URL/anchor filters, and nofollow filter (v1/backlinks/all)
Inputs: target (required), mode, limit, output, +13 more.
backlinksAnchorsBacklinks AnchorsB
Fetch anchor texts of backlinks pointing to a single target with sorting and limit controls (v1/backlinks/anchors)
Inputs: target (required), mode, limit, output, +1 more.
backlinksAuthorityBacklinks AuthorityC
Fetch authority metrics for a target (domain, host or URL) (v1/backlinks/authority)
Inputs: target (required), output.
backlinksIndexedPagesBacklinks Indexed PagesB
Fetch site pages that have backlinks, with sorting and limit controls (v1/backlinks/indexed-pages)
Inputs: target (required), mode, limit, output, +1 more.
backlinksRefdomainsBacklinks Referring DomainsB
Fetch referring domains pointing to a single target with sorting and limit controls (v1/backlinks/refdomains)
Inputs: target (required), mode, limit, output, +1 more.
backlinksSummaryBacklinks SummaryB
Fetch extended backlink statistics for one or multiple targets. Optionally builds an analysis prompt comparing your domain vs a competitor for a given keyword (v1/backlinks/summary)
Inputs: target (required), mode, output.
domainAdsByDomainDomain Ads by DomainC
Fetch domain ads by domain (v1/domain/ads)
Inputs: domain (required), source (required), to, from, +2 more.
domainAdsByKeywordDomain Ads by KeywordC
Fetch domain ads by keyword (v1/domain/ads)
Inputs: source (required), keyword (required), to, from, +2 more.
domainAioDiscoverBrandAIO Discover BrandC
Fetch AI Overviews brand names (v1/domain/aio/discover-brand)
Inputs: source (required), target (required), scope.
domainAioKeywordsByBrandAIO Keywords by BrandC
Fetch AI Overviews domain keywords by brand (v1/domain/aio/keywords-by-brand)
Inputs: brand (required), source (required), sort, limit, +20 more.
domainAioKeywordsByTargetAIO Keywords by TargetC
Fetch AI Overviews domain keywords by target (v1/domain/aio/keywords-by-target)
Inputs: source (required), target (required), sort, limit, +20 more.
domainAioOverviewAIO OverviewC
Fetch AI Overviews domain metrics (v1/domain/aio/overview)
Inputs: source (required), target (required), scope.
domainCompetitorsDomain CompetitorsC
Fetch domain competitors (v1/domain/competitors)
Inputs: domain (required), source (required), type, stats.
domainKeywordsDomain KeywordsC
Fetch domain keywords (v1/domain/keywords)
Inputs: domain (required), source (required), cols, page, +22 more.
domainKeywordsComparisonDomain Keywords ComparisonA
Analyzes and compares the keyword rankings of two websites: domain and compare. It can find keywords they have in common or identify a 'keyword gap'—keywords for which the domain ranks, but the compare domain does not.
Inputs: domain (required), source (required), compare (required), cols, +6 more.
domainKeywordsReverseComparisonDomain Keywords Reverse ComparisonC
Compare keywords across domains (v1/domain/keywords/comparison)
Inputs: domain (required), source (required), compare (required), cols, +5 more.
domainOverviewDomain OverviewC
Fetch domain overview (v1/domain/overview)
Inputs: domain (required).
domainOverviewDbDomain Overview DBC
Fetch domain overview by database (v1/domain/overview/db)
Inputs: domain (required), source (required), with_subdomains.
domainOverviewHistoryDomain Overview HistoryB
Fetch domain historical overview (v1/domain/overview/history)
Inputs: domain (required), source (required), type.
domainOverviewWorldwideDomain Overview WorldwideC
Fetch domain worldwide overview (v1/domain/overview/worldwide)
Inputs: domain (required), fields, currency, show_zones_list.
keywordsExportExport Keywords MetricsC
Bulk retrieve metrics for a list of keywords (v1/keywords/export, POST form-data; source in query)
Inputs: source (required), keywords (required), cols, sort, +1 more.
keywordsLongtailLongtail KeywordsC
Fetch longtail (low search volume) keywords (v1/keywords/longtail)
Inputs: source (required), keyword (required), sort, limit, +15 more.
keywordsQuestionsKeyword QuestionsC
Fetch keyword questions (v1/keywords/questions)
Inputs: source (required), keyword (required), sort, limit, +16 more.
keywordsRelatedRelated KeywordsC
Fetch related keywords (v1/keywords/related)
Inputs: source (required), keyword (required), sort, limit, +16 more.
keywordsSimilarSimilar KeywordsC
Fetch similar keywords from SE Ranking Data API (v1/keywords/similar)
Inputs: source (required), keyword (required), sort, limit, +16 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 25 tools
Most tools are clearly separated by resource area, but domainOverview, domainOverviewDb, and domainOverviewWorldwide are easy to confuse without deeper API knowledge. The domainKeywordsComparison/domainKeywordsReverseComparison pair is also ambiguous since their descriptions don't clearly distinguish the two modes.
All names use camelCase and are grouped by resource prefixes like domain, backlinks, and keywords, which creates a predictable feel. There are minor inconsistencies in qualifier order, such as domainOverviewHistory versus domainKeywordsComparison, but no chaotic mixing of naming styles.
At 25 tools, this server sits at the heavy end of the expected range. Many tools are narrow wrappers around specific API endpoints, and some, like the domain overview variants, could potentially be consolidated without losing clarity.
The tool set covers major SEO data areas well: domain metrics, backlinks, keyword research, ads, competitors, and AI overviews. It lacks some niche historical or advanced backlink endpoints, but typical workflows for an SEO data API can be completed without obvious dead ends.
Related MCP Connectors
Query your SEO data in plain language: rankings, audits, backlinks, competitors and AI visibility.
SEO data your AI can cite: Search Console, GA4, keywords, backlinks, SERPs and AI visibility.
Live SEO intelligence, rank tracking, site audits, and backlink analysis for AI agents.
Ask your web and product analytics: traffic, funnels, goals, revenue and sessions.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables to access SE Ranking SEO data through natural language queries, providing keyword analysis, competitor research, and performance tracking.281Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables querying Google Search Console and Google Analytics 4 through natural language, with tools for SEO analysis like anomaly detection, cannibalization detection, and opportunity scoring.14 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables querying Google Search Console data, including search analytics with advanced filtering, quick wins detection, and rich dimensions, through natural language.6,899 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables querying Google Search Console data such as search analytics and site list via natural language.153 npmMIT