dataforseo

This MCP server exposes DataForSEO API endpoints and optional Local Falcon integration as tools accessible via the Model Context Protocol (MCP). It enables LLMs to perform SEO-related tasks such as keyword research, SERP data retrieval, backlink analysis, on-page checks, and domain analytics by calling standardized tools mapped to the underlying DataForSEO APIs. By default, hundreds of tools are exposed, but you can selectively enable modules and tools using environment variables to reduce context usage and improve discovery speed. To use the server with an LLM, point the MCP client at the server, authenticate with the configured DataForSEO credentials, and start issuing tool calls like serp_google_organic_live, keywords_google_ads_search_volume, backlinks_summary, and more. If you also enable Local Falcon, you can run local geographic queries and grid-based ranking analyses through the Local Falcon integration.

Prerequisites:

• Git
• Node.js and npm (recommended latest LTS)

Installation steps:

1. Clone the repository git clone https://github.com/Skobyn/dataforseo-mcp-server.git

2. Change to the project directory cd dataforseo-mcp-server

3. Install dependencies npm install

4. Build the project (if applicable for this distribution) npm run build

5. Run the server npm start

Notes:

• If you plan to customize environment variables, set them in your shell or your deployment environment before starting the server (see below for examples).

Environment variables and configuration tips:

• DATAFORSEO_LOGIN and DATAFORSEO_PASSWORD are required to authenticate with the DataForSEO API when using that module set.
• LOCALFALCON_API_KEY is optional and enables Local Falcon integration for local ranking analyses.
• LOCALFALCON_API_URL can be set to a custom Local Falcon endpoint if needed.
• ENABLED_MODULES can be used to enable only specific API categories (comma-separated, case-insensitive), e.g. export ENABLED_MODULES="SERP,LABS,BACKLINKS".
• ENABLED_TOOLS provides fine-grained control over individual tools (comma-separated, case-insensitive).
• If neither ENABLED_MODULES nor ENABLED_TOOLS is set, all modules and tools are exposed by default.
• The server uses stdio for transport; ensure your MCP client is compatible with stdio-based MCP calls.
• For production deployments, consider setting up proper environment management, logging, and rate-limiting as needed.