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.

DimensionShadcn UI MCP ServerGive AI assistants direct access to shadcn/ui v4 components, blocks, and demosMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS66 / 100 · C79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions14 / 2018 / 20
Maintenance16 / 2016 / 20
Documentation15 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers using shadcn/ui
  • Teams wanting AI assistants to generate shadcn/ui-style component code
  • Developers needing consistent UI across frameworks (React, Svelte, Vue, React Native)
  • Building AI-powered development tools or integrations
  • 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 not using shadcn/ui
  • Users needing other UI libraries (e.g., Tailwind UI)
  • Offline environments (requires GitHub API access)
  • Scenarios requiring fully local operation without external API dependencies
  • 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
  • GitHub API access (to fetch component and repository data)
  • Network access (for GitHub API and npm package downloads)
  • Read environment variables (e.g., GITHUB_PERSONAL_ACCESS_TOKEN)
  • Local filesystem operations (e.g., for build caches)
  • 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
  • GitHub API rate limiting may cause service unavailability (60 requests/hour default, 5000/hour with token).
  • Supply chain risk from npm packages; verify package integrity.
  • SSE mode may expose the server on the network; configure CORS and access controls.
  • Component code may contain outdated or insecure patterns; review before use.
  • 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, VS Code, Cursor, ContinueClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools80