How to Use DataForSEO MCP Server in 2026

Connect the DataForSEO MCP server and SearchConsole.ai to the same AI client. Use SearchConsole.ai to find what happened on your verified website. Then use DataForSEO to add keyword, search engine results page (SERP), competitor, and backlink data.

A Model Context Protocol (MCP) server lets an AI client request data from an external service. The client can compare DataForSEO data with your Google Search Console data in one conversation.

Start with SearchConsole.ai. This order keeps the work focused on pages and queries that have value for your site.

The short answer

The DataForSEO MCP server has no extra fee. A new account includes $1 of test credit. DataForSEO does not require a monthly subscription. When you need more credit, the minimum top-up is $50. The credit stays in your account until you use it. Thus, the $50 top-up is not a $50 monthly cost. See the DataForSEO MCP page and its minimum-payment rules.

We verified these terms on August 7, 2026. API endpoint prices can change. Your AI client can also have a separate plan or usage cost.

Understand what each MCP server can do

Give each server a clear job.

SearchConsole.ai provides read-only Search Console operations. It does not edit your website or your Search Console property. DataForSEO has separate API charges and usage limits.

Connect DataForSEO and SearchConsole.ai to one AI client

Use an AI client that can connect to more than one MCP server. The menus and configuration files are different in each client.

Follow these steps for the hosted server:

1. Connect SearchConsole.ai for free.
2. Add https://searchconsole.ai/mcp to your AI client.
3. Complete the SearchConsole.ai and Google authorization steps.
4. Create a DataForSEO account.
5. Add the DataForSEO hosted MCP server.
6. Complete OAuth, or use the API credentials from the API Access area. The correct method depends on your client.
7. Use a small test request for each server.

Use the official local server

DataForSEO also supplies an official local server. You need Node.js 18 or a later version. You can run the server with this command:

npx -y dataforseo-mcp-server@latest

The local server needs DATAFORSEO_USERNAME and DATAFORSEO_PASSWORD. Get these values from the API Access area in your DataForSEO account. The official DataForSEO MCP repository contains configuration examples.

Do not put an API password in a prompt. Do not save it in a repository. Use your client's secret storage or protected environment variables.

Verify each connection

Test one source at a time. Start with small requests because DataForSEO charges for API use.

Use these test prompts:

Use only SearchConsole.ai. List the Search Console properties that I can access. Show the exact property identifier and permission level.

Use only DataForSEO. Return the first five organic Google results for one test query in Spain. Show the language, location, date, endpoint, and request cost if available.

Check the source name in each result. If the client uses the wrong server, stop the task. Make the source explicit in the next prompt.

Start with SearchConsole.ai

Start each SEO task with your own search evidence. This prevents a large external dataset from directing the work to pages that have no value for your site.

First, ask SearchConsole.ai to find an opportunity:

Use only SearchConsole.ai for the exact property that I select. Compare the last complete 28 days with the preceding 28 days. Exclude incomplete recent dates. Show the pages and queries with the largest changes in clicks, impressions, CTR, and average position. Keep page data and query data separate. State the exact dates, search type, filters, and row coverage.

Select one page after you review the result. Then get the query data for that exact page:

Use SearchConsole.ai for this exact page. Return its leading queries for the same two periods. Show clicks, impressions, CTR, and average position. Identify queries with high impressions and low CTR. Identify queries with an average position from 4 through 20. Do not use an external keyword estimate yet.

This sequence gives the AI a first-party baseline. It also gives you a fixed page, date range, and query set for the DataForSEO research.

Add DataForSEO keyword and SERP data

Give DataForSEO the selected query list. Use the same country and language as the Search Console analysis.

Use DataForSEO for the selected queries. Return Google search-volume data and the current organic results for Spain and Spanish. State the DataForSEO endpoint, location, language, collection date, and request cost. Keep these values separate from Search Console data.

Then ask the AI to join the data:

Join the results by normalized query. Preserve the original query text. Show Search Console clicks, impressions, CTR, and position beside the DataForSEO keyword and SERP data. Do not calculate a combined volume. Mark missing values as missing. Prioritize only opportunities that have first-party demand and a clear business use.

DataForSEO adds market context. SearchConsole.ai shows the part of that market that your site reached.

Use the combination for content updates

Use this workflow for an existing page:

1. Use SearchConsole.ai to find a page with a loss or an opportunity.
2. Get the exact queries for that page.
3. Use DataForSEO to inspect search volume and the current SERP.
4. Compare the search intent with the page content.
5. Inspect the page title, headings, internal links, and structured data.
6. Make only the changes that the evidence supports.
7. Record the deployment date.
8. Use SearchConsole.ai to compare complete periods after Google crawls and processes the page.

Use this prompt after you collect the data:

Use SearchConsole.ai as the source for my site's performance. Use DataForSEO only as the source for external keyword, SERP, competitor, and backlink data. Explain which facts come from each source. For the selected page, identify one content change and one internal-link change that the evidence supports. Do not claim that a third-party volume estimate is a Search Console measurement. Give a validation plan with exact metrics and dates.

Do not rewrite a page only because DataForSEO reports a large volume. The query can have the wrong intent. The location can be wrong. Your site can also have no authority or useful offer for that search need.

Use the combination for backlink work

SearchConsole.ai does not provide a competitor backlink index. DataForSEO can provide external backlink data. SearchConsole.ai gives this backlink work a useful target.

Follow this sequence:

1. Use SearchConsole.ai to find a page with proven impressions and business value.
2. Use DataForSEO SERP data to find comparable pages for the same search need.
3. Use DataForSEO to get page-level backlinks for those pages.
4. Group the links by type, such as editorial citation, original research, tool, template, or industry resource.
5. Remove scraped, irrelevant, and sitewide links from the comparison.
6. Find the useful asset type that your page does not have.
7. Improve the page before you start outreach.
8. Use SearchConsole.ai to monitor the target page after the work.

Use this prompt:

Use SearchConsole.ai to select one page with stable impressions and an average position from 4 through 20. Use DataForSEO to find the current competing pages and their page-level backlinks. Classify the useful links by type. Do not make a list of domains to copy. Recommend one asset that can make our page more useful. State that later ranking changes do not prove that a backlink caused the change.

How accurate is DataForSEO search volume?

No provider is the most accurate for every query, country, and date.

Our Ahrefs versus DataForSEO search-volume accuracy test used 14 podcast-related queries. The average absolute percentage difference for DataForSEO was 79.9%. DataForSEO was closer to the observed Search Console impressions for two of the 14 queries.

This result applies only to that sample. It does not prove that DataForSEO is always less accurate. Search Console impressions are also not total search volume. They count recorded appearances of one property in Google results. DataForSEO estimates all searches in a selected market.

Use these rules for an accuracy check:

• Use the same country and language.
• Use the same keyword spelling.
• Use a complete date period.
• Record the endpoint and collection date.
• Keep Search Console impressions separate from estimated search volume.
• Use absolute differences when you compare values.
• Repeat the test with a useful sample from your own site.

Control API cost and data quality

An AI agent can make many tool calls. Set clear limits before the work starts.

Set a daily spending limit in your DataForSEO account. Ask the agent to estimate the request scope before a large job. Start with a small batch. Enable only the API modules that you need.

For both sources, require this output:

• Source server and endpoint.
• Exact property, domain, page, or query.
• Country, language, device, and search type when applicable.
• Exact dates or collection time.
• Row count and coverage limit.
• Request cost when available.
• Missing data and errors.
• Facts, calculations, and hypotheses in separate sections.

Do not treat a DataForSEO estimate as a first-party fact.

A complete prompt for both MCP servers

Use this prompt after both connections pass their tests:

Use SearchConsole.ai first. For the exact property that I select, compare the last complete 28 days with the preceding 28 days. Find up to five pages with a material loss or a clear opportunity. Then get the leading queries for each selected page. Use DataForSEO to add external keyword, SERP, competitor, and backlink data. Use the same country and language for all external calls. Keep each source in separate columns. State dates, filters, row limits, missing data, endpoints, and API costs when available. Do not merge Search Console impressions with estimated search volume. Recommend no more than three actions. Tie each action to first-party evidence. Give a post-change measurement plan that uses SearchConsole.ai.

This prompt makes SearchConsole.ai the control source. DataForSEO adds context. It does not replace the first-party evidence.

Official sources

• DataForSEO MCP server
• DataForSEO minimum payment
• DataForSEO MCP server repository

Connect SearchConsole.ai for free and use your verified Search Console data with DataForSEO MCP.