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.

DimensionScreenpipeSearch local screen recordings, audio transcripts, and computer activity.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS50 / 100 · D75 / 100 · B
Reliability5 / 2010 / 20
Security and permissions8 / 2016 / 20
Maintenance11 / 2018 / 20
Documentation14 / 2017 / 20
Setup experience12 / 2014 / 20
Best for
  • Knowledge workers who need to retrieve personal screen and audio history.
  • Users who prioritize local processing and privacy.
  • Developers who want to provide work context to Claude, Cursor, or other MCP clients.
  • Remote workers who need meeting transcription and activity review.
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users who do not want continuous screen or audio capture.
  • Teams that require centralized cloud storage without local recording.
  • Use cases requiring only ordinary file-system or database access.
  • 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
  • Screenpipe needs applicable screen-recording permissions to capture screen content.
  • System-audio and microphone capture require the relevant system audio or microphone permissions.
  • The application uses the accessibility tree to extract screen text and falls back to OCR when unavailable.
  • On macOS, system-audio capture requires Screen & System Audio Recording permission and the relevant experimental feature to be enabled.
  • 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
  • Screens, audio, transcripts, and search indexes may contain passwords, private conversations, or proprietary information.
  • Data is stored locally by default, but enabled analytics and crash diagnostics may send device or error metadata.
  • Cloud transcription, hosted AI, or cloud sync can remotely process related audio, prompts, context, or synchronized data.
  • Continuous capture consumes system resources; the README reports typical CPU usage of 5–10%.
  • 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, Cursor, VS Code, Cline, ContinueClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools011