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., "@seo-data-api-mcp-server show me my top 10 organic keywords"
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
Prerequisites
Before you begin, please ensure you have the following software and accounts ready:
SE Ranking Account: You will need an active SE Ranking account to generate an API token. If you don’t have one, you can sign up here.
Docker: A platform for developing, shipping, and running applications in containers. If you don’t have it, you can download it from the official Docker website.
Docker Compose Plugin: The Docker Compose plugin is a Docker CLI plugin that provides a command-line interface (CLI) for Docker Compose. To build the Docker image, you need to have Docker Compose installed.
Git: A free and open-source distributed version control system. You can download it from the official Git website.
AI Assistant: You will need either the Claude Desktop App or the Gemini CLI installed and configured on your machine.
Installation Steps
Follow these steps to install the SEO-MCP server on your local machine.
Open your terminal (or Command Prompt/PowerShell on Windows).
Clone the project repository from GitHub. This command downloads the necessary files to your machine.
git clone https://github.com/seranking/seo-data-api-mcp-server.gitNavigate into the new directory in your terminal:
cd seo-data-api-mcp-serverBuild the Docker Image
Make sure you're in the seo-data-api-mcp-server repository directory, and run:
docker compose build
# Check that the image is built and named `se-ranking/seo-data-api-mcp-server`:
docker image lsNote: don't worry about the warnings, this is normal when building the image:
WARN[0000] The "SERANKING_API_TOKEN" variable is not set. Defaulting to a blank string.How to Update SEO-MCP
To ensure you have the latest features and improvements, you should update the tool periodically.
Navigate to your
seo-data-api-mcp-serverdirectory in the terminal.Pull the latest changes from the GitHub repository.
git pull origin mainRelated MCP server: SE Ranking SEO Data API MCP Server
Connect 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.jsonWindows:
%AppData%\Claude\claude_desktop_config.jsonLinux:
~/.config/Claude/claude_desktop_config.json
Example of Claude Desktop configuration for MCP server
JSON Configuration Template:
{
"mcpServers": {
"seo-data-api-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SERANKING_API_TOKEN",
"se-ranking/seo-data-api-mcp-server"
],
"env": {
"SERANKING_API_TOKEN": "<your-api-token-here>"
}
}
}
}You need to change the SERANKING_API_TOKEN, get yours from https://online.seranking.com/admin.api.dashboard.html
After saving claude_desktop_config.json, restart Claude Desktop. You should see the server under MCP Servers/Tools.
To verify the setup, ask Claude:
Do you have access to MCP?It should respond by listingseo-data-api-mcp.

Your setup is complete! You can now run complex SEO queries using natural language.

Connect to Gemini CLI
Open the Gemini CLI settings file, which is typically located at:
~/.gemini/settings.jsonAdd the following JSON configuration, making sure to replace the SERANKING_API_TOKEN placeholder value.
{
"mcpServers": {
"seo-data-api-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SERANKING_API_TOKEN",
"se-ranking/seo-data-api-mcp-server"
],
"env": {
"SERANKING_API_TOKEN": "<your-api-token-here>"
}
}
}
}"SERANKING_API_TOKEN": Use your personal API token, which you can generate from the SE Ranking API Dashboard.
Save the configuration file.
To verify the setup, launch the Gemini CLI by running
geminiin your terminal. Once the interface is active, pressCtrl+Tto view the available MCP servers. Ensure seo-data-api-mcp is listed.

Your setup is complete! You can now run complex SEO queries using natural language.

Run as HTTP Server (Node)
In order to run the local Node server, you need to have Node.js 20+ version installed on your machine.
Run the following commands in your terminal:
npm installTo build the project, use the following command:
npm run buildTo start the server use the command:
npm run start-httpThen your HTTP server should be running at: http://0.0.0.0:5000/mcp.
In case you'd like to modify the HOST and PORT, you can do so by creating a .env file in the root directory of the project with the settings you want to override, for example:
HOST=127.0.0.1
PORT=5555Additionally, when you're running the server in the external environments/tools like Replit and similar, you can set the SERANKING_API_TOKEN environment variable in the configuration panel, and the application will use it when you start the server.
Note: If you change the SERANKING_API_TOKEN value when the server is running, you need to restart the server.
Usage Example: Finding Keyword Opportunities
With the configuration complete, you can now use natural language prompts to interact with your SE Ranking data. Here is an example prompt to identify low-hanging keyword opportunities for a domain.
Copy and paste the following into your configured AI assistant:
Use the seo-mcp to identify the Keywords my domain is overlooking and find low-hanging fruit opportunities.
1. Analyze my domain's keyword performance:
- Find keywords my domain has lost (not ranking) using the tool for domainKeywords with pos_change=lost.
- Find keywords where my domain's position has gone down using the tool for domainKeywords with pos_change=down.
2. Conduct a competitive analysis:
- Identify my top 2 competitors by finding all competitors with the tool for domainCompetitors and ordering them by common_keywords DESC.
- Find 30 keywords that these competitors are ranking for but my domain is not. Use the domainKeywordsComparison tool with diff=1, order_field=volume, and order_type=DESC.
3. Identify new keyword opportunities:
- For 10 of the competitor keywords found in the previous step, use the tools for relatedKeywords and similarKeywords to find the top 5 related and similar keywords for each, ordered by volume DESC.
4. Synthesize and Report:
- Create a final report of the findings. In the report, highlight potential low-hanging fruit from the new keyword opportunities by analyzing their CPC and keyword difficulty.
Domain to review: seranking.com
Market: usWhat This Prompt Does
This prompt instructs the model to perform a comprehensive competitive analysis by:
Finding Lost & Declining Keywords: It first identifies keywords for seranking.com that have either been lost from the rankings or have dropped in position.
Identifying Top Competitors: It finds all organic competitors and sorts them to identify the top two based on the number of shared keywords.
Uncovering Competitor-Ranked Keywords: It compares seranking.com against its top competitors to find 30 high-volume keywords that they rank for, but seranking.com does not.
Generating a Final Report: Finally, it synthesizes all of this information into a concise report, highlighting the most promising opportunities for growth.
To send the sample test request, which will verify if your server runs properly and has the correct setup, open another terminal window, and run the following command with your SE Ranking API token provided as an argument:
./test-http-server-curl-request.sh '<your-api-token-here>'For batch MCP Requests testing, you can use this script:
./test-batch-http-server-curl-request.sh '<your-api-token-here>'Troubleshooting
Docker image problems
If you’re having trouble getting the MCP server to connect, here are a few steps to diagnose the issue.
Verifying if the Docker container is running when you run your AI Assistant (Claude or Gemini). If you start a chat with an AI, and your MCP Server is set up properly via JSON config, it should automatically start the Docker container.
To check if it’s running, open your terminal and run:
docker psIf it’s working correctly, you will see an output similar to this:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
de4e410ef0fd se-ranking/seo-data-api-mcp-server "docker-entrypoint.s…" 9 seconds ago Up 8 seconds musing_bhabhaThis confirms that your AI assistant has successfully started the container, and it’s listening for connections.
If docker ps shows no running containers related to the MCP server, it usually points to a configuration issue:
Incorrect/invalid JSON: Double-check the claude_desktop_config.json or settings.json for any syntax errors like missing commas or brackets. You can validate the JSON here: https://jsonlint.com/.
Incorrect image name: Double-check the claude_desktop_config.json or settings.json for the correct image name
se-ranking/seo-data-api-mcp-server
Docker image running, but MCP server is not visible in Claude Desktop / Gemini CLI
If the docker image is running, but the MCP server is not visible in Claude Desktop, you can investigate the container by:
docker inspect <container-id>For the following example, the container ID is de4e410ef0fd:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
de4e410ef0fd se-ranking/seo-data-api-mcp-server "docker-entrypoint.s…" 9 seconds ago Up 8 seconds musing_bhabhaNote: you can shorten the container ID in case no other containers share that prefix, ex. docker inspect de4. When you're running multiple AI chats and/or tools connected to the MCP Servers, there can be multiple containers running, but all with the same IMAGE name.
This will show you the big JSON output, where particularly important is the "Config" section, ex.:
{
"Config": {
"Hostname": "0977c3dc06fb",
"Domainname": "",
"User": "",
"AttachStdin": true,
"AttachStdout": true,
"AttachStderr": true,
"Tty": false,
"OpenStdin": true,
"StdinOnce": true,
"Env": [
"SERANKING_API_TOKEN=8abcdef-6fdd-a981-3ad5-123456",
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"NODE_VERSION=20.19.5",
"YARN_VERSION=1.22.22",
"NODE_ENV=production"
]
}
}Which shows you if you have the correct environment variables set.
Support
SE Ranking API documentation: https://seranking.com/api/integrations/mcp/.
In case you have any questions or need help, please contact us at api@seranking.com
Available Tools
28 toolsaiSearchOverviewAI Search Overview (SE Ranking)B
Retrieve a high-level overview of a domain's performance in LLM: link presence, average position, AI traffic, and historical historical dynamics (trends over time).
Inputs: target (required), source (required), engine (required), scope.
aiSearchPromptsByBrandAI Search: Get Prompts by Brand (SE Ranking)B
Fetch a paginated list of prompts where the specified brand is mentioned in LLM results. Maps to /v1/ai-search/prompts-by-brand.
Inputs: engine (required), brand (required), source (required), sort, +11 more.
aiSearchPromptsByTargetAI Search: Get Prompts by Target (SE Ranking)B
Fetch the list of prompts (queries) that refer to or mention a given target (domain/URL) in the AI Search context. Corresponds to SE Ranking’s “Get Prompts by Target” API section.
Inputs: engine (required), target (required), source (required), scope, +12 more.
backlinksAllBacklinks 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, per_domain, +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, order_by, limit, +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, order_by, limit, +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, order_by, limit, +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: source (required), domain (required), from, to, +2 more.
domainAdsByKeywordDomain Ads by KeywordC
Fetch domain ads by keyword (v1/domain/ads)
Inputs: source (required), keyword (required), from, to, +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: source (required), brand (required), scope, sort, +20 more.
domainAioKeywordsByTargetAIO Keywords by TargetC
Fetch AI Overviews domain keywords by target (v1/domain/aio/keywords-by-target)
Inputs: source (required), target (required), scope, sort, +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: source (required), domain (required), type, stats.
domainKeywordsDomain KeywordsC
Fetch domain keywords (v1/domain/keywords)
Inputs: source (required), domain (required), type, order_field, +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: source (required), domain (required), compare (required), type, +6 more.
domainKeywordsReverseComparisonDomain Keywords Reverse ComparisonC
Compare keywords across domains (v1/domain/keywords/comparison)
Inputs: source (required), domain (required), compare (required), type, +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: source (required), domain (required), with_subdomains.
domainOverviewHistoryDomain Overview HistoryB
Fetch domain historical overview (v1/domain/overview/history)
Inputs: source (required), domain (required), type.
domainOverviewWorldwideDomain Overview WorldwideC
Fetch domain worldwide overview (v1/domain/overview/worldwide)
Inputs: domain (required), currency, fields, 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), sort, sort_order, +1 more.
keywordsLongtailLongtail KeywordsC
Fetch longtail (low search volume) keywords (v1/keywords/longtail)
Inputs: source (required), keyword (required), limit, offset, +15 more.
keywordsQuestionsKeyword QuestionsC
Fetch keyword questions (v1/keywords/questions)
Inputs: source (required), keyword (required), limit, offset, +16 more.
keywordsRelatedRelated KeywordsC
Fetch related keywords (v1/keywords/related)
Inputs: source (required), keyword (required), limit, offset, +16 more.
keywordsSimilarSimilar KeywordsC
Fetch similar keywords from SE Ranking Data API (v1/keywords/similar)
Inputs: source (required), keyword (required), limit, offset, +16 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 28 tools
Tools are grouped by clear prefixes (aiSearch, backlinks, domain, keywords), making their purposes generally distinct. However, minor overlap exists within domain overview variants and keyword-related tools, and 'domainKeywordsComparison' vs 'domainKeywordsReverseComparison' may cause confusion.
The naming follows a consistent camelCase pattern with category prefixes. Most tools are well-structured, though a few, like 'domainKeywordsReverseComparison', break the typical verb-noun pattern slightly.
With 28 tools, the set is slightly larger than ideal but still well-scoped for a comprehensive SEO data API covering multiple subdomains. Each tool serves a specific function, and no tool appears redundant.
The toolset covers a wide range of SEO data retrieval tasks, including AI search, backlinks, domain analysis, and keywords. However, it lacks write operations (e.g., create, update) and some advanced backlink analysis tools, leaving minor gaps.
Maintenance
Related MCP Connectors
Query your SEO data in plain language: rankings, audits, backlinks, competitors and AI visibility.
SEO, GEO & AI Visibility Intelligence directly inside AI assistants. Chat with SEO in plain language: research keywords, analyze SERPs, track competitors, and monitor AI visibility. SeoPerseo's integrated intelligence reveals site issues and how to fix them, create client reports and generate content for your website. Fully integrated with Google Search Console and Google Analytics.
Live SEO intelligence, rank tracking, site audits, and backlink analysis for AI agents.
SEO data your AI can cite: Search Console, GA4, keywords, backlinks, SERPs and AI visibility.
Related MCP Servers
- AlicenseCqualityDmaintenanceConnects AI assistants to SE Ranking's SEO and project management APIs to enable natural language queries for keyword research, backlink analysis, and technical audits. It supports comprehensive tasks including competitive analysis, domain traffic tracking, and AI search visibility monitoring.1001Apache 2.0
- FlicenseBqualityDmaintenanceEnables querying the SE Ranking API for SEO data and analytics using natural language.25-
- 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.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables SEO analytics via the Semrush Analytics API, allowing AI agents to query Semrush data through natural language.81 npmMIT