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 intelligenceGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS69 / 100 · C76 / 100 · B
Reliability11 / 2013 / 20
Security and permissions14 / 2014 / 20
Maintenance13 / 2018 / 20
Documentation17 / 2017 / 20
Setup experience14 / 2014 / 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
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
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
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
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)
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
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
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude Code, Cursor, Claude DesktopClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools815