No user-submitted related servers found.
Scored across 22 tools
Every tool pairs a specific resource type (module, plugin, role, collection, skill, doc, cache) with a clear action (search, get, ensure, generate, package, list, clear), so an agent can tell them apart. The only close pairs—get_role_doc vs. get_standalone_role_doc and package_as_plugin vs. package_for_lola—are explicitly scoped to different role kinds or packaging targets.
All tool names use snake_case and follow a predictable verb_noun pattern: search_* for discovery, get_* for retrieval, generate_* for creation, and package_* for distribution. Resource nouns are consistent, and there is no mixing of naming styles or vague verbs.
22 tools falls in the 16–25 borderline range and feels somewhat heavy for a single MCP server. The count is mostly justified by the parallel module/plugin/role/collection matrix, but deprecated/niche tools like package_for_lola and clear_cache add surface area without being core to the workflow.
The tools cover the full Ansible knowledge loop: discover collections/roles/modules/plugins, retrieve documentation, install collections, generate skills, and package the results. Minor gaps exist—no skill deletion/update and no explicit standalone-role skill generator—but agents can work around them via regeneration and generate_role_skill.