SEO Tools MCP Server

What is SEO Tools MCP Server?

The SEO Tools MCP Server is a stdio-based MCP server that allows LLMs to interact with DataForSEO API functions and other SEO tools for tasks like SEO analysis, keyword research, and backlink analysis.

How to use SEO Tools MCP Server?

Clone the repository, install dependencies with npm install, build with npm run build, set environment variables for authentication (DATAFORSEO_LOGIN and DATAFORSEO_PASSWORD; optionally LOCALFALCON_API_KEY), then run with npm start. The server communicates via stdio and can be integrated with LLMs like Claude.

Key features of SEO Tools MCP Server

• Comprehensive coverage of DataForSEO API endpoints
• Optional integration with Local Falcon for local ranking analysis
• Stdio transport for easy integration with LLM platforms
• Authentication handling and detailed error reporting
• Type-safe tool definitions using Zod schemas
• Extensible architecture for adding new API integrations

Use cases of SEO Tools MCP Server

• Perform keyword research and get search volume data via natural language
• Analyze backlink profiles and referring domains for a website
• Run local SEO grid searches to check business rankings in specific areas
• Conduct on-page audits and technical SEO checks
• Gather e-commerce data from Amazon and Google Shopping through the Merchant API

FAQ from SEO Tools MCP Server

What APIs does the SEO Tools MCP Server support?

It fully supports the DataForSEO API (SERP, Keywords, Labs, Backlinks, OnPage, Domain Analytics, Content Analysis, Content Generation, Merchant, App Data, Business Data) and optionally the Local Falcon API for local ranking analysis.

How do I authenticate with the server?

Set the environment variables DATAFORSEO_LOGIN and DATAFORSEO_PASSWORD for DataForSEO. For Local Falcon, set LOCALFALCON_API_KEY (and optionally LOCALFALCON_API_URL).

What transport protocol does the server use?

The server uses stdio (standard input/output) as its transport layer.

Can I add support for other SEO APIs?

Yes, the server is designed to be extensible. You can create a new integration directory in src/api/, implement client handling and tool registration, then add it to src/index.ts and handle authentication via environment variables.

Does the server require any external runtime?

It requires Node.js and npm for installation and building. The server is built from TypeScript source.