SEO Performance MCP

Name: SEO Performance MCP
Author: AutomateLab-tech

by AutomateLab-techversion 1.0.1i★ –iRuns on your computer

Registry nameio.github.AutomateLab-tech/seo-performance-mcp

Install

Overview

Description from the maker (original English)

Per-URL SEO verdicts from GSC, GA4, Matomo, Clarity, AI citations: refresh/expand/merge/kill.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Marketing & social media
You need to fill in: GSC_SERVICE_ACCOUNT_JSON, MATOMO_TOKEN, GA4_SERVICE_ACCOUNT_JSON, CLARITY_API_TOKEN, GHOST_ADMIN_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: GSC_SERVICE_ACCOUNT_JSON, GSC_SITE_URL, MATOMO_URL, MATOMO_TOKEN, MATOMO_SITE_ID, GA4_PROPERTY_ID, GA4_SERVICE_ACCOUNT_JSON, CLARITY_PROJECT_ID, CLARITY_API_TOKEN, POSTS_SITEMAP_URL, POSTS_LIST, GHOST_ADMIN_API_URL, GHOST_ADMIN_API_KEY, CITATION_INTELLIGENCE_URL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "seo-performance": {
      "command": "npx",
      "args": [
        "-y",
        "@automatelab/seo-performance-mcp"
      ],
      "env": {
        "GSC_SERVICE_ACCOUNT_JSON": "your-value",
        "GSC_SITE_URL": "your-value",
        "MATOMO_URL": "your-value",
        "MATOMO_TOKEN": "your-value",
        "MATOMO_SITE_ID": "your-value",
        "GA4_PROPERTY_ID": "your-value",
        "GA4_SERVICE_ACCOUNT_JSON": "your-value",
        "CLARITY_PROJECT_ID": "your-value",
        "CLARITY_API_TOKEN": "your-value",
        "POSTS_SITEMAP_URL": "your-value",
        "POSTS_LIST": "your-value",
        "GHOST_ADMIN_API_URL": "your-value",
        "GHOST_ADMIN_API_KEY": "your-value",
        "CITATION_INTELLIGENCE_URL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add seo-performance --env GSC_SERVICE_ACCOUNT_JSON=your-value --env GSC_SITE_URL=your-value --env MATOMO_URL=your-value --env MATOMO_TOKEN=your-value --env MATOMO_SITE_ID=your-value --env GA4_PROPERTY_ID=your-value --env GA4_SERVICE_ACCOUNT_JSON=your-value --env CLARITY_PROJECT_ID=your-value --env CLARITY_API_TOKEN=your-value --env POSTS_SITEMAP_URL=your-value --env POSTS_LIST=your-value --env GHOST_ADMIN_API_URL=your-value --env GHOST_ADMIN_API_KEY=your-value --env CITATION_INTELLIGENCE_URL=your-value -- npx -y @automatelab/seo-performance-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "seo-performance": {
      "command": "npx",
      "args": [
        "-y",
        "@automatelab/seo-performance-mcp"
      ],
      "env": {
        "GSC_SERVICE_ACCOUNT_JSON": "your-value",
        "GSC_SITE_URL": "your-value",
        "MATOMO_URL": "your-value",
        "MATOMO_TOKEN": "your-value",
        "MATOMO_SITE_ID": "your-value",
        "GA4_PROPERTY_ID": "your-value",
        "GA4_SERVICE_ACCOUNT_JSON": "your-value",
        "CLARITY_PROJECT_ID": "your-value",
        "CLARITY_API_TOKEN": "your-value",
        "POSTS_SITEMAP_URL": "your-value",
        "POSTS_LIST": "your-value",
        "GHOST_ADMIN_API_URL": "your-value",
        "GHOST_ADMIN_API_KEY": "your-value",
        "CITATION_INTELLIGENCE_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "seo-performance": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@automatelab/seo-performance-mcp"
      ],
      "env": {
        "GSC_SERVICE_ACCOUNT_JSON": "your-value",
        "GSC_SITE_URL": "your-value",
        "MATOMO_URL": "your-value",
        "MATOMO_TOKEN": "your-value",
        "MATOMO_SITE_ID": "your-value",
        "GA4_PROPERTY_ID": "your-value",
        "GA4_SERVICE_ACCOUNT_JSON": "your-value",
        "CLARITY_PROJECT_ID": "your-value",
        "CLARITY_API_TOKEN": "your-value",
        "POSTS_SITEMAP_URL": "your-value",
        "POSTS_LIST": "your-value",
        "GHOST_ADMIN_API_URL": "your-value",
        "GHOST_ADMIN_API_KEY": "your-value",
        "CITATION_INTELLIGENCE_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

GSC_SERVICE_ACCOUNT_JSON secret env
Base64-encoded Google service account JSON with Search Console read access.
GSC_SITE_URL env
Search Console site URL (e.g. sc-domain:example.com or https://example.com/).
MATOMO_URL env
Matomo instance URL (e.g. https://example.com/analytics).
MATOMO_TOKEN secret env
Matomo auth token with view access.
MATOMO_SITE_ID env
Matomo idSite for the site to query.
GA4_PROPERTY_ID env
GA4 property ID (numeric, no G- prefix).
GA4_SERVICE_ACCOUNT_JSON secret env
Base64-encoded Google service account JSON with GA4 Data API access.
CLARITY_PROJECT_ID env
Microsoft Clarity project ID.
CLARITY_API_TOKEN secret env
Microsoft Clarity Data Export API token.
POSTS_SITEMAP_URL env
XML sitemap URL used to enumerate posts. Primary platform-agnostic discovery path.
POSTS_LIST env
Optional JSON array overriding sitemap discovery.
GHOST_ADMIN_API_URL env
Optional. Ghost Admin API base URL. Pair with GHOST_ADMIN_API_KEY for richer metadata.
GHOST_ADMIN_API_KEY secret env
Optional. Ghost Admin API key in the form id:secret.
CITATION_INTELLIGENCE_URL env
Optional URL of a citation-intelligence MCP server to delegate AI-citation queries to.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account AutomateLab-tech, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Marketing & social mediai

More stars than 0% of the other 2985 servers in this category
Published to the registry more recently than 75% of the other 2985 servers in this category
Basic checks equal to or better than 100% of the other 2985 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is SEO Performance MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: GSC_SERVICE_ACCOUNT_JSON, MATOMO_TOKEN, GA4_SERVICE_ACCOUNT_JSON, CLARITY_API_TOKEN, GHOST_ADMIN_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 11 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

MCP YouTube Transcript

by jkawamoto

An MCP server retrieving transcripts of YouTube videos

Runs on your computer★ 495MITUpdated 10 days ago

Install

Google Analytics MCP

by surendranb

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

Runs on your computer★ 244MITUpdated 10 days ago

Install

BibiGPT YouTube Video Summarizer

by JimmyLv

AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.

Runs in the cloud★ 137MITUpdated 10 days ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

seo-performance-mcp

Know which blog posts to refresh, expand, merge, or kill - without guessing.

A MCP server that turns your scattered SEO and analytics data into one clear verdict per URL. Plug it into Claude, Cursor, or any MCP-aware client and ask: "Which three posts should I update this week?" - and get an answer backed by hard numbers.

What it does

seo-performance-mcp unifies post-publish signals from every channel you already pay for:

Google Search Console - clicks, impressions, CTR, position, top queries
Matomo or GA4 - visits, dwell time, bounce rate
Microsoft Clarity - scroll depth, rage clicks, dead clicks
AI citation tracking - which LLMs cite your URL today vs. last month
Sitemap / CMS - publish dates, tags, word counts (any platform via XML sitemap; optional Ghost integration for richer metadata)

It then runs a deterministic rule engine over those signals and emits a verdict per URL:

refresh / expand / merge / kill / double_down / hold

with reason codes, evidence, and a 0-1 confidence score. Reporting only - the server never mutates your posts.

Why it matters

Most content teams have analytics in five tabs and a gut feeling. That's how good posts rot quietly, mediocre posts get over-promoted, and the obvious "rewrite this one" is invisible until traffic has already cratered.

This MCP closes the loop:

One question, one URL in, one verdict out.
Same logic across the whole cohort, so the ranking is comparable.
All decisions traceable to numeric thresholds you can pin in src/verdict/rules.ts.
AI clients (Claude, Cursor, MCP hosts) can drive the entire content audit in plain English.

Who it's for

Content marketers running a blog of 50+ posts and tired of guessing what to refresh.
SEO consultants doing audits who want a portable, deterministic scoring layer instead of bespoke spreadsheets.
AI-first content teams wiring up rewrite agents - this MCP is the upstream signal layer.
Indie publishers on Ghost, WordPress, Hugo, Astro, Next, Webflow, or any CMS that exposes a sitemap.

What you get

After one cohort run you have:

A ranked table of every post with a verdict and confidence score.
A markdown brief per "refresh" URL: numbers + top queries + suggested actions an editor (or a writing agent) can act on immediately.
A list of "quick wins": queries sitting at positions 5-15 with below-expected CTR - the fastest title-rewrite wins on the property.
A historical AI-citation diff: which LLMs cited you and stopped.

Install

npx -y @automatelab/seo-performance-mcp

In a Claude, Claude Code, or Cursor MCP config:

"mcpServers": { "seo-performance": { "command": "npx", "args": ["-y", "@automatelab/seo-performance-mcp"], "env": { "POSTS_SITEMAP_URL": "https://example.com/sitemap.xml", "GSC_SERVICE_ACCOUNT_JSON": " ", "GSC_SITE_URL": "sc-domain:example.com", "MATOMO_URL": "https://example.com/analytics", "MATOMO_TOKEN": "...", "MATOMO_SITE_ID": "1", "GA4_PROPERTY_ID": "123456789", "GA4_SERVICE_ACCOUNT_JSON": " ", "CLARITY_PROJECT_ID": "...", "CLARITY_API_TOKEN": "...", "CITATION_INTELLIGENCE_URL": "https://citation.example.com" } } } }

Every env var is optional. Adapters that lack their env config skip their slice of the snapshot; the server still boots. The verdict engine works on whatever slices are present.

Platform integration

Point it at any site, no CMS plugin required. The post-discovery layer resolves in priority order:

`POSTS_LIST` - JSON array of {url, title?, published_at?, tags?, word_count?}. Use this when you already have a content index and want exact control.
Ghost Admin API - if both GHOST_ADMIN_API_URL and GHOST_ADMIN_API_KEY are set, Ghost is used as a richer metadata source. Optional.
HTML extraction - per-URL og:title, article:published_time, and JSON-LD datePublished are read live from the URL.
XML sitemap - set POSTS_SITEMAP_URL to your sitemap (or sitemap index) and the server enumerates posts from + .

Most users only need POSTS_SITEMAP_URL. WordPress, Hugo, Astro, Next.js, Webflow, Framer, Wix, Squarespace, Notion-as-a-site, Substack-mirror sites all expose a sitemap by default.

To add a brand-new platform: nothing to build - just point POSTS_SITEMAP_URL at it.

Tools exposed

Tool	What it returns
`posts_list`	Posts with `{url, title, age_days, tags}` from sitemap, Ghost, or your `POSTS_LIST`.
`posts_snapshot`	Per-URL unified rollup for a 30/60/90-day window: GSC + Matomo + GA4 + Clarity + citations + meta.
`posts_decay_curve`	Weekly GSC clicks/impressions/position buckets + a `decay/plateau/growth` trend label.
`posts_verdict`	Verdict (`refresh/expand/merge/kill/double_down/hold`) + reason codes + 0-1 confidence.
`posts_refresh_brief`	Markdown brief for a human or downstream LLM editor: numbers, top queries, suggested actions.
`cohort_report`	Cohort verdict table sorted by priority + confidence. "Which three posts should I refresh this week?"
`posts_cite_loss`	LLM citations that dropped off for a given URL. Needs `CITATION_INTELLIGENCE_URL`.
`gsc_quick_wins`	`(page, query)` pairs at positions 5-15 with low CTR - fastest title-rewrite wins.

Use as a GitHub Action

Run any of the tools on a cron from CI and post the output to a GitHub Issue, Discussion, or PR. The action is published on the GitHub Marketplace.

- uses: AutomateLab-tech/seo-performance-mcp@v1

with: tool: cohort_report format: markdown input: '{"window": 90, "min_age_days": 90, "limit": 20}' gsc-service-account-json: ${{ secrets.GSC_SERVICE_ACCOUNT_JSON }} gsc-site-url: ${{ secrets.GSC_SITE_URL }} posts-sitemap-url: ${{ secrets.POSTS_SITEMAP_URL }}

Outputs:

Output	Description
`result`	Tool output as a multi-line string (markdown or JSON, per `format`).
`result-file`	Path of the file the tool output was written to. Hand to `peter-evans/create-issue-from-file` etc.
`rows`	For `cohort_report` with `format: json` only: number of rows returned.

A complete weekly-audit workflow that opens a GitHub Issue with the cohort report is in examples/weekly-cohort-report.yml.

Use as a one-shot CLI

The package also ships a seo-perf-cli bin so you can run a single tool without an MCP client:

npx -p @automatelab/seo-performance-mcp seo-perf-cli cohort_report \

--input '{"window": 90, "limit": 20}' \ --format markdown

Same env vars as the MCP server. --format markdown is supported for cohort_report and posts_refresh_brief; other tools fall back to fenced JSON.

Companion skills + Cursor rule

Three thin routing files ship in the repo so the LLM in your client knows *when* to reach for these tools:

skills/seo-performance/SKILL.md - tool-routing skill. Drop into ~/.claude/skills/seo-performance/ (or .claude/skills/ per project) to auto-load in Claude Code. Routes a single question to the right tool.
skills/weekly-audit/SKILL.md - one-shot weekly audit playbook. Composes gsc_quick_wins + cohort_report + posts_cite_loss into a deduped, cross-signal ranked digest with proposed edits per URL. Drop in alongside the routing skill.
cursor/rules/seo-performance.mdc - copy to .cursor/rules/seo-performance.mdc in any Cursor workspace.

All optional. The MCP server works without them; they just shorten the "which tool do I call" round-trip.

MCP prompts

The server exposes three prompts that bundle the playbook. Any MCP client (Claude Desktop, Claude Code, Cursor, Continue) can list and invoke them:

Prompt	What it runs
`audit_cohort`	`cohort_report` on posts >=90d, then `posts_refresh_brief` per refresh/expand/merge row. The weekly audit.
`find_quick_wins`	`gsc_quick_wins` (positions 5-15) + per-URL `posts_snapshot`, then proposes verbatim-query meta_title rewrites.
`citation_loss_sweep`	`posts_cite_loss` per URL, refresh_brief for any with losses, targeted H1/lead phrasing recommendations.

Verdict engine

Deterministic, rule-based, traceable. Reason codes:

ctr_below_position_expected
position_drift
decay_30d_over_30pct / decay_60d_over_50pct
stagnant_no_clicks
thin_content_low_dwell
rising_impressions_low_ctr / rising_clicks_continue_investment
citation_loss / citation_growth
duplicate_or_cannibalizing
high_bounce_low_scroll
fresh_post_too_young

The mapping (reasons → verdict) and every threshold lives in src/verdict/rules.ts. Edit it, pin it in tests, ship your own rule book.

Development

npm install

npm run dev # tsx src/index.ts npm run build # tsc npm test # vitest

License

MIT

Maintenance and verification

See the maintenance guide for interpretation limits, current tool names where applicable, and reproducible verification.

SEO Performance MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Marketing & social mediai

Common questions

Alternatives

MCP YouTube Transcript

Google Analytics MCP

BibiGPT YouTube Video Summarizer

README from the maker

seo-performance-mcp

What it does

Why it matters

Who it's for

What you get

Install

Platform integration

Tools exposed

Use as a GitHub Action

Use as a one-shot CLI

Companion skills + Cursor rule

MCP prompts

Verdict engine

Development

License

Maintenance and verification