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.

DimensionGEML MCP ServerAn MCP server for GEML documents, enabling block-at-a-time edits with validation.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS68 / 100 · C76 / 100 · B
Reliability12 / 2013 / 20
Security and permissions14 / 2014 / 20
Maintenance13 / 2018 / 20
Documentation16 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Documentation workflows that have adopted GEML.
  • Collaborative authoring with AI agents or scripts where safety is required.
  • Software development workflows that rely on documentation or code skeletons.
  • 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
  • Repositories that don't use GEML.
  • As a general-purpose file system tool.
  • Use cases requiring a network-accessible MCP server.
  • 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 and write access to files under the directory specified by --root, and only that directory.
  • Fetching packages on demand via npm/npx.
  • Ability to create and write .gemlhistory sidecar files inside the root.
  • 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
  • Misconfigured --root may cause unexpected changes, but writes outside the directory are explicitly refused.
  • Invalid document modifications are refused, but network access is needed for package installation.
  • History files may grow over time; tracking quotas is outside the root.
  • Vulnerable to misconfiguration of clients or tools; ensure the --root path is correct.
  • 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 Desktop, Claude Code, Generic MCP clientClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools1215