@mhdd_24/ansible-mcp
Related Servers
Alternatives to @mhdd_24/ansible-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables management and analysis of AWS security groups, S3 buckets, and VPC connections via MCP.7MIT
- FlicenseNot gradedqualityCmaintenanceEnables inspecting and managing Kubernetes clusters through MCP, including listing deployments and pods, retrieving logs and events, and scaling or restarting deployments.-
- FlicenseNot gradedqualityCmaintenanceEnables managing Atlas self-hosted installations through MCP, including setup, configuration, health checks, and public metrics.-
- AlicenseNot gradedqualityCmaintenanceEnables users to execute notebook cells, manage environments, and validate workbooks via MCP, facilitating reproducible machine-learning answers.MIT
- AlicenseAqualityCmaintenanceEnables managing GitHub Actions workflows through MCP, including listing and inspecting workflows, triggering workflow_dispatch and repository_dispatch events, and monitoring or canceling workflow runs.718 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables managing Zerobyte backups via MCP, including listing repositories, snapshots, schedules, and restoring backups.-
TDQS
Scored across 4 tools
Each tool targets a distinct action: checking environment, inventory listing, syntax validation, and playbook execution. There is no overlap in purpose, making selection unambiguous.
All tools follow the same ansible_ prefix followed by clear verb_noun structure. This consistent pattern makes the tool names predictable and easy to scan.
With only 4 tools, the server is tightly scoped to the core Ansible workflows. Every tool addresses a fundamental need and none feel redundant or unnecessary.
The server covers the main lifecycle for working with Ansible: verify availability, inspect inventory, validate playbooks, and run them. Missing are advanced features like ad-hoc commands or detailed inventory introspection, but these are not essential for basic operation.