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.

DimensionMarkdownify MCP ServerConvert diverse files and web content to Markdown.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS50 / 100 · D75 / 100 · B
Reliability8 / 2010 / 20
Security and permissions11 / 2016 / 20
Maintenance7 / 2018 / 20
Documentation13 / 2017 / 20
Setup experience11 / 2014 / 20
Best for
  • Users who need to normalize multiple file types and web content into Markdown.
  • Users who want local MCP desktop-app integration for Markdown conversion.
  • Developers comfortable configuring Bun, Node.js, and Python dependencies.
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users seeking structured database or cloud-storage operations.
  • Users requiring verified compatibility with a specific MCP client.
  • Users running the slim Docker image who need audio transcription or image OCR.
  • 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
  • The server needs to read the file paths supplied to its file-input tools; MD_ALLOWED_PATHS can restrict readable directories.
  • When MD_ALLOWED_PATHS is unset, file access is unrestricted by that setting.
  • Tools handling web pages, YouTube, or Bing content need access to the relevant web content; the source does not state any additional authentication requirements.
  • 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
  • The default file-reading scope is unrestricted; set MD_ALLOWED_PATHS to narrow the readable boundary.
  • The published Docker image installs only markitdown[pdf], so audio transcription and image OCR tools fail in that slim image.
  • When using Docker, mount only required directories and pass container paths to the tools.
  • 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, Claude Code, Codex, Other MCP stdio clients
Tools1011