AutomateLab-tech/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
In a Claude, Claude Code, or Cursor MCP config:
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:
1. **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.
2. **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.
3. **HTML extraction** - per-URL og:title, article:published_time, and JSON-LD datePublished are read live from the URL.
4. **XML sitemap** - set POSTS_SITEMAP_URL to your sitemap (or sitemap index) and the server enumerates posts from + .