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.

DimensionDembrandtExtract any website's design system into design tokens in seconds: logo, colors, typography, borders & more. One command.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS66 / 100 · C79 / 100 · B
Reliability7 / 2012 / 20
Security and permissions13 / 2018 / 20
Maintenance14 / 2016 / 20
Documentation18 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • Frontend developers needing to rapidly analyze a website's design system and extract reusable tokens.
  • Design system teams needing to document existing sites or track design changes across versions.
  • AI agents using MCP that need to automatically fetch website design information for development or auditing.
  • 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
  • Users needing full interactive analysis (e.g., hover effects) since only some interaction states are extracted from CSS.
  • Canvas/WebGL-rendered websites because they have no DOM to read.
  • Unauthorized automated access that violates a website's terms of service; ensure permission.
  • 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
  • Network access: Requires internet to access target websites.
  • Local file system: Write permissions for saving output files (JSON, PDF, DESIGN.md).
  • Browser execution: Uses Playwright to drive a browser; may need system privileges.
  • 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
  • Target websites may prohibit automated access, risking IP bans or legal issues.
  • Extracted tokens may contain copyrighted design elements; do not reproduce third-party brand assets without permission.
  • Browser automation can be resource-intensive; in CI or restricted environments, configuration like --no-sandbox may be needed.
  • 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, Cursor, WindsurfClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools120