# SearchAtlas [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://github.com/Search-Atlas-Group/searchatlas-mcp-server  
**GitHub Stars:** 2  
**npm Downloads (last month):** 317  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/searchatlas

## Description
SEO, content generation, PPC, keyword research, site auditing, authority building, and LLM

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "searchatlas": {
    "command": "npx",
    "args": ["-y","searchatlas-mcp-server"],
    "env": {
      "SEARCHATLAS_TOKEN": "",
      "SEARCHATLAS_API_KEY": "",
      "SEARCHATLAS_API_URL": ""
    }
  }
}
```

**Requires environment variables:** `SEARCHATLAS_TOKEN`, `SEARCHATLAS_API_KEY`, `SEARCHATLAS_API_URL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What the SearchAtlas MCP server does

SearchAtlas MCP server gives compatible AI clients access to the SearchAtlas v2 MCP service. The available catalogue contains more than 500 tools spanning SEO automation, PPC, content operations, site analysis, local SEO, link building, digital PR, LLM visibility, keyword rank tracking, reporting, and other SearchAtlas product areas.

Representative capabilities include running technical SEO workflows, listing and managing projects, checking backlinks, generating content briefs, querying keyword performance, managing Google Business Profile data, inspecting LLM visibility reports, creating social posts, and submitting URLs for indexing. The exact tool set is supplied by the hosted service and can change without requiring a package update.

## How it works

The SearchAtlas MCP server is a thin stdio bridge. A client starts the package locally through Node.js, and the bridge communicates with the hosted v2 MCP endpoint at `https://mcp.searchatlas.com/mcp/`. This allows clients that only support stdio to use the remote SearchAtlas tools. Clients with native Streamable HTTP support can connect to the endpoint directly instead.

Tools are discovered dynamically during the MCP connection. The README lists roughly 587 currently available tools and provides `searchatlas check` as a way to inspect the live count and verify the connection.

## Setup and configuration

Install the npm package globally, or invoke it through `npx`, then run `searchatlas login`. The login flow opens a browser and asks you to provide the token shown in the browser's developer-console storage. The CLI validates the credential, saves it locally, and prints client configuration examples with detected paths.

Authentication is selected in this order:

1. `SEARCHATLAS_TOKEN`
2. `SEARCHATLAS_API_KEY`
3. The `~/.searchatlasrc` file created by `searchatlas login`

`SEARCHATLAS_API_URL` can override the default hosted MCP endpoint. After configuring a client, run `searchatlas check` to validate the credential, configuration, and MCP handshake. Node.js 18 or newer is listed as a requirement.

## Tools and capabilities

Tool groups documented by the project include:

- `otto_*` for OTTO SEO automation
- `ppc_*` for Google Ads and PPC operations
- `cg_*` for Content Genius
- `se_*` for Site Explorer
- `gbp_*` for Google Business Profile
- `local_seo_*` for local SEO heatmaps
- `ll_*` for Link Laboratory
- `dpr_*` for Digital PR
- `llmv_*` for LLM Visibility
- `krt_*` for keyword rank tracking
- `gsc_*` for Google Search Console
- `social_hub_*` for social publishing
- `rb_*` for report retrieval and details

The SearchAtlas MCP server is suitable for conversational requests such as finding long-tail keywords, identifying site issues, creating content briefs, listing projects, or running available playbooks. Whether a particular operation is available depends on the live tool catalogue and the connected SearchAtlas account.

## Limitations and notes

This package does not provide a standalone local implementation of the SearchAtlas tools; it forwards MCP traffic to the hosted v2 service. A valid SearchAtlas token or API key is needed for authenticated use. GUI clients may require absolute paths to Node.js and the installed package because they may not inherit the shell's `PATH`. The project specifically documents configurations for Claude Code, Cursor, Claude Desktop, Windsurf, VS Code, and Zed, while native Streamable HTTP clients can bypass the local bridge.

The SearchAtlas MCP server's tool count and available operations are live rather than fixed in the npm package. Run the health check or list tools from the client to see the current catalogue.

_Full upstream README: https://allmcps.com/mcp/searchatlas/readme_