ansible-flow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANSIBLE_FLOW_TIMEOUT | No | Seconds (default 120 module / 300 playbook) | |
| ANSIBLE_FLOW_INVENTORY | No | Default -i inventory | |
| ANSIBLE_FLOW_CATALOG_DIR | No | Override catalog path | |
| ANSIBLE_FLOW_COLLECTIONS | No | Comma-separated collection allowlist override | |
| ANSIBLE_FLOW_PLAYBOOK_ROOTS | No | Extra colon-separated playbook path roots | |
| OPENFLOW_ANSIBLE_PLAYBOOK_ROOTS | No | Same roots (OpenFlow-compatible alias) |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_modulesA | Search allowlisted Ansible modules (gallery) by name, FQCN, collection, or description. |
| get_module_schemaA | Return slim arg schema for a module FQCN (when catalog has it). |
| run_moduleB | Run an Ansible module via local ansible CLI. Prefer check_mode=true first. |
| run_playbookA | Run ansible-playbook on a path under allowlisted roots. Prefer check_mode=true first. |
| list_collectionsA | List collections present in the committed gallery. |
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 5 tools
Each tool targets a distinct action: searching the module catalog, retrieving module schemas, running a module, running a playbook, and listing collections. There is no functional overlap between any of the tools, making selection unambiguous.
All tool names follow a consistent verb_noun pattern using snake_case: search_modules, get_module_schema, run_module, run_playbook, list_collections. The naming is predictable and uniform across the entire set.
With 5 tools, the set is well-scoped for an Ansible flow server. It covers the essential operations of discovering, inspecting, and executing Ansible content without unnecessary bloat or heaviness.
The toolset covers the core lifecycle: discover (search/list), inspect (get schema), and execute (run module/playbook). A minor gap is the lack of a direct way to list playbooks or manage inventory, but these are not essential for the stated flow-centric purpose.