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.

DimensionAfter Effects MCP ServerMCP server for Adobe After Effects enabling remote control via the Model Context Protocol.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS48 / 100 · D75 / 100 · B
Reliability8 / 2010 / 20
Security and permissions12 / 2016 / 20
Maintenance10 / 2018 / 20
Documentation10 / 2017 / 20
Setup experience8 / 2014 / 20
Best for
  • Users who want to integrate AI into their video editing workflow
  • Creators who want to automate After Effects operations without deep programming
  • Users of MCP-compatible clients like Claude Desktop
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users without After Effects 2022 or later
  • Not suitable for those who want to run in the cloud or without local After Effects
  • Not for users needing real-time video preview or complex timeline operations
  • Users needing to write to upstream databases (read-only)
  • Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
  • Users expecting all advanced features without API keys
Required permissions
  • Requires access to the local file system to read configuration files
  • Requires communication with After Effects to execute commands
  • Requires internet access to query public biomedical APIs
  • Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
  • Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
Risks and side effects
  • Requires running After Effects and Node.js locally, which may consume significant system resources
  • Commands may fail if the bridge panel is not open in After Effects
  • Executing scripts within After Effects carries security risks; avoid untrusted scripts
  • Upstream API rate limits may affect performance
  • Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
  • Features requiring API keys (e.g., OncoKB) may be incomplete without them
  • Local binary installations need regular updates for compatibility
Supported clientsClaude Desktop, CursorClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools1411