# SearchAtlas [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://github.com/Search-Atlas-Group/searchatlas-mcp-server  
**GitHub Stars:** 2  
**npm Downloads (last month):** 443  
**Views:** 8  
**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 SearchAtlas MCP server does

SearchAtlas MCP server gives an MCP-compatible AI client access to SearchAtlas v2 capabilities through a local package or the hosted MCP endpoint. The available catalogue covers SEO automation, paid search, content operations, site analysis, local search, link building, digital PR, LLM visibility, rank tracking, reporting, and other SearchAtlas product areas.

The server is intended for tasks such as reviewing technical SEO problems, auditing a site, researching keywords, generating content briefs, checking backlinks, managing PPC campaigns, inspecting Google Business Profile data, and querying project or report information. It can also expose actions for creating or updating supported SearchAtlas resources, depending on the tool group and the account permissions.

## How it works

The npm package is a thin stdio bridge. It forwards MCP requests to the hosted v2 endpoint at `https://mcp.searchatlas.com/mcp/`, allowing clients that only support local stdio processes to use the remote service. Clients with native Streamable HTTP support can connect to the endpoint without the bridge.

Tools are discovered dynamically from the hosted service. The client therefore receives the live tool catalogue rather than a fixed list bundled into the package. The README reports approximately 587 tools at the time of writing, with new hosted tools becoming available without a package update.

## Setup and configuration

The package requires Node.js 18 or newer. Install it globally with npm, yarn, or pnpm, or invoke it through `npx`. Run `searchatlas login` to authenticate in a browser, retrieve the token from the browser's local storage as instructed, and save the credential. The login command also prints client configuration with detected local paths. `searchatlas check` validates the saved credential and tests MCP connectivity.

Authentication values are read in this order: `SEARCHATLAS_TOKEN`, `SEARCHATLAS_API_KEY`, then `~/.searchatlasrc`. `SEARCHATLAS_API_URL` can replace the default hosted endpoint. The token or API key must be supplied through the environment or the login-created configuration file.

For local client configurations, the package can be run with `npx -y searchatlas-mcp-server`. GUI clients may need an absolute Node.js path and a direct path to the installed package because they do not always inherit the shell's `PATH`.

## Tools and capabilities

SearchAtlas MCP server groups tools by product prefix, including:

- `otto_*` for OTTO SEO automation and site projects.
- `ppc_*` for Google Ads and PPC accounts, campaigns, and performance.
- `cg_*` for Content Genius articles, briefs, and content editing.
- `se_*` for Site Explorer details and backlink overviews.
- `gbp_*` and `local_seo_*` for Google Business Profile and local SEO data.
- `ll_*`, `dpr_*`, and `llmv_*` for link orders, digital PR, and LLM visibility.
- `krt_*`, `gsc_*`, and `rb_*` for rank tracking, Search Console data, and reports.
- `social_hub_*`, `cs_*`, `kg_*`, `dkn_*`, `indexer_*`, and `pr_*` for social, content strategy, knowledge, indexing, and press-release workflows.

Tool names and counts can change because discovery comes from the hosted service. Ask the connected client to list tools or run `searchatlas check` to inspect the current catalogue.

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

