Audiense Insights vs SEO Performance MCP
Audiense Insights is an MCP server published by AudienseCo. Marketplaces we read that list it: 1 (Docker MCP Catalog). SEO Performance MCP is an MCP server published by AutomateLab-tech. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Audiense Insights |  SEO Performance MCP |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:064623a07a6b Forks (GitHub): 11 Pulls (Docker Hub): 41 214 Stars (Docker Hub): 0 Stars (GitHub): 19 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Downloads/month (npm): 319 Downloads/week (npm): 55 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Audiense Insights | SEO Performance MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 19 (better) | 3 (worse) |
| Pulls (Docker Hub) (differs) | 41 214 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/audiense-insights) | On your machine (@automatelab/seo-performance-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 8 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 2 | 14, secrets among them: 5 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/audienseco/mcp-audiense-insights | github.com/automatelab-tech/seo-performance-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Audiense Insights
Audiense Insights MCP Server is a server based on the Model Context Protocol (MCP) that allows Claude and other MCP-compatible clients to interact with your Audiense Insights account.
SEO Performance MCP
Per-URL SEO verdicts from GSC, GA4, Matomo, Clarity, AI citations: refresh/expand/merge/kill.
How to run each
Audiense Insights As a local MCP server: Docker image
claude mcp add --env "AUDIENSE_CLIENT_SECRET=<YOUR_AUDIENSE_CLIENT_SECRET>" --env "TWITTER_BEARER_TOKEN=<YOUR_TWITTER_BEARER_TOKEN>" --transport stdio audiense-insights -- docker run -i --rm -e AUDIENSE_CLIENT_SECRET -e TWITTER_BEARER_TOKEN mcp/audiense-insightsRequires: AUDIENSE_CLIENT_SECRET (secret), TWITTER_BEARER_TOKEN (secret)
SEO Performance MCP As a local MCP server: npm package
claude mcp add --env "CLARITY_API_TOKEN=<YOUR_CLARITY_API_TOKEN>" --env "GA4_SERVICE_ACCOUNT_JSON=<YOUR_GA4_SERVICE_ACCOUNT_JSON>" --env "GHOST_ADMIN_API_KEY=<YOUR_GHOST_ADMIN_API_KEY>" --env "GSC_SERVICE_ACCOUNT_JSON=<YOUR_GSC_SERVICE_ACCOUNT_JSON>" --env "MATOMO_TOKEN=<YOUR_MATOMO_TOKEN>" --transport stdio seo-performance-mcp -- npx -y @automatelab/seo-performance-mcpRequires: CLARITY_API_TOKEN (secret), GA4_SERVICE_ACCOUNT_JSON (secret), GHOST_ADMIN_API_KEY (secret), GSC_SERVICE_ACCOUNT_JSON (secret), MATOMO_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of SEO Performance MCP publish no list of tools, so we do not compare tools.
Settings each asks for
Only Audiense Insights asks for
AUDIENSE_CLIENT_IDAUDIENSE_CLIENT_SECRET (secret)TWITTER_BEARER_TOKEN (secret)
Only SEO Performance MCP asks for
CITATION_INTELLIGENCE_URLCLARITY_API_TOKEN (secret)CLARITY_PROJECT_IDGA4_PROPERTY_IDGA4_SERVICE_ACCOUNT_JSON (secret)GHOST_ADMIN_API_KEY (secret)GHOST_ADMIN_API_URLGSC_SERVICE_ACCOUNT_JSON (secret)GSC_SITE_URLMATOMO_SITE_IDMATOMO_TOKEN (secret)MATOMO_URL
Show the remaining 2
POSTS_LISTPOSTS_SITEMAP_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Audiense Insights · What it can do: SEO Performance MCP · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.