Brandsystem MCP vs Seo MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Brandsystem MCP vs Seo MCP
In-depth architectural comparison of the Brandsystem MCP and Seo MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Brandsystem MCP
Marketing · Local stdio
Quality: 64/100 (Good) | Auth: No auth required
Seo MCP
Marketing · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Brandsystem MCP if you need specialized Marketing tools running via a local process. Choose Seo MCP if your workspace requires Marketing integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Brandsystem MCP when:
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Make your brand machine-readable. Extract brand identity (colors, fonts, logo, voice, visual rules) from any website via static CSS + rendered-page extraction, compile into DTCG tokens, brand runtime contracts, and interaction policies. 34 tools across 4 progressive sessions. Subscribable brand://runtime and brand://policy MCP resources. Content compliance scoring (0-100), pass/fail gate, and HTML/CSS preflight. Brandcode Studio connector for hosted brand sync.
Six tools for SEO and AI-readability audits. 91 checks, 11 score modules.
Category & Scope
Tools & Capabilities Breakdown
Brandsystem MCP Tools (34)
brand_start
Begin here.** Creates a brand system from a website URL in under 60 seconds. Use `mode='auto'` for one-call setup with rendered and deep-site fallback on weak JS-rendered sites.
brand_status
Check progress, get next steps, or see a getting-started guide if no brand exists yet.
brand_extract_web
Extract logo (SVG/PNG), colors, and fonts from any website URL.
brand_extract_visual
Screenshot the rendered page in headless Chrome and extract computed colors, fonts, and visual context from JS-heavy sites.
brand_extract_site
Discover representative pages, render them across desktop and mobile, capture screenshots, sample multiple components, and persist `extraction-evidence.json`.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Brandsystem MCP is categorized under Marketing and uses a local stdio subprocess. In contrast, Seo MCP belongs to Marketing using local stdio subprocess. Select Brandsystem MCP when you need capabilities focused on marketing and Seo MCP when you require tools for marketing.
Generate `design-synthesis.json` and `DESIGN.md` from extracted evidence or the current brand state.
brand_extract_figma
Extract from Figma design files (higher accuracy). Two-phase: plan then ingest.
brand_set_logo
Add/replace logo via SVG markup, URL, or data URI.
brand_compile
Generate DTCG design tokens, brand runtime contract, and interaction policy from extracted data.
brand_clarify
Resolve ambiguous brand values interactively (color roles, font confirmations).
brand_audit
Validate .brand/ directory for completeness and correctness.
brand_report
Generate portable HTML brand report. Upload to any AI chat as instant guidelines.
+22 more tools listed on main page
Seo MCP Tools (6)
run_audit_anonymous
Run 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_audit
Queue 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_audit
Fetch 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_audits
List 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_pdf
Return 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_traffic
If 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.