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.

DimensionGhost MCP ServerAn MCP server for managing Ghost CMS through LLM interfacesBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS53 / 100 · D75 / 100 · B
Reliability11 / 2010 / 20
Security and permissions9 / 2016 / 20
Maintenance10 / 2018 / 20
Documentation11 / 2017 / 20
Setup experience12 / 2014 / 20
Best for
  • Content operators using Ghost CMS who want to manage a blog through an LLM interface.
  • Developers or administrators who need to manage Ghost entities from MCP clients such as Claude Desktop.
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users who do not use Ghost CMS.
  • Users who cannot provide a Ghost Admin API key or access to a Ghost site.
  • 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 a Ghost Admin API key (GHOST_ADMIN_API_KEY) to access the Ghost Admin API.
  • Requires a Ghost site URL (GHOST_API_URL) and optionally an API version (GHOST_API_VERSION).
  • 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 server can create, edit, and delete entities such as posts, members, and newsletters, so mistakes may cause content or member data loss.
  • An Admin API key grants administrative access to the Ghost site; exposure or misuse may lead to unauthorized access.
  • The key is supplied as a plaintext environment variable in the client configuration, so the local config file must be protected.
  • 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 DesktopClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools4211