MCP Server

Connect your favorite AI app to SnowSEO and work with your SEO just by chatting. Instead of opening the dashboard, you can ask Claude, ChatGPT, or any AI assistant something like “how are my tracked keywords doing this month?” and get the answer straight from your SnowSEO account — and, for the actions you switch on, have it do the work too: “track these five keywords for me.”

What is the MCP server?

The Model Context Protocol (MCP) is an open standard that lets AI apps connect securely to outside services. The SnowSEO MCP server is how your AI app reaches your SnowSEO data — your keywords, rankings, topic clusters, Search Console stats, and more — so you can ask about them in normal conversation instead of switching between apps. By default the connection is read-only — the app can view your data and answer questions, nothing more. You can also switch on specific actions per brand (like tracking keywords or managing existing articles) so the assistant can do them for you. You decide exactly what’s allowed in Settings → Integrations → MCP, and every connected app follows those rules.

What you can do

Once connected, just ask your AI app to:

Check your rankings — see tracked keywords, what moved up or down, and trends over time
Research keywords — get keyword ideas with search volume, competition, and AI suggestions for your brand
Review topic clusters — see which clusters are gaining visibility and how they’re performing
Look at your traffic — Search Console clicks, impressions, CTR, GA4 visitors, and PostHog analytics
Review AI visibility — inspect tracked prompts, model visibility, competitors, citations, and filters
Check your content — article SEO scores, status, and recent team activity
Plan content — get article title ideas, target keywords, outlines, and FAQ prompts for any topic
Read your brand setup — audience, competitors, and brand profile
See your whole portfolio — an org-level rollup of every brand’s visibility, rankings, traffic, and open work
Review recommended next steps — the ranked to-do list of what to fix, with how-to detail for each item
Check your backlink outreach - prospects worth pitching, who you found at each site, what’s queued or sent, and who replied

…and take action for you

Switch these on per brand — they’re off by default — and the assistant can also:

Track & untrack keywords — start rank-tracking new keywords, or remove ones you no longer need
Track AI prompts — add, refresh, update, or remove prompts from AI-visibility tracking
Organize topics — create topic clusters and add keywords or prompts to them
Generate articles — write a complete SEO article from a brief, or run it step by step (titles → outline → draft); this uses credits, so the assistant asks first
Manage content — edit existing articles and schedule, publish, unpublish, or change public-feed visibility
Work your next steps — start, snooze, dismiss, reopen, or mark next steps done, and refresh the list
Run backlink outreach - search for prospects, look up who to pitch, resolve their addresses, draft a pitch, and queue or reply to real email; this spends credits and sends mail, so keep these off unless you want the assistant doing it

You turn each one on or off in Settings → Integrations → MCP — see Control what AI can do.

Connect your AI app

This is the easy way and works on any SnowSEO plan. You add SnowSEO as a “connector” inside your AI app, sign in through your browser once, and you’re done — there’s no key to copy or paste. The server URL is the same everywhere:

https://mcp.snowseo.com/mcp

AI apps occasionally rename these menus as they update, so the exact wording may differ slightly — but the flow is always the same: find where the app adds a custom connector (or MCP server), paste the URL above, and approve the SnowSEO sign-in.

Claude (Desktop & web)

Open Claude and go to Settings → Connectors.
Click Add custom connector (this needs a paid Claude plan — Pro, Max, Team, or Enterprise).
Give it a name like SnowSEO and paste the server URL: https://mcp.snowseo.com/mcp
Click Add, then Connect. Claude opens the SnowSEO sign-in page in your browser — sign in and click Allow.
SnowSEO now appears in your connectors. Start a chat and ask away.

ChatGPT

ChatGPT calls custom MCP connectors apps, and you add them through Developer mode (available on paid ChatGPT plans).

In ChatGPT, open Settings → Apps, then Advanced, and turn on Developer mode. This is what lets you add custom connectors.
Back on the Apps screen, click Create app.
In the New App dialog, give it a Name like SnowSEO. Under Connection, keep Server URL selected and paste https://mcp.snowseo.com/mcp.
Set Authentication to OAuth.
Tick “I understand and want to continue” on the risk notice, then click Create.
Sign in to SnowSEO and approve access. The app is now available — turn it on in a chat and ask about your SEO.

Other apps & assistants

Most MCP-capable apps follow the same pattern. Find where the app adds a custom connector or MCP server, paste https://mcp.snowseo.com/mcp, and approve the SnowSEO sign-in in your browser. No API key needed.

Which brand am I connecting?

Your connection is tied to your SnowSEO user session, not one fixed brand. The assistant should call list_teams first, let you choose the brand/team you mean, and pass that teamId to team-scoped tools. Tool permissions are still managed per brand in Settings → Integrations → MCP.

Example prompts

Once you’re connected, try asking:

What you want	Just ask
Check your rankings	”Using SnowSEO, how are my tracked keywords doing this month?”
Spot movers	”Which of my keywords dropped in ranking recently?”
Review clusters	”Summarize my topic clusters and which are gaining visibility.”
See your traffic	”Show my Search Console clicks and impressions for the last 28 days.”
Find new keywords	”Give me keyword ideas about remote team productivity.”
Check your content	”What are the SEO scores on my latest articles?”
Write an article	”Write an article titled ‘Best tools for remote teams’ in my Productivity cluster.”
Review link prospects	”Which backlink prospects have the best odds and nobody has been contacted yet?”
Check outreach replies	”Has anyone replied to my outreach this week?”

Some questions chain together automatically — ask about a topic cluster and a good assistant will list your clusters first, then dig into the one you mean.

Developer setup (CLI & editors)

Building with an AI coding tool? The same server works from the command line and code editors. These use the same browser sign-in (OAuth) on any plan.

Claude Code

claude mcp add --transport http snowseo https://mcp.snowseo.com/mcp

Then run /mcp, pick snowseo, and choose Authenticate to sign in. Add --scope user to use it in every project, or --scope project to share it with your team in a checked-in .mcp.json.

Cursor, VS Code, Windsurf & other editors

Open your client’s MCP config (usually a .mcp.json or mcp.json file) and add the server with no auth header:

{
  "mcpServers": {
    "snowseo": {
      "type": "http",
      "url": "https://mcp.snowseo.com/mcp"
    }
  }
}

On first connect the client opens the SnowSEO sign-in page in your browser. Approve it once and you’re connected.

Field names differ a little between clients (Windsurf uses serverUrl instead of url; VS Code’s top-level key is servers). The flow is the same — point it at the URL with no auth header and let the client handle sign-in.

Client only supports stdio? Use the mcp-remote bridge

Some clients can only launch local commands. Bridge to the remote server with mcp-remote (needs Node.js) — it handles the browser sign-in for you:

{
  "mcpServers": {
    "snowseo": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.snowseo.com/mcp"]
    }
  }
}

What the assistant can access

These are the tools the app uses behind the scenes. Call list_teams first to choose a brand, then pass the returned teamId to team-scoped tools. Read tools are on by default (you can switch any off per brand); actions stay off until you switch them on per brand. Read (on by default):

Tool	What it returns
`list_teams`	Teams this user can access and their team IDs
`brands_overview`	Org-level portfolio read: per-brand AI visibility, domain rating, open next steps, tracked prompts/keywords, Search/Traffic, plus org KPIs
`list_integrations`	Sanitized integrations grouped by dashboard section for a team
`keyword_research`	Keyword ideas with search volume, competition, and CPC
`suggest_keywords`	AI keyword suggestions from a website + brand context
`rank_tracking_keywords`	All tracked keywords with current position and trend
`rank_tracking_top_keywords`	Best-performing tracked keywords, with period comparison
`rank_tracking_keyword_changes`	Keywords that improved, dropped, newly ranked, or were lost
`rank_tracking_keyword_history`	Position history for a specific keyword over time
`topic_clusters_list`	All topic clusters with counts, visibility, and trend
`topic_cluster_detail`	One cluster’s keyword/prompt performance and competitors
`gsc_traffic_stats`	Search Console clicks, impressions, CTR, and position
`gsc_top_pages`	Search Console top pages
`gsc_search_queries`	Search Console top queries
`gsc_page_changes`	Search Console page performance changes
`gsc_countries`	Search Console country breakdown
`gsc_devices`	Search Console device breakdown
`gsc_pages_for_keyword`	Search Console pages ranking for one keyword
`bing_traffic_stats`	Bing Webmaster Tools clicks, impressions, CTR, and position
`bing_top_pages`	Bing Webmaster Tools top pages
`bing_search_queries`	Bing Webmaster Tools top queries
`bing_backlinks`	Bing Webmaster Tools backlink summaries
`ga_overview`	GA4 users, pageviews, and sessions by day with comparison
`ga_traffic_overview`	GA4 total users, pageviews, and sessions with comparison
`ga_pages`	GA4 page performance
`ga_sources`	GA4 source and referral-source breakdowns
`ga_channels`	GA4 traffic channels
`ga_countries`	GA4 country breakdown
`ga_devices`	GA4 device-category breakdown
`ga_browsers`	GA4 browser breakdown
`ga_operating_systems`	GA4 operating-system breakdown
`ga_campaigns`	GA4 campaign performance
`ga_engagement`	GA4 engagement metrics
`ga_user_type`	GA4 new vs returning user split
`ga_filter_values`	GA4 analytics filter values
`posthog_overview`	PostHog users, pageviews, and sessions by day
`posthog_page_counts`	PostHog page-level visitor counts
`posthog_pages`	PostHog page performance
`posthog_sources`	PostHog source and referral-source breakdowns
`posthog_channels`	PostHog traffic channels
`posthog_countries`	PostHog country breakdown
`posthog_devices`	PostHog device-category breakdown
`posthog_browsers`	PostHog browser breakdown
`posthog_operating_systems`	PostHog operating-system breakdown
`posthog_campaigns`	PostHog campaign performance
`posthog_avg_duration`	PostHog average session duration
`posthog_user_type`	PostHog new vs returning user split
`posthog_filter_values`	PostHog analytics filter values
`ai_visibility_summary`	Headline AI visibility, share of voice, citation share, and sentiment
`ai_visibility_overview`	Brand leaderboard, visibility and share-of-voice trends, competitor comparison
`ai_visibility_trends`	Visibility and sentiment over time by AI platform, plus the competitor radar
`ai_visibility_brands`	Every brand seen in AI answers, ranked by mentions
`ai_visibility_competitors`	Per-competitor visibility, mentions, citations, and sentiment
`ai_visibility_citations`	Sources AI answers cite: domains, type splits, per-platform counts
`ai_visibility_citation_source`	Every AI answer that cited one domain or URL
`ai_visibility_platforms`	Per-AI-platform mentions, visibility, position, citations, sentiment
`ai_visibility_sentiment`	Quoted evidence behind the brand’s AI sentiment score
`ai_visibility_prompts`	Tracked prompts with per-prompt visibility and run status
`ai_visibility_prompt_detail`	One tracked prompt: every AI answer, brands named, sources cited
`ai_visibility_brand`	AI visibility summary for one brand or competitor
`ai_visibility_filters`	AI visibility platforms, countries, competitors, and prompt filters
`ai_visibility_models`	Available AI visibility models and active state
`cms_articles`	Articles with status, SEO scores, and metadata
`get_article`	Full article detail by slug
`generate_titles`	SEO-friendly article title ideas for a topic cluster
`generate_keywords`	Ranked target keywords for an article title (optionally from competitor pages)
`generate_prompts`	FAQ-style reader questions to guide an article’s structure
`find_competitor_sources`	Competitor articles on a topic, found by web search, to inform planning
`generate_outline`	Structured, type-specific article outline from a title and keywords
`generate_internal_links`	Most relevant existing articles to link to from a new article
`generation_status`	Whether an article is currently generating and how far along it is
`article_internal_links`	Outbound internal links for one article
`team_internal_links`	All stored internal links for a team
`article_audit`	Latest cached article audit
`article_audit_history`	Cached article audit history
`activity_feed`	Recent team activity across the platform
`brand_settings`	Brand profile, audience, competitors, and colors
`next_steps`	Recommended next steps for a team, ranked by priority (or resolved wins)
`next_steps_detail`	How to fix one next step: fix steps, best practices, impact, and AI prompts
`outreach_prospects`	Sites worth pitching for a backlink, with their target page, odds and pipeline stage
`outreach_prospect_pages`	Pages on one prospect’s site that mention your brand or a competitor
`outreach_pages`	Every discovered page across all prospects
`outreach_prospect_people`	People found at one prospect’s site, with their role
`outreach_people`	Every contact found across all prospects
`outreach_prospect_emails`	Contact addresses for one prospect, with verification status
`outreach_people_search_terms`	Job titles to pick from before searching a site for people
`outreach_templates`	Reusable pitch subjects and bodies
`outreach_drafts`	Unsent pitches saved for each prospect
`outreach_queued`	Pitches waiting to be sent
`outreach_scheduled`	Queued pitches with their recipient, subject, and when each was queued
`outreach_inbox_threads`	Pitch conversations and their messages
`outreach_messages`	Individual outreach messages sent and received
`outreach_send_status`	Connected mailboxes, daily limits, and how much is already used
`outreach_sending_accounts`	Mailboxes outreach can send from (never returns passwords)
`outreach_automation_settings`	Whether earned links are re-checked automatically, and how often

Actions (off until you switch them on in Settings → Integrations → MCP):

Tool	What it does
`track_keywords`	Start rank-tracking one or more keywords
`untrack_keywords`	Remove one or more keywords from rank tracking
`track_prompts`	Add one or more prompts to AI-visibility tracking
`refresh_tracked_prompt`	Refresh one tracked prompt and its region variants
`update_tracked_prompts`	Update prompt text, enabled, branded, or pinned state
`delete_tracked_prompts`	Delete one or more tracked prompts
`delete_prompt_responses`	Delete selected responses from a tracked prompt
`ai_visibility_fan_out_queries`	Generate AI visibility query variations
`update_ai_visibility_model`	Enable or disable one AI visibility model
`create_topic_cluster`	Create a new topic cluster
`add_keywords_to_topic`	Attach a keyword to a topic cluster (optionally tracking it)
`add_prompts_to_topic`	Attach or create prompts on a topic cluster
`generate_article`	Write a complete SEO article from a brief in one step (outline + draft). Uses credits
`create_article`	Create a draft article from an outline produced by `generate_outline` (no content generated)
`start_article_generation`	Write the content for an existing draft article. Uses credits
`update_article`	Edit an existing article draft
`set_article_public_feed`	Show or hide an article on the public feed
`schedule_article`	Schedule an existing article to publish to a connected CMS
`unschedule_article`	Remove pending scheduled publishing from existing articles
`publish_article`	Publish existing articles to connected CMS providers
`unpublish_article`	Unpublish articles from connected CMS providers
`delete_article`	Delete an existing SnowSEO article
`next_steps_start`	Move a recommended next step into the in-progress state
`next_steps_mark_done`	Mark a recommended next step as done
`next_steps_reopen`	Return a next step to the open to-do list
`next_steps_dismiss`	Dismiss a next step so it leaves the list
`next_steps_snooze`	Hide a next step for a number of days
`next_steps_refresh`	Recompute a team’s next steps from the latest data
`outreach_discover`	Search for pages mentioning your brand and turn them into prospects. Uses credits
`outreach_add_prospects`	Add one site or a batch by domain, or by the URL of the page to pitch
`outreach_block_prospects`	Remove prospects and stop their sites returning from future searches
`outreach_set_prospect_stage`	Mark a prospect Contacted or Negotiating, or clear the override
`outreach_find_people`	Look up who to pitch at one site or a batch. Uses credits per site
`outreach_enrich_people`	Resolve the email addresses of people already found. Uses credits per person
`outreach_recheck_prospects`	Re-crawl a prospect’s pages to see whether the link went live. Uses page crawls
`outreach_draft_email`	Write a pitch for one prospect. Sends nothing. Uses credits
`outreach_save_draft`	Save unsent writing for one prospect. Sends nothing
`outreach_delete_draft`	Discard the saved draft for one prospect
`outreach_queue_emails`	Queues real email to real people. Cannot be undone once sent
`outreach_draft_reply`	Write a reply in an existing conversation. Sends nothing. Uses credits
`outreach_reply`	Sends a real reply in an existing conversation. Cannot be undone
`outreach_create_template`	Save a reusable pitch subject and body
`outreach_update_template`	Rename or edit a pitch template
`outreach_update_automation`	Turn automatic link re-checking on or off and set its cadence

outreach_queue_emails and outreach_reply send real email from your mailbox and cannot be undone. They are off until you switch them on, like every other action, and a good assistant will show you the wording before queueing anything - but treat them as the two switches worth thinking hardest about. Anything still queued can be pulled back from the dashboard; anything sent cannot.Connecting a mailbox is deliberately not an MCP tool: it takes mailbox passwords, which is not something an assistant should handle for you. Connect mailboxes in Settings → Integrations → Sending Accounts.

Not every endpoint in the API reference is available as an MCP tool. Long-running or background operations are left out because an assistant won’t wait on a single call - for example, a full SEO Audit runs as a crawl job that can take minutes, so it stays in the dashboard and REST API only. The tools above are the complete set an AI app can use.

Tools are documented here at the conceptual level — there is currently no per-tool parameter reference. Each tool maps to a /v3 endpoint, so consult the matching API reference page for exact inputs. Authentication is OAuth 2.1 only today; there is no API-key path for the MCP server.

Technical details

Property	Value
Endpoint	`https://mcp.snowseo.com/mcp`
Transport	Streamable HTTP (`POST`)
Auth	OAuth 2.1 (any plan) — browser sign-in, no key to copy
Brand context	User-scoped OAuth; team-scoped tools use `teamId` from `list_teams`
Access	Read by default; optional write actions you enable per brand

The server is a thin, stateless proxy over the Developer API: every tool call maps to a /v3 endpoint, and nothing is stored — your credentials are forwarded per request and team-scoped calls carry the selected teamId.

Control what AI can do

You’re always in charge of what a connected app can do. In the dashboard, open Settings → Integrations → MCP to see every tool grouped into Reading your data and Taking actions, each with an on/off switch.

Reads are on by default — viewing your SEO data is safe.
Actions are off by default — switch on only the ones you want the assistant to perform for you.
Rules are per brand, and every app connected to that brand (Claude, ChatGPT, Cursor…) follows them — flip a switch and it applies everywhere on the next request.
Only admins and owners can change these; other teammates can view them.

Turning a tool off blocks it at the moment it’s called: the assistant may still list it, but the request is refused and it’s told the tool is switched off for this brand. There is no delay: the check runs on every request, so a switch you flip now applies to the very next one.

Use the same settings for every brand

By default each brand keeps its own rules, so a brand you add later starts from the defaults again (reads on, actions off) rather than inheriting what you set elsewhere. If you’d rather manage one list, turn on Use the same settings for all brands. While it’s on:

Every brand follows the shared list, and editing it from any brand changes them all.
Brands you add later start with it too, with nothing to copy over.
Turning it back off is safe: each brand gets its own saved settings back, exactly as they were before you switched sync on.

Switching it on replaces what your other brands currently use with the settings of the brand you enable it from, so the dashboard asks you to confirm first. The toggle only appears once your organization has more than one brand, and like the rules themselves it’s admins and owners only.

Permission API

The same allow/deny matrix is available over the REST API. The dashboard settings screen is a thin client over these routes, and the API enforces the resulting state per brand on every request. GET /v3/settings/mcp Team-scoped (teamId), any member. Returns the full tool catalog with, for each tool, its name, label, description, group (read or write), default state, and effective state for the brand, plus canManage (whether the caller may edit), syncEnabled (whether the organization shares one list) and brandId. PATCH /v3/settings/mcp Team-scoped, team admins/owners only (members can read the matrix but not change it). Body: permissions, a map of tool name → "allow" | "deny" (deltas only; values matching a tool’s default are cleared). Reads default to allow and writes default to deny. Returns the updated catalog in the same shape as the GET route. When syncEnabled is true this writes to the organization’s shared list, so the change applies to every brand, and the request shape is identical either way. PATCH /v3/settings/mcp/sync Team-scoped, team admins/owners only. Body: enabled (boolean). Turning it on copies the calling brand’s current settings to the organization’s shared list, which every brand then follows; turning it off returns each brand to its own saved settings, which are never overwritten while sync is on. Returns syncEnabled and the resulting catalog.

Troubleshooting

Do I need a paid plan?

No — connecting an AI app works on any SnowSEO plan. You just add the connector and approve access in your browser.

I can't find where to add a connector in my app.

The menu differs per app: in Claude it’s Settings → Connectors → Add custom connector; in ChatGPT it’s Settings → Apps → Advanced → Developer mode, then Create app. Most apps only allow custom connectors on paid plans.

It used the wrong brand.

Ask the assistant to call list_teams and use the teamId for the brand you mean. You do not need to reconnect just to switch brands.

The assistant can't do something (like tracking a keyword).

That action is probably switched off for this brand. Open Settings → Integrations → MCP, turn it on under Taking actions, and ask again — new actions are off by default. (Some actions also use credits or need a specific plan.)

A brand I just added can't do what my other brands can.

New brands start from the defaults (reads on, actions off) rather than copying an existing brand. Either switch its actions on under Settings → Integrations → MCP, or turn on Use the same settings for all brands so every brand, including ones you add later, follows a single shared list.

Changing one brand changed all of them.

Use the same settings for all brands is switched on, so there’s one shared list and editing it from any brand applies everywhere. Turn it off to go back to per-brand rules, and each brand keeps the settings it had before sync was enabled.

The app shows empty data for a keyword.

Make sure it’s a keyword you actually track (ask for rank_tracking_keywords to see them), and that the brand has Google Search Console connected. Untracked keywords have no history to show.

The connection won't authenticate.

Re-run the sign-in step and approve access in the browser window. Make sure your client uses the streamable-http transport and that it didn’t cache an expired session — removing and re-adding the connector forces a fresh sign-in.

Overview

Website Analysis

Keywords & Research

Topic Clusters

Traffic & Analytics

AI Visibility

Rank Tracking

Article Generation

Content

Content Utilities

Backlink Outreach

Reports

Dashboard

Settings

What is the MCP server?

What you can do

…and take action for you

Connect your AI app

Claude (Desktop & web)

ChatGPT

Other apps & assistants

Which brand am I connecting?

Example prompts

Developer setup (CLI & editors)

Claude Code

Cursor, VS Code, Windsurf & other editors

What the assistant can access

Technical details

Control what AI can do

Use the same settings for every brand

Permission API

Troubleshooting

​What is the MCP server?

​What you can do

​…and take action for you

​Connect your AI app

​Claude (Desktop & web)

​ChatGPT

​Other apps & assistants

​Which brand am I connecting?

​Example prompts

​Developer setup (CLI & editors)

​Claude Code

​Cursor, VS Code, Windsurf & other editors

​What the assistant can access

​Technical details

​Control what AI can do

​Use the same settings for every brand

​Permission API

​Troubleshooting

What is the MCP server?

What you can do

…and take action for you

Connect your AI app

Claude (Desktop & web)

ChatGPT

Other apps & assistants

Which brand am I connecting?

Example prompts

Developer setup (CLI & editors)

Claude Code

Cursor, VS Code, Windsurf & other editors

What the assistant can access

Technical details

Control what AI can do

Use the same settings for every brand

Permission API

Troubleshooting