Seo MCP Server

SEO tools via x402: briefs, keywords, SERP, backlinks, audits. $0.50-$3/req USDC on Base.

Local serverstdio

What is the Seo MCP server?

Seo MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. SEO tools via x402: briefs, keywords, SERP, backlinks, audits. $0.50-$3/req USDC on Base.

What you get

MCP (Model Context Protocol) server for SEODesignLab's x402-protected SEO endpoints.

What the assistant can call

Once Seo is connected, these are the calls the assistant has available:

  • get_content_brief — /api/briefs/
  • keyword_research — /api/dataforseo/keywords/
  • serp_analysis — /api/dataforseo/serp/
  • backlink_profile — /api/dataforseo/backlinks/
  • on_page_audit — /api/dataforseo/audit/
  • Cursor — Add to your Cursor MCP settings (.cursor/mcp.json in your project root or global settings):

Configuration and credentials

You will need 3 environment variables: SEO_API_BASE, X402_PAY_TO, X402_NETWORK. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

@seodesignlab/mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Among the search and retrieval options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Seo's toolset — get_content_brief, keyword_research, serp_analysis and 3 more — is a fair guide to whether it matches your workflow. It is maintained by SEODesignLab; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the seo mcp server does with a few real requests.

Available tools

ToolWhat it does
get_content_brief/api/briefs/
keyword_research/api/dataforseo/keywords/
serp_analysis/api/dataforseo/serp/
backlink_profile/api/dataforseo/backlinks/
on_page_audit/api/dataforseo/audit/
CursorAdd to your Cursor MCP settings (.cursor/mcp.json in your project root or global settings):

How to install the Seo MCP server

{
  "mcpServers": {
    "seo-tools": {
      "command": "npx",
      "args": ["-y", "@seodesignlab/mcp-server"],
      "env": {
        "SEO_API_BASE": "your-value",
        "X402_PAY_TO": "your-value",
        "X402_NETWORK": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
SEO_API_BASEConfiguration value read at startup.Optional
X402_PAY_TOConfiguration value read at startup.Optional
X402_NETWORKConfiguration value read at startup.Optional

Example prompts to try

  • Use Seo to get content brief.
  • Use Seo to keyword research.
  • Use Seo to serp analysis.

Frequently asked questions

It connects Seo to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (get_content_brief, keyword_research, serp_analysis, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Seo directly.