M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionBrandsystem MCPTurn existing brand guidelines into AI-usable portable brand runtime.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS62 / 100 · C79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions12 / 2018 / 20
Maintenance12 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • Design teams needing consistent brand identity in AI-driven content.
  • Developers who want to automate brand guideline extraction and token compilation.
  • Teams using Claude Code, Cursor, and similar tools.
  • Marketing professionals and content creators managing brand assets.
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
Not for
  • General AI tasks that don't need brand management.
  • Users who only want a hosted brand service (might be better with @brandcode/mcp).
  • Those relying on Figma direct integration without extra Figma MCP server.
  • Users without Node.js 20+ or who prefer not to run local servers.
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
Required permissions
  • Reads the websites you specify for extractions (network access).
  • Reads local filesystem and writes to the .brand directory (within your project dir).
  • Accesses authentication credentials when connecting hosted Brandcode Studio (stored in .brand/brandcode-auth.json).
  • Sends optional feedback to the brand team.
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
Risks and side effects
  • Network communication with remote sites, possible copyright/privacy concerns.
  • Extracted data is algorithmically inferred, may have inaccuracies, needs human review.
  • Figma extraction requires an additional Figma MCP, adding configuration complexity.
  • Default core profile only exposes 12 tools; full functionality requires opting into full profile.
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsClaude Desktop, Claude Code, Cursor, Windsurf, Cline, CodexClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools330