SearchAtlas logo

SearchAtlas

Connects MCP clients to SearchAtlas for SEO, PPC, content, keyword research, local SEO, and related marketing workflows.

Install SearchAtlas

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "searchatlas": {
      "command": "npx",
      "args": [
        "-y",
        "searchatlas-mcp-server"
      ],
      "env": {
        "SEARCHATLAS_TOKEN": "YOUR_VALUE_HERE",
        "SEARCHATLAS_API_KEY": "YOUR_VALUE_HERE",
        "SEARCHATLAS_API_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y searchatlas-mcp-server

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked .

Overview

SearchAtlas MCP server connects MCP-compatible clients to SearchAtlas v2, exposing a hosted catalogue of roughly 500+ tools for SEO, PPC, content, keyword research, local SEO, reporting, and related workflows. It runs locally as a Node.js stdio bridge to `https://mcp.searchatlas.com/mcp/`, while clients with native Streamable HTTP support can use the remote endpoint directly. Reach for it when an agent needs to inspect or manage SearchAtlas projects, campaigns, audits, content, rankings, or visibility data.

Use cases

  • Run technical SEO audits for websites
  • Research keywords and track rankings
  • Create and manage PPC campaigns
  • Generate content briefs and edit articles
  • Review local SEO and LLM visibility data

Key features

  • Hosted SearchAtlas v2 MCP access
  • Local stdio bridge for MCP clients
  • Dynamic discovery of approximately 500+ tools
  • SEO, PPC, content, and keyword workflows
  • Local SEO, backlink, PR, and visibility tools
  • CLI login and connectivity checks

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

22/23 checks healthy over the last 99d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · searchatlas-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2Stargazers on the source repository.
npm downloads386Package downloads in the last 30 days.
Last commit6mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity8 viewsConfig copies, upvotes, and views on AllMCPs.

How SearchAtlas works

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.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about SearchAtlas

Install the npm package globally or run `npx -y searchatlas-mcp-server`. Then authenticate with `searchatlas login` and add the generated client configuration.

Yes. The README provides a Claude Desktop configuration using the installed package and a `SEARCHATLAS_TOKEN` environment variable. Restart Claude Desktop after saving the configuration.

It accepts a SearchAtlas JWT in `SEARCHATLAS_TOKEN`, an alternative API key in `SEARCHATLAS_API_KEY`, or credentials saved by `searchatlas login` in `~/.searchatlasrc`.

Yes. Clients with native Streamable HTTP support can connect directly to `https://mcp.searchatlas.com/mcp/`; other clients can use the local stdio bridge.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSearchAtlas AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/searchatlas?style=directory)](https://allmcps.com/mcp/searchatlas)
HTML Embed
<a href="https://allmcps.com/mcp/searchatlas"><img src="https://allmcps.com/api/badge/searchatlas?style=directory" alt="SearchAtlas on AllMCPs" /></a>