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.

DimensionMedusa MCP ServerMCP server for the Medusa JS SDKMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS43 / 100 · D79 / 100 · B
Reliability6 / 2012 / 20
Security and permissions7 / 2018 / 20
Maintenance10 / 2016 / 20
Documentation10 / 2018 / 20
Setup experience10 / 2015 / 20
Best for
  • Developers building e-commerce on Medusa JS who want AI-agent automation
  • Teams integrating a Medusa backend with LLM toolchains
  • Engineers comfortable customizing OpenAPI definitions for fine-grained tool control
  • 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 not using Medusa
  • Users seeking official Medusa support or hosted solutions
  • Non-technical users unable to deploy a Node.js service and manage credential environment variables
  • 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 to a Medusa backend URL
  • A Medusa publishable API key (PUBLISHABLE_KEY)
  • Medusa admin username and password for admin operations
  • 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
  • Admin credentials stored as environment variables carry leak risk
  • AI agents can trigger real commerce operations (order fulfillment, pricing updates); mistakes may affect production data
  • Server defaults to localhost:3000; exposing it to a network requires your own security measures
  • No tool list is documented, so actual capabilities must be verified by reviewing the source
  • 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, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools00