能力标签

🔌 MCP 🤖 Agent 🔄 工作流 🐳 Docker 💻 CLI 🔗 REST API 🧠 Claude ✨ GPT

🔌

MCP工具

Rocannon

基于 Python · 让 AI 助手直接操作你的系统与工具

英文名：rocannon

⭐ 5 Stars 💻 Python 📄 MIT 🏷 AI 8.0分

8.0AI 综合评分

ansiblemcpautomation

⬇ 下载源码 ZIP ⚙️ 配置说明 📺 TG 频道

✦ AI Skill Hub 推荐

Rocannon 是 AI Skill Hub 本期精选MCP工具之一。综合评分 8.0 分，整体质量较高。我们强烈推荐将其纳入你的 AI 工具库，帮助提升工作效率。

📚 深度解析

Rocannon 是一款基于 MCP（Model Context Protocol）标准协议的 AI 工具扩展。MCP 协议由 Anthropic 开发并开源，旨在建立 AI 模型与外部工具之间的标准化通信接口，目前已被 Claude Desktop、Claude Code、Cursor 等主流 AI 工具采纳。

通过安装 Rocannon，你的 AI 助手将获得额外的工具调用能力，可以用自然语言直接操控该工具的功能，无需学习复杂的命令行语法。MCP 工具的核心价值在于"一次配置，永久增强"——配置完成后，每次与 AI 对话时都可以无缝调用这些工具。

在技术实现上，MCP 工具通过标准的 JSON-RPC 协议与 AI 客户端通信，工具的功能以"工具列表"的形式暴露给 AI 模型，AI 可以按需调用。Rocannon 提供了结构化的工具调用接口，使 AI 模型能够精确地理解和使用每个功能点，显著降低 AI 在工具使用上的错误率。

与传统的 API 集成相比，MCP 工具的优势在于无需编写代码——用户只需在配置文件中添加几行 JSON，即可让 AI 获得全新能力。AI Skill Hub 将 Rocannon 评为 AI 评分 8.0 分，属于同类工具中的优质选择。

📋 工具概览

Rocannon 是一款遵循 MCP（Model Context Protocol）标准协议的 AI 工具扩展。通过 MCP 协议，它可以让 Claude、Cursor 等主流 AI 客户端直接访问和操作外部工具、数据源和服务，实现 AI 能力的无缝扩展。无论是文件操作、数据库查询还是 API 调用，都可以通过自然语言在 AI 对话中直接触发，极大提升生产效率。

GitHub Stars

⭐ 5

开发语言

Python

支持平台

Windows / macOS / Linux

维护状态

轻量级项目，按需更新

开源协议

MIT

AI 综合评分

8.0 分

工具类型

MCP工具

Forks

—

📖 中文文档

以下内容由 AI Skill Hub 根据项目信息自动整理，如需查看完整原始文档请访问底部「原始来源」。

📌 核心特色

通过标准 MCP 协议与 Claude、Cursor 等主流 AI 客户端深度集成
提供结构化工具调用接口，显著降低 AI 集成复杂度
支持 Claude Desktop 和 Claude Code 无缝接入，开箱即用
可与其他 MCP 工具组合叠加，构建完整 AI 工作站
轻量无侵入设计，不影响现有系统架构

🎯 主要使用场景

在 Claude Desktop 对话中直接调用本地工具，实现 AI 与系统的深度联动
通过自然语言驱动复杂的多步骤自动化任务，代替繁琐手动操作
将多个 MCP 工具组合使用，构建个人专属 AI 工作站

以下安装命令基于项目开发语言和类型自动生成，实际以官方 README 为准。

安装命令

# 方式一：通过 Claude Code CLI 一键安装
claude skill install https://github.com/msradam/rocannon

# 方式二：手动配置 claude_desktop_config.json
{
  "mcpServers": {
    "rocannon": {
      "command": "npx",
      "args": ["-y", "rocannon"]
    }
  }
}

# 配置文件位置
# macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
# Windows: %APPDATA%/Claude/claude_desktop_config.json

📋 安装步骤说明

确认已安装 Node.js（v18 或以上版本）
打开 Claude Desktop 或 Claude Code 的 MCP 配置文件
按「交给 Agent 安装 → Claude Desktop」标签中的 JSON 配置填入 mcpServers 字段
保存配置文件并重启 Claude 客户端
重启后，在对话中即可使用本工具

以下用法示例由 AI Skill Hub 整理，涵盖最常见的使用场景。

常用命令 / 代码示例

# 安装后在 Claude 对话中直接使用
# 示例：
用户: 请帮我用 Rocannon 执行以下任务...
Claude: [自动调用 Rocannon MCP 工具处理请求]

# 查看可用工具列表
# 在 Claude 中输入："列出所有可用的 MCP 工具"

以下配置示例基于典型使用场景生成，具体参数请参照官方文档调整。

配置示例

// claude_desktop_config.json 配置示例
{
  "mcpServers": {
    "rocannon": {
      "command": "npx",
      "args": ["-y", "rocannon"],
      "env": {
        // "API_KEY": "your-api-key-here"
      }
    }
  }
}

// 保存后重启 Claude Desktop 生效

📑 README 深度解析真实文档完整度 37/100 查看 GitHub 原文 →

以下内容由系统直接从 GitHub README 解析整理，保留代码块、表格与列表结构。

简介

Rocannon

Every installed Ansible module and role, as a typed MCP tool.

Rocannon runs on your Ansible control node and turns it into an MCP server. At startup it reads ansible-doc and exposes every module you have installed (plus any role with an argument spec) as a typed tool, so an MCP client like Claude Code, Cursor, or your own agent can drive your real environment in plain English. The tool surface is whatever you have installed, one collection or a hundred. Each tool's name is its Ansible FQCN with dots swapped for underscores (e.g. ansible.builtin.copy becomes ansible_builtin_copy), the form OpenAI-style function calling requires; the original FQCN stays in the tool's description.

demo

Claude Haiku driving Rocannon's typed Ansible tools against a real RHEL 9 host.

Install

pip install rocannon

This brings ansible-core and ansible-runner with it. rocannon doctor checks the environment for anything missing.

Quickstart

rocannon quickstart

Scaffolds a localhost profile under .rocannon/ and prints the wiring for your MCP client (Claude Code, Claude Desktop, Cursor) plus a command to confirm the tools registered. Then ask your assistant something like "Gather facts from localhost and tell me the OS and kernel version."

You don't need an LLM, though. The same tools are a shell:

rocannon mcp doctor --profile .rocannon/quickstart.yml   # list registered tools
rocannon repl       --profile .rocannon/quickstart.yml   # operator shell

Examples

- examples/case-study: natural language to ad-hoc Ansible on a real RHEL 9 host, then replayed as a standard playbook. - examples/containerlab: the same agent driving a two-node Arista cEOS fabric, where the arista.eos modules become tools. - examples/execution-environment: Rocannon baked into an Ansible Execution Environment for a frozen, reproducible tool set. - examples/execution-environment-dispatch: the opposite shape, Rocannon stays on the control host and dispatches each module call into a plain EE image instead.

Rocannon vs dedicated MCP servers

Most MCP servers target one layer: the service API. The MongoDB MCP server queries documents. The AWS MCP server describes EC2 instances. The Kubernetes MCP server inspects pods. None of them can touch the OS underneath.

Rocannon operates at the OS and configuration layer — the same layer Ansible has always owned. That makes it complementary to service-layer MCP servers, and the only MCP option for domains that have no official server at all.

Collection	What it does that service MCP can't	Equivalent service MCP
`amazon.aws`	Configure the OS on EC2 — packages, users, services, files	AWS MCP (awslabs)
`azure.azcollection`	Configure VMs after provisioning; multi-cloud plays	Azure MCP (Microsoft, official)
`google.cloud`	Configure GCE VMs; self-managed DBs on GCE	Google Cloud MCP (50+ official servers)
`kubernetes.core`	Configure nodes before the API exists; bootstrap kubeadm	kubernetes-mcp-server (Red Hat)
`community.mongodb`	Install `mongod`, write `mongod.conf`, build replica sets across hosts	MongoDB MCP (official)
`community.postgresql`	Install PostgreSQL, configure `pg_hba.conf`, set up streaming replication	No official MCP server
`community.mysql`	Install MySQL, configure `my.cnf`, manage replication	No official MCP server
`community.hashi_vault`	Install and initialize Vault on hosts; pull Vault secrets into module args	Vault MCP (HashiCorp, beta)
`cisco.ios` / `arista.eos`	Idempotent device config via NETCONF/SSH; `--check`/`--diff` before pushing	Cisco/Arista management-plane MCP only
`ansible.builtin` / `ansible.posix`	Package, service, file, user management — abstracted across distros	SSH MCP (community only, raw shell)

A few things stand out from this table:

Self-managed PostgreSQL and MySQL have no official MCP server. The Anthropic reference Postgres server was deprecated in July 2025. For those, Rocannon is the only MCP path.
Network automation is where MCP coverage is thinnest. cisco.ios, arista.eos, and junipernetworks.junos have decades of vendor investment. The network MCP servers cover management planes (Catalyst Center, CloudVision), not direct device configuration.
Dedicated service MCP servers do some things better. MongoDB MCP's Atlas integration, AWS MCP's CloudWatch log correlation, and Google Cloud MCP's managed remote endpoints are genuinely useful for their specific domains. Use them alongside Rocannon when you need both layers.

The typical workflow:

Use a service MCP server to query and explore (MongoDB MCP to inspect a collection, AWS MCP to find a misconfigured security group).
Use Rocannon to act at the OS or config layer (fix the EC2 user data, restart a service, push a patched config file).
Run commit_session to save the successful steps as a standard ansible-playbook-runnable YAML — no Rocannon needed for the next run.

What plain Ansible still does better than Rocannon: multi-host sequencing with serial, throttle, and run_once; change-management pipelines; scheduled drift enforcement; versioned roles and collections. Rocannon is for exploration and targeted action. When a task needs to be repeatable and auditable, commit it to a playbook.

🎯 aiskill88 AI 点评 A 级 2026-07-05

高质量的MCP工具，简化Ansible服务器生成