SearchAtlas

**npm** · **MCP Registry** · **GitHub**
Connect any MCP-compatible AI client to the **SearchAtlas v2 MCP server** — 500+ tools covering OTTO SEO, PPC, Content Genius, Site Explorer, Google Business Profile, Local SEO, Link Laboratory, Digital PR, LLM Visibility, keyword research, and more.
This package runs as a thin stdio bridge to the hosted v2 MCP server at https://mcp.searchatlas.com/mcp/ so it works with clients that only speak stdio. Clients with native Streamable-HTTP support can connect to the remote endpoint directly.
Works with **Claude Code, Cursor, Claude Desktop, VS Code, Windsurf, and Zed**.
---
Setup (3 steps)
1. Install & log in
**With npm:**
**With yarn:**
**With pnpm:**
**Without installing (npx):**
This opens your browser. After logging in:
1. Press **F12** (or **Cmd+Option+I** on Mac) to open DevTools
2. Go to **Console** tab
3. Run: localStorage.getItem("token")
4. Copy the result and paste it into the terminal
The CLI validates your token, saves it, and **prints ready-to-paste configs with your paths auto-detected**.
2. Add to your MCP client
Claude Code
**macOS / Linux:**
**Windows (PowerShell):**
> **Windows note:** You must use npx.cmd instead of npx. This is because Claude Code spawns processes directly and Windows requires the .cmd extension.
Done. That's it.
Cursor
Create .cursor/mcp.json in your project root (or ~/.cursor/mcp.json for global):
> **Your paths may differ.** Run which node and npm root -g to find them, or just copy the config that searchatlas login printed — it has your exact paths.
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
Restart Claude Desktop after saving.
Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
VS Code (GitHub Copilot)
Add to .vscode/mcp.json in your project:
Zed
Add to Zed settings.json:
3. Verify
---
Why full paths?
macOS GUI apps (Cursor, Claude Desktop, VS Code, Windsurf, Zed) **don't inherit your shell's PATH**, so they can't find node or npx. Using the full path to node and pointing it directly at the installed package avoids spawn npx ENOENT and env: node: No such file errors entirely.
searchatlas login detects your paths automatically and prints configs you can copy-paste.
| How to find your paths | Command |
|------------------------|---------|
| Full path to node | which node |
| Global npm modules dir | npm root -g |
---
Usage
Just talk naturally. The AI picks the right tool:
---
CLI Commands
| Command | Description |
|---------|-------------|
| searchatlas login | Log in, save token, print MCP configs |
| searchatlas check | Validate credentials + API connectivity |
| searchatlas --version | Print version |
| searchatlas --help | Show help |
> All commands also work via npx searchatlas-mcp-server .
---
Tools
Tools are discovered dynamically from the hosted v2 MCP server — your client sees the live catalogue (currently ~587 tools) without needing a package update when new ones ship. The major groups:
| Prefix | Area | Representative tools |
|--------|------|----------------------|
| otto_* | OTTO SEO automation (70 tools) | otto_list_projects, otto_add_site, otto_get_dynamic_optimizations |
| ppc_* | Google Ads / PPC (76 tools) | ppc_list_accounts, ppc_create_campaign, ppc_get_keyword_performance |