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.

Dimensionn8n MCP Client NodeConnect and call MCP servers in n8n workflows.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS40 / 100 · D76 / 100 · B
Reliability5 / 2013 / 20
Security and permissions6 / 2014 / 20
Maintenance7 / 2018 / 20
Documentation11 / 2017 / 20
Setup experience11 / 2014 / 20
Best for
  • n8n users who want to integrate MCP tools into their automation flows.
  • Developers building AI agents that need to call external tools and data sources.
  • Teams that need to quickly connect to various MCP servers, whether local (via npx) or remote (HTTP).
  • 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
  • Developers who need a direct programming interface rather than a graphical workflow.
  • Users without an n8n environment who just want a standalone MCP client.
  • Users who rely on SSE transport and cannot upgrade to HTTP Streamable (SSE is deprecated).
  • 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
  • Requires the ability to install community nodes in n8n.
  • Requires setting the environment variable N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true to use the node as a tool.
  • With STDIO transport, it can execute arbitrary local commands (as defined by the user's command setting), potentially with system permissions.
  • Can make network requests to configured MCP servers, including sending additional headers.
  • 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
  • STDIO commands can execute arbitrary local commands; if misconfigured (e.g., using untrusted servers), it may compromise the system.
  • SSE transport is deprecated and no longer updated, potentially having security vulnerabilities.
  • Environment variables (like API keys) may be stored in n8n credentials; if the n8n instance is not secure, there is a risk of exposure.
  • Running third-party MCP servers (e.g., downloaded via npx) may introduce insecure dependencies.
  • 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 DesktopClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools615