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 Workflow BuilderManage n8n workflows through natural language, connecting AI assistants to your automation platform.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS44 / 100 · D76 / 100 · B
Reliability5 / 2013 / 20
Security and permissions7 / 2014 / 20
Maintenance8 / 2018 / 20
Documentation13 / 2017 / 20
Setup experience11 / 2014 / 20
Best for
  • Teams using n8n for automation who want to leverage AI assistants to simplify workflow management.
  • Users who want to create workflows through conversational interfaces without directly using the n8n Web UI.
  • Developers looking to integrate AI assistants into their existing n8n workflows.
  • 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 without an n8n instance or API key.
  • Those seeking a full low-code visual interface rather than AI-driven management.
  • Users requiring direct support or maintenance from the official n8n product team.
  • 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 access to your n8n instance URL (`N8N_HOST`) and an API key (`N8N_API_KEY`).
  • The API key should have appropriate permissions, typically read/write access to workflows, executions, tags, and audits.
  • The server communicates directly with your n8n instance; it does not store data but requires network access.
  • 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
  • API key leakage could lead to unauthorized access to your n8n workflows and data.
  • Misconfiguration could result in unintended workflow modifications, deletions, or executions.
  • Involving automation actions should first be tested on a small scale.
  • When using third-party hosted services (like Smithery.ai), consider data privacy implications.
  • 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, Cline, Continue, Other MCP-compatible clientsClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools1515