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.

DimensionPostHogOpen-source product analytics platform PostHog, steerable from Claude Code, Cursor, and other MCP-compatible agents.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS41 / 100 · D75 / 100 · B
Reliability4 / 2010 / 20
Security and permissions8 / 2016 / 20
Maintenance17 / 2018 / 20
Documentation7 / 2017 / 20
Setup experience5 / 2014 / 20
Best for
  • Teams already using PostHog for product analytics, feature flags, or experiments who want to control it from an AI agent
  • Developers who want product signals (errors, rage clicks, etc.) surfaced directly inside Claude Code, Cursor, or similar agent environments
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users who only need a narrow, single-purpose MCP tool (e.g., pure database or file-system access) — PostHog's surface area is broad
  • Users requiring a strictly FOSS codebase — the `ee` directory in this repo is under a separate, non-MIT license
  • Self-hosted deployments needing vendor support — the README explicitly states no customer support or guarantees are provided for open-source deployments
  • 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
  • Access to data within a PostHog project/account, including events, session recordings, feature flags, experiments, error tracking, surveys, and data warehouse records
  • Write access to modify project configuration if using the agent to create or change feature flags/experiments
  • 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
  • PostHog aggregates substantial user behavioral and product data; agent access to it carries exposure risk for sensitive information (user identifiers, session content)
  • Repository licensing is mixed (MIT for the main repo, separate proprietary license for the `ee` directory) — confirm which features are covered before relying on them in production
  • Self-hosted open-source deployments are explicitly unsupported by the vendor and are recommended only up to roughly 100k events/month before needing to migrate to Cloud
  • 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
Tools011