PlugWiki
dataforseo-mcp-server logo

DataForSEO MCP Server: Setup for Claude, Cursor and Other Apps

OfficialRemoteLocal
Getnpmdataforseo-mcp-serverdataforseo/mcp-server-typescript
Tools
4
1 read · 3 change
Stars
256
on GitHub
Downloads
12.8K
a week
Works in
14
apps
Risk
High
can delete

Lets Claude, Cursor and other assistants read the DataForSEO docs and call its SEO APIs for search results, backlinks and more.

This is DataForSEO's own server. It has four tools: three to browse the API docs, and one that makes the actual calls, so the assistant works out which endpoint to use and then runs it. You can use the hosted server and sign in with your DataForSEO account, or run it on your computer with your API login and password.

You need a DataForSEO account either way. This is the new v3 server, and the older v2 server is marked deprecated.

Good for

  • SEO specialists who want live search results and backlink data pulled into a chat
  • Developers building on DataForSEO who want the assistant to find the right endpoint and fields
  • Agencies that already have a DataForSEO account and want quick one-off reports

Works in

14 should work

Tap an app to see how to set it up and any known problems.

Install dataforseo-mcp-server

Claude Code

  1. 1

    Copy this prompt.

    Add the dataforseo-mcp-server server to Claude Code. Run this command:

claude mcp add --transport http dataforseo https://mcp.dataforseo.com/v3/mcp

Ask me for DATAFORSEO_LOGIN, DATAFORSEO_PASSWORD and only put the values in that config, nowhere else.

Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Sign-in with the vendor account (OAuth).

Built from the package data we hold. Not yet tested by us.

Tools

  • Lists the sections of the DataForSEO API docs

    Returns the names of the documentation sections, such as SERP API, so the assistant knows where to look.

    Try: “What parts of the DataForSEO API can you use?”

    Network · docs_list_sections

  • Gets the list of DataForSEO API endpoints

    Fetches the documentation index (the llms.txt file), and can narrow it to one section. Results are cached for 24 hours.

    Try: “List the endpoints in the SERP API section”

    Write · docs_index

  • Reads the docs page for one endpoint

    Fetches the documentation for a docs URL or path, so the assistant can see which fields an endpoint takes. It can include code examples in several languages.

    Try: “Read the docs for the Google organic live SERP endpoint”

    Write · docs_search

  • Calls any DataForSEO API endpoint as your account

    Sends a GET, POST, PUT or DELETE request to the path or URL you give, with a JSON body, using your credentials. This is the tool that fetches the actual data.

    Try: “Get the top 10 Google results for "standing desk" in the US”

    Delete · api_request

Read from the source code

Permissions

high risk · 3 things to watch

High risk

The assistant can send any request to the DataForSEO API as your account, including DELETE, and there is no read-only mode. Use the hosted sign-in or a dedicated API login, and review each request before it runs.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • One tool can call any endpoint, including DELETE

    api_request accepts GET, POST, PUT and DELETE, and there is no read-only mode. Use an API login you can afford to lose and check each request before you approve it. github.com

  • The local web mode listens on every network address

    Started with --mode http, the server binds to all interfaces and falls back to the login in your environment when a caller sends none. Use the default mode instead, or keep the port behind a firewall. github.com

  • Your API password is stored in plain text in the config

    The local setup puts DATAFORSEO_PASSWORD in your app's config file. Use the hosted sign-in if you would rather not store it. github.com

Security advisories

No published security advisories as of Nov 1, 2026.

Technical details
Talks tomcp.dataforseo.com (hosted server). api.dataforseo.com (API calls). docs.dataforseo.com (documentation)
Sign-in and keysHosted: you sign in with your DataForSEO account. Local: your API login and password sit in the app's config as environment variables.

Questions

Is the DataForSEO MCP server official?

Yes. DataForSEO publishes it in its own GitHub organization and runs the hosted version at mcp.dataforseo.com. The older v2 server is deprecated.

What is the DataForSEO MCP server URL?

The hosted server is https://mcp.dataforseo.com/v3/mcp. You sign in with your DataForSEO account, so no API password goes into the config.

Should I use the hosted server or run it locally?

Use the hosted server if your app supports remote servers, because you sign in and store no password. Run it locally if you want it on your own machine, with your API login and password in the config. It needs Node.js 22 or later.

Do I need a DataForSEO account?

Yes. Hosted use signs in with your account. Local use needs the API login and password from the API access page in your DataForSEO dashboard.

Can it run read-only?

No. The three docs tools only read, but api_request can send write and delete requests. Use an API login you are comfortable with and review requests before approving them.

Why does the assistant only have four tools?

The server does not wrap each API in its own tool. The assistant reads the docs, picks an endpoint and calls it through one request tool. That keeps the tool list short, but the assistant needs a clear question.

Can it cut down what a response contains?

Yes. You can give it a field configuration file that lists which fields to keep for each endpoint path. That makes large responses smaller. The README has an example.

Information

updated Nov 2, 2026

Publisher
Official
Package
dataforseo-mcp-server
Registry
npm
Transport
stdio, Streamable HTTP
Auth
OAuth
Version
3.1.3
License
Apache-2.0
Last commit
Oct 2, 2026

GitHubnpm

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 2
  1. DataForSEO MCP Server README · github.com
  2. Tool registrations at the 3.1.3 release · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.