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.

DimensionDokploy MCP ServerManage Dokploy through MCP.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS44 / 100 · D76 / 100 · B
Reliability8 / 2013 / 20
Security and permissions4 / 2014 / 20
Maintenance6 / 2018 / 20
Documentation13 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Teams already operating Dokploy and needing API automation
  • Developers who want centralized Dokploy resource management in an MCP client
  • 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 a Dokploy server or API token
  • Use cases requiring management of platforms other than Dokploy without a corresponding API
  • 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
  • Access to the Dokploy server URL is required
  • A Dokploy API authentication token is required
  • Depending on the API operation, the server may have permission to create, modify, deploy, stop, delete, and manage security-sensitive resources
  • 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 server exposes a broad range of Dokploy API operations, including potentially destructive deployment, stop, deletion, password, and security actions
  • API responses may contain environment variables, tokens, passwords, or other sensitive fields; set DOKPLOY_REDACT_ENV=true to redact them
  • Protect DOKPLOY_API_KEY and any service tokens supplied through DOKPLOY_CUSTOM_HEADERS
  • 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 clientsCursor, Windsurf, VS Code, Claude Code, Zed, Claude Desktop, BoltAIClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools015