SearchAtlas

What SearchAtlas MCP server does

SearchAtlas MCP server gives MCP-compatible AI clients access to the SearchAtlas v2 platform. Its tool catalogue covers SEO automation through OTTO, PPC and Google Ads workflows, Content Genius, Site Explorer, Google Business Profile, local SEO heatmaps, Link Laboratory, Digital PR, LLM Visibility, keyword rank tracking, Google Search Console, social publishing, content strategy, knowledge graphs, indexing, and report building.

The available catalogue is discovered from the hosted v2 service rather than being fixed entirely in the local package. The README reports roughly 587 tools at the time of writing, with new tools becoming available through the hosted service without requiring a package update. Exact availability can be checked with the CLI or by asking the connected client to list its tools.

Typical requests include running a technical site audit, finding long-tail keywords, reviewing keyword performance, generating a content brief, listing projects, checking LLM visibility, or running an available playbook. The agent selects from the exposed tools based on the request.

How it works

The npm package acts as a thin stdio adapter. It starts locally for clients that communicate through standard input and output, then connects to https://mcp.searchatlas.com/mcp/, the hosted SearchAtlas v2 MCP endpoint. Clients with native Streamable-HTTP support can use the remote endpoint directly instead of the local bridge.

SearchAtlas MCP server uses credentials obtained through the SearchAtlas login flow. The CLI can open a browser for authentication, accept a token copied from the browser’s local storage, validate it, and save it in ~/.searchatlasrc. At runtime, credential lookup checks SEARCHATLAS_TOKEN first, then SEARCHATLAS_API_KEY, and finally the saved configuration file.

Setup and configuration

The package requires Node.js 18 or newer. It can be installed globally with npm, Yarn, or pnpm, or invoked with npx. The MCP client configuration starts the package with npx -y searchatlas-mcp-server or points directly to the installed package’s JavaScript entry point.

Run searchatlas login to authenticate and generate client configuration examples. Run searchatlas check to validate the saved credentials, endpoint configuration, token structure, and MCP handshake. SEARCHATLAS_API_URL can override the default hosted endpoint when a different v2 MCP URL is required.

Full executable paths may be needed in desktop applications because GUI clients may not inherit the shell’s PATH. The login command detects local paths and prints configurations intended for supported clients.

Tools and capabilities

Tool groups documented by the project include:

• OTTO SEO project and optimization operations
• PPC accounts, campaigns, and keyword performance
• Content Genius articles, editing, and briefs
• Site Explorer details and backlink analysis
• Google Business Profile and citation workflows
• Local SEO heatmaps and rank checks
• Link Laboratory orders and projects
• Digital PR campaigns
• LLM Visibility reports and projects
• Keyword rank tracking
• Google Search Console performance data
• Social Hub posts and Content Strategy resources
• Knowledge Graph, Domain Knowledge Network, Indexer, and Report Builder operations

SearchAtlas MCP server exposes representative operations such as listing projects, adding sites, creating campaigns, generating briefs, retrieving visibility reports, tracking keywords, submitting indexing batches, and managing reports. The precise tool set is live and may change independently of the npm package.

Limitations and notes

The local package does not provide an independent SearchAtlas data service; it bridges clients to the hosted v2 MCP endpoint. A SearchAtlas token or API key is needed for authenticated access. The README documents client configurations for Claude Desktop, Cursor, Windsurf, VS Code, Zed, and Claude Code, while this listing identifies MCP client compatibility where supported by the directory schema.

The tool count and groups are reported as current examples rather than a permanent API contract. Use searchatlas check or inspect the connected client’s tool list before relying on a particular operation. On Windows, Claude Code configurations use npx.cmd rather than npx.