Rocannon vs dedicated MCP servers
Most MCP servers operate at one layer: the service API. They can query MongoDB collections, describe EC2 instances, or list Kubernetes pods. None of them can touch the OS underneath. Rocannon operates at the OS and configuration layer, the same layer Ansible has owned for 15 years.
mongod installation and OS configuration. Each does what the other cannot.Collection-by-collection comparison
| Collection | Equivalent MCP server | What Rocannon does that the MCP server cannot | What the MCP server does better |
|---|---|---|---|
amazon.aws |
AWS MCP (awslabs, official) | OS-level config on EC2: packages, users, services, files; cross-cloud plays; Vault-sourced credentials | CloudWatch log correlation, cost analysis, IAM-governed access, interactive resource discovery |
azure.azcollection |
Azure MCP (Microsoft, official) | Configure VMs after provisioning; multi-cloud orchestration; combining ARM + host config in one run | Azure CLI generation, VS Code integration, conversational resource management |
google.cloud |
Google Cloud MCP (50+ official managed servers) | OS-level config on GCE VMs; self-managed database setup; no local install required on GCP's side | BigQuery, GKE, Cloud SQL via natural language; remote managed endpoints |
kubernetes.core |
kubernetes-mcp-server (Red Hat/containers, GA) | Node-level OS config before the K8s API exists; kubeadm bootstrap; containerd and kubelet management | Conversational cluster troubleshooting, log correlation, multi-cluster inspection |
community.docker |
Docker MCP Toolkit (Docker Desktop 4.62+) | Install Docker Engine on bare hosts; configure daemon.json; manage containers across an inventory | GUI-integrated server discovery, Docker Desktop catalog |
community.mongodb |
mongodb-mcp-server (MongoDB, official) | Install mongod, write mongod.conf, build replica sets across inventory hosts, configure OS-level ulimits and firewall | Query documents, Atlas integration, schema analysis, Performance Advisor |
community.postgresql |
No official MCP server (Anthropic reference deprecated July 2025) | Install PostgreSQL, configure pg_hba.conf and postgresql.conf, set up streaming replication across inventory | Interactive SQL for already-running managed instances (community-only servers) |
community.mysql |
No official MCP server (AWS Aurora MCP covers managed Aurora only) | Install MySQL, configure my.cnf, manage replication across self-managed hosts | Managed Aurora SQL via AWS MCP (Aurora only) |
community.hashi_vault |
Vault MCP (HashiCorp, public beta) | Install and initialise Vault on hosts; unseal across a cluster; pull Vault secrets into module arguments for downstream services | Interactive KV/PKI management, secret CRUD via natural language |
cisco.ios / arista.eos |
Cisco Docker Suite / Arista CloudVision MCP (management-plane only) | Idempotent device config via NETCONF/SSH; check/diff before pushing; change-management workflows across device fleets | CloudVision/Catalyst Center conversational queries, telemetry |
ansible.builtin / ansible.posix |
No official MCP server (community SSH servers only) | Idempotent package/service/file/user management; distro-abstracted (apt/yum/dnf); check mode; no raw shell required | Bare imperative shell (community SSH servers, no idempotency) |
When to reach for what
| Situation | Reach for |
|---|---|
| Diagnose a live host, gather facts, apply a targeted fix, all in one conversation | Rocannon |
| Query documents, inspect schemas, manage Atlas clusters | MongoDB MCP server |
| The same task must run reliably across 10+ hosts, on a schedule, or in CI | Ansible playbook (commit from Rocannon with commit_session) |
| Your org runs Ansible Automation Platform and you want Claude to trigger job templates | AAP MCP server (ansible/aap-mcp-server) |
| You only need a shell, with no module library or idempotency | SSH MCP server |
| Both OS and service layer in one session (install MongoDB and query it) | Rocannon + MongoDB MCP server side by side |
| Self-managed PostgreSQL or MySQL (no official MCP server exists) | Rocannon, the only MCP option here |
| Network device config (Cisco, Arista, Juniper), where MCP coverage is thin | Rocannon with cisco.ios, arista.eos, junipernetworks.junos |
Why not just use an SSH MCP server?
SSH MCP gives you a shell. Rocannon gives you Ansible modules: ansible.builtin.copy, community.crypto.x509_certificate, kubernetes.core.k8s. They're typed, idempotent, with check mode and diff. The LLM gets a tool that declares what it does and what it changes, not a raw shell that could do anything.
Why not just write a playbook?
You should, eventually. Rocannon's commit_session tool turns a successful conversation into a standard Ansible playbook that runs with ansible-playbook and no Rocannon in the loop. The workflow is: explore and fix with Rocannon, then commit for the next time it needs to be repeatable.
What plain Ansible still does better
- Multi-host sequencing with
serial,throttle, andrun_once - Approval gates and change-management pipelines
- Compliance drift enforcement via scheduled runs
- Versioned roles and collections as reusable automation packages
- CI/CD integration, triggerable by pipelines, not conversational agents
Rocannon is a conversation partner and exploration tool. When a task needs to be repeatable, auditable, and pipeline-triggerable, commit it to a playbook.