seo-stack-mcp

What this does

seo-stack-mcp exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

GOOGLE_APPLICATION_CREDENTIALS
SEO_STACK_OAUTH_CLIENT
GA4_PROPERTY_ID
GSC_SITE_URL
ADSENSE_ACCOUNT_ID
ADSENSE_CURRENCY
BING_WEBMASTER_API_KEY
BING_SITE_URL
CLARITY_API_TOKEN
GOOGLE_ADS_DEVELOPER_TOKEN
GOOGLE_ADS_CLIENT_ID
GOOGLE_ADS_CLIENT_SECRET
GOOGLE_ADS_REFRESH_TOKEN
GOOGLE_ADS_CUSTOMER_ID
GOOGLE_ADS_LOGIN_CUSTOMER_ID
OPENPAGERANK_API_KEY

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install seo-stack-mcp?

Run the Claude Code command in the install section to add seo-stack-mcp to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with seo-stack-mcp?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to seo-stack-mcp as well.

Does seo-stack-mcp need an API key?

Yes. Before it can run, set these environment variables: GOOGLE_APPLICATION_CREDENTIALS, SEO_STACK_OAUTH_CLIENT, GA4_PROPERTY_ID, GSC_SITE_URL, ADSENSE_ACCOUNT_ID, ADSENSE_CURRENCY, BING_WEBMASTER_API_KEY, BING_SITE_URL, CLARITY_API_TOKEN, GOOGLE_ADS_DEVELOPER_TOKEN, GOOGLE_ADS_CLIENT_ID, GOOGLE_ADS_CLIENT_SECRET, GOOGLE_ADS_REFRESH_TOKEN, GOOGLE_ADS_CUSTOMER_ID, GOOGLE_ADS_LOGIN_CUSTOMER_ID, OPENPAGERANK_API_KEY. They go in the env block of your MCP config.