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.

DimensionStorybook MCP AddonMCP addon that runs inside your Storybook dev server so AI agents can write and test UI component stories.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS55 / 100 · C79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions12 / 2018 / 20
Maintenance13 / 2016 / 20
Documentation11 / 2018 / 20
Setup experience11 / 2015 / 20
Best for
  • Frontend teams already using Storybook who want AI agents to help draft or test component stories
  • Developers using Claude Code or Codex who want ready-made Storybook integration
  • 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
  • Projects that don't use Storybook
  • Teams needing a hosted/remote MCP server rather than one tied to a local dev server
  • 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
  • Runs a local HTTP server bound to the Storybook dev server's port (default 6006)
  • Reads component files and existing stories in your project
  • 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
  • The README explicitly states the project is experimental; APIs and architecture may change without notice
  • No authentication is described for the local HTTP endpoint in the source material, so exposing the dev server port beyond localhost could let other local processes reach it
  • 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 Code, Codex, VS CodeClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools20