← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionMeiGen AI Design MCPOpen-source image and video generation MCP server for major AI coding toolsBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS55 / 100 · C75 / 100 · B
Reliability8 / 2010 / 20
Security and permissions11 / 2016 / 20
Maintenance9 / 2018 / 20
Documentation14 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Users creating images or videos inside AI coding tools
  • Design workflows that benefit from curated prompts and prompt enhancement
  • Users with a local GPU or an image-generation API backend
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users who only need text or conventional coding capabilities
  • Users who do not want prompts or reference images sent to third-party cloud APIs unless using local ComfyUI
  • Users without a configured generation backend or API credentials who need image or video generation
  • 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
  • Run npx and access the npm package
  • Provide an API key or token for MeiGen Cloud or an OpenAI-compatible API
  • Access the configured ComfyUI service when using local generation
  • Send prompts and, where applicable, reference images to the configured service; local reference images may be uploaded
  • Write configuration and generated results to local configuration, image, and video directories
  • 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
  • Cloud backends receive prompts and reference images, with privacy handling determined by the provider
  • Reference images are uploaded to Cloudflare R2 and expire automatically after 24 hours
  • Image and video generation may incur service costs or be limited by model, resolution, and quality capabilities
  • Local files may be compressed and uploaded when using non-ComfyUI backends
  • Video generation can take several minutes and may fail if client timeouts are too short
  • 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 Code, Cursor, Codex, Windsurf, Roo Code, OpenClaw, Hermes AgentClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools811