The loop this is for
Audit → fix-prompt → your coding agent.
get_fix_prompt returns an instruction written for a coding agent, not a human checklist: what the finding means, how to fix it, and the severity and area it affects. Your assistant reads a finding from your audit, asks for its fix-prompt, and applies it to the repo it already has open — the audit and the code never leave your editor.
- 1
- 2
Connect the MCP server with your token (below).
- 3
Ask your assistant to pull a finding and its fix-prompt, and apply it.
Worth knowing
Audits are started in the dashboard — no MCP tool starts one. Over MCP you read the runs and their findings. A fix-prompt is guidance for your agent, per finding type; it is not a patch, and your agent still has to make and check the change.
What you get
41 tools your assistant can call.
Once connected, your AI coding CLI can ask UPGeoSEO for your sites, audits and fixes — and act on them. The list below is generated from the server itself, so it is what is actually registered today, not a summary someone wrote once.
Read — 27 tools
These only look. They return your own data and change nothing.
detect_localesShow the languages detected on one of your sites.
get_ai_visibilityThe site's AI-visibility report, query by query: per language and engine (Google AI Overviews, Google AI Mode, ChatGPT, Gemini, Perplexity), how often AI answers cite your site or mention your brand over the last 4 weeks (k of n) with a paired trend, plus every tracked query's latest result, cited URLs and history.
get_analyticsGoogle Analytics 4 report for one of your sites.
get_analytics_realtimeGA4 realtime active users, by country and page.
get_articleLook up one article by id: its title, language, status, whether it is the PRIMARY or a translation, slug, live URL, image refs, SEO score, and its whole translation group.
get_article_impactSEO + GEO impact deltas/trend for one article vs. its pre-publish baseline.
get_audit_findingsPAGINATED — returns at most `limit` findings (default 50, max 200) with `page.hasMore` and `page.nextOffset`; read `summary` for totals by severity and type, then page with `offset`.
get_bing_performanceBing Webmaster traffic, per-page stats, and crawl stats for one of your sites.
get_calendarPAGINATED — the content calendar for one of your sites: each slot's scheduled date, TARGET KEYWORD (with its volume/competition), locale, role, intent, and the article it produced.
get_content_planA site's content plan: without locale, where each language stands; with locale, that language page by page (the page's own keyword, its topics, what is already scheduled, what was left out and why).
get_fix_promptGet a ready-to-paste remediation prompt for a finding type.
get_geo_summaryLive GA4 rollup of AI-assistant referral traffic (ChatGPT, Perplexity, Gemini, Claude, Copilot, You.com).
get_impact_reportThe site's impact report: clicks/impressions/avg position for the last 28 days vs. the prior 28 days, counting ONLY the URLs of articles this account published (never a customer's pre-existing pages).
get_index_statusStored Google index verdicts for one of your sites' articles.
get_indexnow_setupShow the IndexNow verification file one of your sites must serve so Bing, Yandex, Seznam and Naver accept the URLs we submit on your behalf.
get_integration_schemasGet JSON Schema for everything UPGeoSEO emits to your own systems (Article, WebhookPublishPayload, RssItem, StructuredData, TranslationGroup) plus the MCP tool index and per-channel integration guides.
get_keyword_metricsThe STORED search metrics for one keyword on one of your sites (volume, competition, CPC, difficulty, market, source, measured-at).
get_keywordsPAGINATED — the keywords discovered for one of your sites, with volume, competition, difficulty, intent, source, and whether each is already scheduled on the calendar.
get_search_performanceGoogle Search Console performance for one of your sites (clicks, impressions, CTR, position).
get_site_speedThe last stored PageSpeed Insights check (mobile + desktop).
get_usageShow this month's action usage for one of your sites — what each limit counts, used/total, reset date.
list_auditsList recent audit runs for one of your sites.
list_rivalsThe rivals YOU named (up to 10) and how you compare over the last four weeks of AI answers.
list_sitesList every site this token can reach: a token acts as the person who created it, so these are the sites that person can open in the dashboard, across every account they belong to (a restricted teammate sees only the sites shared with them), each with its account, your role there, and its latest audit scores (foundation + AI-readiness).
list_tracked_questionsThe questions YOU asked us to track in AI answers (up to 10 per language), each with its latest result per engine: answered (with whether your brand was mentioned and your site linked) or no answer shown.
remove_rivalStop comparing with a rival.
remove_tracked_questionStop tracking one of your questions.
Write — 14 tools
These change something: they add a site, plan a calendar, publish or delete. Most are confirm-gated (below); all of them are limited to the sites you can open.
add_rivalName a rival to compare with in AI answers: a name (2 to 60 characters) and optionally its website, reduced to its domain (it may not be your own).
add_siteAdd a new site, by its URL, to the account this token was created in (owner or admin only): crawls it and builds its brand profile.
add_tracked_questionTrack one more question in AI answers for a language of the site.
connect_publishAdd a publish destination for a site: a WordPress site, a webhook, a Ghost site, a Webflow CMS collection, a Shopify store or a Wix site (the last two return an install link).
create_focusasks firstConcentrate the next days on a new feature (other articles of that language mention it) or a newly launched language, without adding articles.
delete_articleasks firstPermanently delete one article, or every non-primary translation of a group.
generate_calendarasks firstPlan a content calendar for one of your sites.
launch_localeasks firstRe-run market research for one of this site's already-enabled languages.
publish_articleasks firstPublish a DRAFT article to the site's connected destination.
publish_translationsasks firstCascade-publish a whole translation group: the primary plus every draft sibling.
recrawl_siteRe-learn one of your sites: re-read it and refresh its brand profile and brand colors.
refresh_locale_keywordsasks firstRefresh a non-primary language's keyword ideas: replace the ones not yet on your calendar with freshly researched ones.
reschedule_itemMove a PLANNED calendar item to a new publish date.
update_site_profileComplete or edit a site's onboarding / brand profile, switch Autopilot on or off (publishMode), and (admin-only) set its publishing schedule.
Before anything changes
Every action asks you first.
The tools that change your site or use part of your monthly allowance use a two-call flow. The first call changes nothing — it returns a preview of exactly what would happen, and a note that confirmation is required. Only a second call carrying confirm:true does the work. Your assistant shows you the preview in between, so an agent cannot quietly publish or use your allowance on your behalf.
What the first call returns
{
"confirm_required": true,
"message": "This will publish “How to split rent” to example.com's connected destination.
Call publish_article again with confirm:true to proceed."
}A handful of write tools are not confirm-gated because they are cheap and reversible — adding a site, re-crawling one, editing its profile, moving a calendar item. Nothing that publishes is in that group.
Get your token
Generate a token, once.
Every client below authenticates with the same thing: a personal token that acts as you. Here’s where to get it.
Sign in to your UPGeoSEO account (or create one — it’s free to start).
Open Dashboard → Your profile and find the API access (MCP) card.
Click Generate token. Copy it now — it starts with ugs_live_ and is shown only once.
Connect your client
Point your AI coding CLI at the server.
UPGeoSEO speaks standard MCP over Streamable HTTP with bearer auth, so it works with any client that supports a remote HTTP server and a custom header. Pick yours below and swap YOUR_TOKEN for the token you generated.
Claude Code (CLI)
One command adds it — run it from anywhere:
claude mcp add --transport http upgeoseo \
https://app.upgeoseo.com/api/mcp \
--header "Authorization: Bearer YOUR_TOKEN"Cursor
Add an entry to ~/.cursor/mcp.json (global) or .cursor/mcp.json in your project:
// ~/.cursor/mcp.json (or .cursor/mcp.json in your project)
{
"mcpServers": {
"upgeoseo": {
"url": "https://app.upgeoseo.com/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}Windsurf
Add it to Windsurf’s mcp_config.json with the same url + headers shape:
// Windsurf → mcp_config.json
{
"mcpServers": {
"upgeoseo": {
"url": "https://app.upgeoseo.com/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}Note: some Windsurf versions name the field serverUrl instead of url. If url doesn’t take, rename that one key — everything else stays the same.
Cline & other VS Code MCP extensions
Add a server to your .mcp.json (or the extension’s MCP settings), url + headers as usual:
// .mcp.json (or your MCP extension's settings)
{
"mcpServers": {
"upgeoseo": {
"url": "https://app.upgeoseo.com/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}Any other MCP client — the raw facts
If your client supports a remote HTTP MCP server with custom headers, it works. The only three things it needs:
- Transport: Streamable HTTP
- Endpoint:
https://app.upgeoseo.com/api/mcp - Auth: HTTP header
Authorization: Bearer <token>
Exact config-file paths and field names vary by client and by version. The constant is always the same: the URL above, plus the Authorization: Bearer header carrying your token.
Try it
Once it’s connected, just ask.
You don’t call the tools by name — you talk to your assistant, and it picks them. A few things to try:
“List my sites.”
“Show the open findings for example.com.”
“Get the fix prompt for h1_missing and apply it to this repo.”
Security
Scoped to you, confirm-gated, revocable.
Your access, and only yours
A token acts as you: it reaches every site you can already open in the dashboard, in your own account and in any account you belong to, with the role you hold on each. No tool accepts an account id as an argument, so a client holding your token cannot reach anyone else’s data — including by asking for it.
Writes are gated, not blocked
This is not a read-only integration: 14 of the 41 tools change something. What protects you is the confirm step, your plan’s monthly limits, and the fact that publishing goes through the same checks as the dashboard.
Revoke anytime
Delete a token from the same API access (MCP) card whenever you want. Once revoked, any client still holding it stops working immediately.
Shown once
We show a new token a single time, at generation. If you lose it, you don’t recover it — you generate a fresh one and swap it in.
