SearchAtlas MCP Server is an MCP (Model Context Protocol) server bridge tool for marketing scenarios, used to connect MCP-compatible AI clients to the SearchAtlas v2 hosted MCP server.
Purpose: Through this tool, users can directly invoke SearchAtlas's marketing capabilities in AI clients, covering SEO, content generation, PPC, keyword research, site audits, authority building, and LLM brand visibility monitoring, among others.
Main capabilities: This package itself is a lightweight stdio bridge that connects to the hosted v2 MCP server located at https://mcp.searchatlas.com/mcp/ . Tools are dynamically discovered from the hosted server, and clients can see the live catalog (currently about 587 tools), with no need to update the package when new tools are added. The main tool groups include: OTTO SEO, PPC, Content Genius, Site Explorer, Google Business Profile, local SEO, Link Laboratory, digital PR, LLM visibility, keyword research, and more.
Usage:
- Installation and login: It can be run without installation via npx, and the command will open a browser. After logging in, press F12 (Cmd+Option+I on Mac) to open developer tools, run localStorage.getItem("token") in the Console tab, and copy the result to paste into the terminal. The CLI will verify the token, save it, and print a configuration that can be pasted directly, with the path automatically detected.
- Add to an MCP client: Supports Claude Code, Cursor, Claude Desktop, VS Code, Windsurf, and Zed. On Windows, use npx.cmd instead of npx. The configuration location differs by client; for example, Cursor uses .cursor/mcp.json in the project root or the global ~/.cursor/mcp.json; Claude Desktop uses ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows; Windsurf uses ~/.codeium/windsurf/mcp_config.json; VS Code uses .vscode/mcp.json in the project; Zed uses settings.json. After saving, restart the client.
- Usage: Converse directly in natural language, and the AI will choose the appropriate tool. All commands can also be run via npx searchatlas-mcp-server <command>.
Token priority (the first match takes effect): SEARCHATLAS_TOKEN environment variable, SEARCHATLAS_API_KEY environment variable, ~/.searchatlasrc file (created by searchatlas login).
Native Streamable-HTTP client: If the MCP client directly supports Streamable HTTP, you can skip the npm package and connect to the remote server in one step: the URL is https://mcp.searchatlas.com/mcp/，传输方式为 Streamable HTTP (JSON-RPC + SSE), with the request header Authorization: Bearer <SEARCHATLAS_TOKEN>.
Use cases: Suitable for users who need to integrate SearchAtlas marketing tools into AI clients, especially scenarios using Claude Code, Cursor, Claude Desktop, VS Code, Windsurf, or Zed for SEO, content marketing, PPC management, keyword research, local SEO, link building, digital PR, and LLM brand visibility monitoring.
Limitations and notes: A SearchAtlas account is required. Node.js >= 18 is required. macOS GUI applications do not inherit the shell's PATH, so the full path to node must be used and pointed directly to the installed package to avoid spawn npx ENOENT and env: node: No such file errors; searchatlas login will automatically detect the path and print a copy-pasteable configuration. For troubleshooting, run searchatlas check, or use MCP Inspector for testing.
