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.

DimensionOpenTwitter MCP ServerTwitter/X Data · User Profiles · Tweet Search · Follower Events · KOL TrackingBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS49 / 100 · D75 / 100 · B
Reliability5 / 2010 / 20
Security and permissions7 / 2016 / 20
Maintenance10 / 2018 / 20
Documentation14 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Developers
  • Data analysts
  • Marketers needing real-time Twitter account monitoring
  • AI assistant users integrating Twitter data into workflows
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users who do not need Twitter data
  • Users requiring data from X's official API rather than a third-party API
  • Users concerned about sending data to a third-party service
  • 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
  • Network access to connect to api.6551.io and wss://ai.6551.io
  • API token from environment variable or config.json
  • No file system writes or other local system permissions
  • 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
  • Dependence on third-party API service for data
  • Token leakage could lead to unauthorized usage
  • API service may become unavailable or change
  • Data may be incomplete or delayed as it is not from an official source
  • 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, Cursor, Windsurf, Cline, Continue, Cherry Studio, Zed, OpenClawClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools1511