AgentPixel vs Seo MCP
A side-by-side look at the AgentPixel and Seo MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
AgentPixelMarketing · Remote HTTP/SSEConsent-first website pixel for AI agents. Your agent sets up a consent bar, installs the tag, verifies it and reads contacts. Hosted remote MCP server at https://agentpixel.io/mcp?src=allmcps (Streamable HTTP). try_sample works with no account or key.53GoodAuth: oauth 2.0Verdict: choose AgentPixel for marketing work over a hosted endpoint; choose Seo MCP for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
AChoose AgentPixel when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Choose Seo MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MCP_API_KEY, PORT, APP_API_BASE_URL, APP_PUBLIC_BASE_URL, MCP_INTERNAL_TOKEN. - You want tools like
run_audit_anonymous, run_audit, get_audit.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A AgentPixel | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 53/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | None listed | MCP_API_KEYPORTAPP_API_BASE_URLAPP_PUBLIC_BASE_URLMCP_INTERNAL_TOKEN |
| Verified owner |
Tools & capabilities
AgentPixel tools
No tool names declared yet. Check the project README from the listing page.
Seo MCP tools 6
run_audit_anonymousRun a one-shot SEO + AI-readability audit on any public URL. Returns scores across 11 modules and ~90 checks, plus actionable findings with rule docs. Limited to 1 audit per IP per 24 hours — for higher volume, get an API key at https://app.metricspot.com/settings/api-keys and use `run_audit`. Synchronous: blocks until the audit completes. Does NOT include Core Web Vitals (use `run_audit` for full PSI scoring). No auth required.run_auditQueue a full SEO + AI-readability audit (includes Core Web Vitals from Google PSI and organic traffic if Google is linked). Returns the audit envelope immediately with `status: queued` and an `audit_id`. Poll `get_audit` with the returned `audit_id` until `status` becomes `complete` (typical 10-30s). Counts against the user's plan allowance. Requires an API key as a Bearer token. Quota and per-domain cooldowns mirror the dashboard.get_auditFetch a previously-run audit by id. Returns module scores (0-100), total score, all findings with severity, recommendation text, and links to the HTML report. Use this to poll a queued `run_audit` until `status: complete`. Requires an API key.list_auditsList the user's audits (most recent first, deduplicated by URL). Returns `audit_id`, `url`, `status`, `total_score`, `created_at`. Default limit 24, max 100. Use the returned `audit_id` with `get_audit` for full findings. Requires an API key.get_audit_pdfReturn a signed download URL for the branded PDF report for a given audit id. If no PDF has been rendered yet, queues a render and returns `status: queued` — poll the same tool again, or fetch the URL directly once ready. Requires an API key.get_organic_trafficIf the user has linked GA4 + Google Search Console, return the 28-day organic traffic snapshot for an audit: session count, daily trend, top landing pages, top queries, and indexing health. Returns `connected: false` if Google is not linked. Cached 24h server-side. Requires an API key.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
AgentPixel
{
"mcpServers": {
"agentpixel": {
"url": "https://agentpixel.io/mcp?src=allmcps"
}
}
}
Seo MCP
{
"mcpServers": {
"seo-mcp": {
"command": "npx",
"args": [
"-y",
"@metricspot/mcp-server"
],
"env": {
"MCP_API_KEY": "YOUR_MCP_API_KEY_HERE",
"PORT": "YOUR_PORT_HERE",
"APP_API_BASE_URL": "YOUR_APP_API_BASE_URL_HERE",
"APP_PUBLIC_BASE_URL": "YOUR_APP_PUBLIC_BASE_URL_HERE",
"MCP_INTERNAL_TOKEN": "YOUR_MCP_INTERNAL_TOKEN_HERE"
}
}
}
}
Frequently asked questions
AgentPixel is categorized under Marketing and uses a remote HTTP/SSE transport. Seo MCP belongs to Marketing and uses a local stdio subprocess. Pick AgentPixel for marketing work and Seo MCP for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
AgentPixel is listed as a paid service. Auth: oauth 2.0. Seo MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add agentpixel and seo-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AgentPixel has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Seo MCP has 55/100 (Good) with 2 views, 2 installs and 0 GitHub stars.
