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.

DimensionAdobe Premiere Pro MCPGive AI full control over Adobe Premiere Pro.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS60 / 100 · C79 / 100 · B
Reliability11 / 2012 / 20
Security and permissions13 / 2018 / 20
Maintenance12 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience10 / 2015 / 20
Best for
  • Creative professionals and post-production teams seeking AI-driven video editing.
  • Developers who want to integrate Premiere Pro automation into AI workflows.
  • Users who want to automate repetitive editing tasks with AI assistance.
  • 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
  • Non-technical users? Some configuration is required, but Claude Desktop offers a one-click .mcpb install.
  • Large-scale production? Requires local installation and permission management.
  • Users needing real-time collaboration or cloud editing? This server is single-machine control, not multi-user.
  • 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
  • Read and write project files, media files, and XMP metadata.
  • Execute ExtendScript code (requires explicit authority).
  • Communicate with a local Adobe Premiere Pro instance.
  • Export files to the local filesystem.
  • 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
  • Any client that can reach the MCP server can fully control Premiere Pro.
  • execute_extendscript and evaluate_expression allow arbitrary code execution; enable with caution.
  • Filesystem operations may overwrite or delete files.
  • Remote deployment requires an auth token to prevent unauthorized access.
  • 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, Windsurf, Cursor, GitHub CopilotClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools1000