In-depth architectural comparison of the AI Seo MCP and Brandsystem MCP — Build 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
AI Seo MCP
Marketing · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Brandsystem MCP — Build
Marketing · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Verdict Summary: Choose AI Seo MCP if you need specialized Marketing tools running via a local process. Choose Brandsystem MCP — Build 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 AI Seo 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).
Primary tools included: Eight-dimension AI-SEO page scoring, Schema, canonical, robots, sitemap, and llms.txt audits, AI crawler access checks.
Schema, canonical, robots, sitemap, and llms.txt audits
AI crawler access checks
AEO and GEO content rewrites
Citation-worthiness and entity analysis
Optional Chromium rendering for SPAs
Brandsystem MCP — Build 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.
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).
AI Seo MCP is categorized under Marketing and uses a local stdio subprocess. In contrast, Brandsystem MCP — Build belongs to Marketing using local stdio subprocess. Select AI Seo MCP when you need capabilities focused on marketing and Brandsystem MCP — Build when you require tools for marketing.
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`.
brand_generate_designmd
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.
AI-SEO / AEO / GEO audit MCP for any public URL. Scores schema.org coverage, robots.txt and llms.txt health, canonical and OpenGraph setup, and AI-citation likelihood; suggests rewrites tuned for Answer Engine and Generative Engine surfaces. No vendor keys, no crawls of private data. Install: npx -y @automatelab/ai-seo-mcp.
Build portable .brand runtimes from websites, Figma, and PDFs for use across AI tools.