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.

DimensionSemSemantic version control on top of Git, giving AI coding agents entity-level code intelligenceContext7Upstash's official server providing up-to-date third-party library docs for AI coding assistants
FMRS69 / 100 · C80 / 100 · B
Reliability11 / 2014 / 20
Security and permissions14 / 2016 / 20
Maintenance13 / 2017 / 20
Documentation17 / 2015 / 20
Setup experience14 / 2018 / 20
Best for
  • Developers using AI coding agents who want to reduce token consumption
  • Teams that need cross-file impact analysis and entity-level diffs
  • Projects working in Git repos that want deterministic dependency-graph answers instead of grep results
  • Developers using fast-moving frameworks/libraries worried about the AI suggesting stale code
  • Scenarios wanting zero-config documentation lookup
Not for
  • Users who do not use an MCP client
  • Scenarios needing browser automation, cloud storage, or database access
  • Users wanting a zero-install experience: running sem mcp requires the sem binary to be installed first
  • Looking up internal/private codebase documentation (Context7 targets publicly published open-source libraries)
  • Cases needing very high coverage of obscure, niche libraries (coverage depends on what Context7's platform has indexed)
Required permissions
  • Read local code repository files
  • Store a SQLite entity cache and query index on the local machine (by default under the OS cache directory; overridable with SEM_CACHE_DIR)
  • Optional: log in to sem cloud via the GitHub device flow with sem login (only needed for cloud acceleration)
  • Usable without an API key (subject to a free-tier rate limit); CONTEXT7_API_KEY is an optional credential for higher quota
  • Read-only documentation lookup — no code execution or local filesystem access involved
Risks and side effects
  • The sem binary name conflicts with the sem binary shipped by GNU Parallel; run sem --version to check which one you are using
  • The entity cache is stored outside the repository by default under the OS cache directory, and setting SEM_CACHE_DIR can change its location
  • Cloud queries are opt-in per repo; logging in does not by itself upload a repo or send a query, but enabling cloud queries does send data to sem cloud
  • Local telemetry records command names on your own machine only and uploads nothing in that mode; opting in uploads counts, and SEM_NO_TELEMETRY=1 or DO_NOT_TRACK=1 forces the record-nothing behavior
  • Agents issue read queries against repository code, so ensure their working directory and permission scope match your expectations
  • The free tier has limited quota — high-frequency use may hit rate limits
  • Documentation content comes from Context7's platform index, so its accuracy and freshness depend on that platform's crawl cadence
Supported clientsClaude Code, Cursor, Claude DesktopClaude Code, VS Code, Cursor, Cline, Amp
Tools82