MCP for AI agents

Growth context for
your coding agent.

GrowthAtlas MCP lets Cursor, Claude Code, and similar agents use your joined GrowthAtlas data — pages, competitors, content pipeline, Pulse, and Search Console / Analytics metrics from connections you already made in the dashboard. Agents diagnose issues and apply HTML, CSS, JS, and technical fixes in your website repo. GrowthAtlas never SSHs into your site.

Get Started Sign in & connect MCP →

How GrowthAtlas MCP works

Data in GrowthAtlas. Code changes in your IDE. Optional writes stay inside GrowthAtlas.

Step 1

Connect your agent

In Cursor, Claude Code, or Codex: add the GrowthAtlas MCP URL and log in with OAuth (or paste a token from Settings → MCP as a fallback). Full access is selected by default; you can narrow scopes on the consent screen.

Step 2

Agent reads context

Tools return agent-shaped summaries: site pages, GSC/GA performance from your existing Google connections, competitors, drafts, and Pulse status.

Step 3

Diagnose & plan

Structured findings separate repo fixes from GrowthAtlas content, settings, or Pulse monitors — so the agent knows where to act.

Step 4

Fix in the right place

CSS, JS, HTML, and technical SEO land in your repo. Ideas, drafts, SEO Autopilot, and monitors can be created in GrowthAtlas when you grant write abilities.

One-click setup

Paste this into your agent

Drop the prompt below into Cursor, Claude Code, or Codex. The agent should add the GrowthAtlas MCP, open login, and finish OAuth. No manual token required.

Copy-paste prompt 
Add the GrowthAtlas remote MCP server and connect my account with OAuth (full access).

MCP URL: https://mcp.growthatlas.io/mcp

Steps:
1. Add this as a remote / HTTP MCP server (not stdio).
2. Prefer OAuth / "Log in to GrowthAtlas" — do not ask me to paste a gat_ token unless OAuth is unavailable.
3. When the browser opens, I will sign in and approve the connection.
4. After it connects, call whoami and list_projects to confirm access.
5. For project-scoped tools, always pass project_id from list_projects.

Docs: https://growthatlas.io/mcp

What agents can access (V1)

Read tools use GrowthAtlas data you already synced. GSC and GA metrics require the same Google Search Console and Analytics connections you set up in the app — MCP does not run a separate OAuth flow.

Context

Project overview, pages, entities, and joined site structure for the active project.

Performance

Search Console and Analytics snapshots already stored in GrowthAtlas — not raw Google API credentials.

Diagnose

Ranked findings with fix surfaces: your repo, GrowthAtlas content, settings, or Pulse.

Content (optional write)

Create ideas, briefs, and drafts in the content pipeline, and update the brand profile, when the token allows.

SEO Autopilot (optional write)

Create or adjust SEO Autopilot campaigns on your schedule.

Pulse (optional write)

Read monitor status and create or update uptime and DNS monitors.

GEO / AI Visibility (optional write)

Results from your GEO prompt panel on Perplexity Sonar and OpenAI web search: mention and citation rates, runs, cited domains, and GA4 AI referral traffic. With write access, create, enable, import, delete, and Run now prompts.

Social Hub (Instagram publishing and social intelligence) is not part of MCP V1. Connector CMS publish and inbound social ingest are out of scope too.

Works with MCP clients

Cursor, Claude, Codex — same server

GrowthAtlas speaks standard remote MCP over HTTPS. Any client that supports remote MCP can use https://mcp.growthatlas.io/mcp.

Preferred: OAuth “log in to GrowthAtlas” (Cursor and other OAuth-capable clients). Full access is checked by default on the consent screen. Fallback: mint a gat_ token in Settings → MCP and pass it as a Bearer header — useful for Claude Code, Codex, or any client that prefers static tokens.

OAuth (recommended)

  1. Add remote MCP URL: https://mcp.growthatlas.io/mcp
  2. Choose Log in / OAuth when the client offers it
  3. Approve GrowthAtlas in the browser (full access selected by default)

Bearer token fallback

{
    "mcpServers": {
        "growthatlas": {
            "url": "https://mcp.growthatlas.io/mcp",
            "headers": {
                "Authorization": "Bearer gat_YOUR_TOKEN_HERE"
            }
        }
    }
}

Security & scopes

  • ✓ Tokens are account-scoped, hashed at rest, and shown once when created.
  • ✓ Abilities: read, write content, write SEO Autopilot, write Pulse, publish to site, trigger scans — full access is selected by default; you can narrow scopes anytime.
  • ✓ Every tool call requires a project_id; tokens can be locked to one project.
  • ✓ MCP tokens are separate from Connector API keys and inbound social tokens.
  • ✓ Protocol traffic is served at mcp.growthatlas.io; this page lives on the marketing site.

Where work happens

Your agent uses GrowthAtlas as the source of truth for growth data and recommendations. Implementation work — templates, styles, scripts, structured data in code — belongs in the repository you already have open in the IDE.

Need site publish? See Connector API →

Connect your agent to GrowthAtlas

Create a project, connect GSC and GA in the dashboard, then add https://mcp.growthatlas.io/mcp in Cursor, Claude Code, or Codex and log in.

Start Free →