Ansible MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_playbookC | Run an Ansible playbook |
| list_inventoryC | List Ansible inventory hosts and groups |
| check_syntaxA | Check syntax of an Ansible playbook without executing it |
| list_tasksC | List all tasks that would be executed by a playbook |
| run_ad_hocC | Run an Ansible ad-hoc command against specified hosts |
| vault_encrypt_stringC | Encrypt a string using Ansible Vault |
| vault_decrypt_stringC | Decrypt a string encrypted with Ansible Vault |
| aws_ec2C | Manage AWS EC2 instances (list, create, start, stop, terminate) |
| aws_s3C | Manage AWS S3 buckets and objects |
| aws_vpcC | Manage AWS VPC networks |
| aws_cloudformationC | Manage AWS CloudFormation stacks |
| aws_iamC | Manage AWS IAM roles and policies |
| aws_rdsC | Manage AWS RDS database instances |
| aws_route53C | Manage AWS Route53 DNS records and zones |
| aws_elbC | Manage AWS Elastic Load Balancers |
| aws_lambdaC | Manage AWS Lambda functions |
| aws_dynamic_inventoryC | Create AWS dynamic inventory |
| terraformC | Execute Terraform commands (init, plan, apply, destroy, validate, output, etc.) |
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 18 tools
Most tools are clearly distinct by AWS service or Ansible function, with minimal overlap. However, aws_ec2's broad scope (list, create, start, stop, terminate) could be confused with more specific AWS tools, and terraform seems out of place in an Ansible-focused server, creating some ambiguity.
Tools follow a consistent snake_case pattern throughout, with clear verb_noun structures (e.g., run_playbook, list_inventory). The main deviation is the terraform tool, which lacks a verb prefix, slightly breaking the pattern.
With 18 tools, the count is borderline high for an Ansible server, especially since it includes AWS-specific tools that might be better scoped separately. It feels slightly heavy, but still manageable given the domain coverage.
The toolset covers core Ansible operations (syntax checking, inventory, tasks, ad-hoc commands, playbooks, vault) and extensive AWS management, but lacks tools for other cloud providers or non-AWS infrastructure, which could be gaps for broader automation needs.