ansible-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROXMOX_HOST | Yes | Your Proxmox host | |
| PROXMOX_USER | Yes | Your Proxmox user (e.g., root@pam) | |
| PROXMOX_PASSWORD | Yes | Your Proxmox password |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ansible-playbookC | Run an Ansible playbook |
| ansible-taskC | Run a single Ansible task ad-hoc |
| ansible-roleC | Run an Ansible role |
| create-playbookC | Create a new Ansible playbook file |
| list-hostsB | List all hosts in inventory |
| create-playbook-flexibleB | Create an Ansible playbook with flexible input (YAML string or structured data) |
| validate-playbookB | Validate an Ansible playbook syntax |
| generate-inventory-playbookC | Generate a playbook for gathering inventory information |
| create-role-structureB | Create a complete Ansible role directory structure |
| terraform-planB | Create an execution plan for Terraform changes |
| terraform-applyB | Apply Terraform configuration to create/update infrastructure |
| terraform-outputA | Get outputs from Terraform state |
| create-vm-templateC | Generate Terraform configuration for Proxmox VMs |
| discover-proxmoxB | Discover all VMs on a Proxmox server and extract their configuration |
| generate-inventoryC | Generate an Ansible inventory file from discovered Proxmox VMs |
| generate-diagramB | Generate infrastructure diagram from current state |
| capture-stateB | Capture current infrastructure state for change tracking |
| browse-servicesC | Browse available services in the catalog with optional filtering |
| service-detailsC | Get detailed information about a specific service |
| deploy-serviceC | Deploy a service from the catalog by creating VM and configuring it |
| list-environmentsA | List available deployment environments |
| deploy-to-environmentC | Deploy a service to a specific environment |
| create-acceptance-testC | Create an acceptance test deployment |
| add-external-serverB | Add an external server to the Ansible inventory |
| discover-network-devicesC | Discover devices on the network and classify them |
| remove-external-serverA | Remove an external server from inventory |
| test-server-connectivityC | Test connectivity to a server using various methods |
| discover-ansible-controllerB | Discover existing Ansible controllers on the network |
| import-ansible-configB | Import configuration from existing Ansible controller |
| migrate-ssh-keysC | Migrate SSH keys from existing controller |
| hardware-scanC | Comprehensive hardware scan of a system |
| storage-analysisC | Detailed storage analysis including health checks |
| network-interfacesC | Detailed network interface information |
| gpu-detectionC | Detect and analyze GPU hardware |
| hardware-inventoryC | Manage hardware inventory database |
| hardware-benchmarkC | Run basic hardware benchmarks |
| delete-vm-enhancedB | Delete VM from Proxmox and automatically update infrastructure context |
| create-vm-enhancedB | Create VM in Proxmox and automatically update infrastructure context |
| manage-service-enhancedC | Manage services and automatically update their status in context |
| proxmox-inventoryC | Discover and manage Proxmox infrastructure inventory |
| inventory-statusC | Check inventory status and staleness |
| query-sopC | Query standard operating procedures for common MCP operations |
| list-sopsC | List all available standard operating procedures |
| get-best-practiceC | Get best practices for MCP operations |
| get-error-recoveryC | Get error recovery steps for common issues |
| get-validation-checksC | Get validation checks for operations |
| compare-inventory-stateA | Compare context inventory with live Proxmox inventory and detect deviations |
| process-deviationC | Process a specific inventory deviation with user decision |
| check-node-capacityC | Check if a node has capacity for requested resources |
| find-best-nodeC | Find the best node for VM placement based on resources and preferences |
| detect-existing-serviceC | Detect if a service is already installed in the infrastructure |
| handle-duplicate-serviceC | Handle user decision for duplicate service |
| update-ollama-modelsC | Update models on existing Ollama server |
| get-service-sopC | Get installation and management procedures for a specific service |
| list-service-sopsA | List all available service-specific SOPs |
| compare-service-requirementsC | Compare requirements for multiple services |
| store-vm-credentialsC | Store ansible-admin credentials for a VM in context |
| retrieve-vm-credentialsB | Retrieve ansible-admin credentials for a VM |
| generate-secure-passwordC | Generate a secure password for ansible-admin accounts |
| update-context-after-operationC | Update MCP context after successful VM or service operations |
| list-vm-credentialsB | List all VMs with stored credentials |
| validate-templateC | Validate a template meets MCP standards |
| fix-templateC | Fix non-compliant template issues |
| discover-templatesC | Discover and validate all templates in infrastructure |
| create-compliant-templateC | Create a new MCP-compliant template from a base VM |
| security-scan-portsC | Scan for open ports on specified hosts |
| security-check-passwordsC | Check for weak passwords and password policies |
| security-audit-accountsC | Audit user accounts for security issues |
| security-check-updatesC | Check for security updates and vulnerable packages |
| security-check-firewallB | Check firewall configuration and rules |
| security-check-sshC | Audit SSH configuration for security |
| security-quick-scanC | Run a quick security assessment covering basic checks |
| server-restartA | Restart MCP or SSE server to recover from errors |
| server-logsC | Get server logs for debugging |
| server-healthD | Check server health and dependencies |
| server-debugC | Run diagnostic commands for debugging |
| setup-proxmoxC | Configure Proxmox connection settings |
| setup-networkC | Configure network settings for VMs |
| setup-servicesC | Configure IP addresses for services |
| get-configC | Get current configuration values |
| test-connectionC | Test connection to configured services |
| setup-wizardA | Run interactive setup wizard to configure all settings |
| get-mcp-contextB | Get stored context information from MCP |
| set-mcp-contextB | Store context information in MCP for future sessions |
| load-service-toolsC | Load tools specific to a service |
| unload-service-toolsC | Unload tools specific to a service |
| list-loaded-toolsA | List all currently loaded tools and services |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 87 tools
Several tools have unclear boundaries, such as create-playbook vs create-playbook-flexible, discover-proxmox vs proxmox-inventory, and test-server-connectivity vs test-connection. The large number of overlapping operational areas makes it easy for an agent to select the wrong tool despite mostly descriptive names.
The tool names consistently use lowercase hyphenated snake_case, which is readable. However, the pattern is mixed: many are verb_noun like create-playbook, but others are noun_noun like inventory-status or noun_verb like server-restart, so the convention is not strictly enforced.
With 87 tools, the server is dramatically over-scoped for an Ansible-focused MCP. Many tools cover tangential domains like Terraform, hardware benchmarking, security scanning, and server debugging, making the toolset unwieldy and difficult for agents to navigate effectively.
The toolset provides broad lifecycle coverage across Ansible playbooks, Proxmox VM management, inventory, credentials, services, security checks, and context persistence. Minor gaps exist, such as no explicit Terraform destroy/state tool or playbook update/delete, but overall agents have enough tools to complete most workflows without dead ends.