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.

DimensionCircleCI MCP ServerIntegrate CircleCI development workflows with the Model Context Protocol for AI-powered development.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS42 / 100 · D76 / 100 · B
Reliability6 / 2013 / 20
Security and permissions10 / 2014 / 20
Maintenance8 / 2018 / 20
Documentation10 / 2017 / 20
Setup experience8 / 2014 / 20
Best for
  • Developers using MCP-compatible clients like Cursor, VS Code, Claude Desktop.
  • Teams that want to manage CircleCI pipelines seamlessly within their IDE.
  • Developers needing quick diagnostics for build failures and test issues.
  • 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 needing the latest features and security updates, as the package is deprecated and unmaintained.
  • Users seeking a hosted solution; CircleCI's hosted MCP server is recommended.
  • Users needing public remote access unless deploying a self-managed remote server with extra security.
  • 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 a CircleCI Personal API token (CIRCLECI_TOKEN) with read access to projects.
  • In remote mode, requires configuring allowed hosts (MCP_ALLOWED_HOSTS) and authentication.
  • File-related tools may read/write files; set MCP_FILE_OUTPUT_ROOTS to restrict root directories.
  • 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
  • Token exposure: if the personal or shared token leaks, unauthorized operations may occur.
  • Deprecation risk: the server is no longer maintained, potentially with security or compatibility issues.
  • Remote mode risk: if authentication is disabled (REQUIRE_REQUEST_TOKEN=false), anyone reaching the port can act on the server.
  • 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, VS Code, Claude Desktop, Claude Code, Windsurf, Amazon Q DeveloperClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools1315