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.

DimensionAnsible Automation Platform MCP ServerAn MCP service exposing Ansible Automation Platform APIs through OpenAPI specificationsGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS52 / 100 · D76 / 100 · B
Reliability9 / 2013 / 20
Security and permissions8 / 2014 / 20
Maintenance10 / 2018 / 20
Documentation13 / 2017 / 20
Setup experience12 / 2014 / 20
Best for
  • Teams that already run Ansible Automation Platform and hold a valid AAP authentication token
  • Ops and automation engineers who want MCP clients to call AAP APIs with role- and permission-limited tool access
  • Offline or customized environments that need OpenAPI specs loaded from local files or custom URLs
  • 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 AAP instance or a valid token
  • Clients that require stdio local-process transport (this service is an HTTP endpoint)
  • Users expecting write operations to be enabled by default (writes require ALLOW_WRITE_OPERATIONS=true)
  • 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
  • A valid AAP authentication token (Authorization: Bearer or BEARER_TOKEN_OAUTH2_AUTHENTICATION)
  • A token with permission to access the AAP services in use
  • Write operations are disabled by default and require ALLOW_WRITE_OPERATIONS=true
  • Network access to the AAP base URL, or read access to configured local OpenAPI files
  • 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
  • Setting ignore-certificate-errors: true for development disables HTTPS certificate validation, enabling man-in-the-middle risk
  • With ALLOW_WRITE_OPERATIONS enabled, write operations allowed by the token can be performed and may modify or delete AAP resources unintentionally
  • The token appears in plain text on the command line, in environment variables, or in client configuration and may leak
  • Available tools and permissions depend on token permissions and toolset configuration; misconfiguration can expose more operations than intended
  • 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 clientsClaudeClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools015