Ansible MCP Server

Created By
tarnovera year ago
MCP for Ansible
Overview

What is Ansible MCP Server?

Ansible MCP Server is a Model Context Protocol (MCP) server designed for Ansible automation, enabling AI assistants to interact with Ansible, execute playbooks, manage inventory, and perform various Ansible operations directly.

How to use Ansible MCP Server?

To use the Ansible MCP Server, clone the repository, install dependencies, build the server, and configure the MCP settings to integrate with your AI assistant.

Key features of Ansible MCP Server?

  • Execute Ansible playbooks with customizable parameters.
  • View and manage Ansible inventory.
  • Validate playbook syntax without execution.
  • Preview tasks that would be executed by a playbook.
  • Access the default Ansible inventory file via a resource API.

Use cases of Ansible MCP Server?

  1. Automating server configurations using Ansible playbooks.
  2. Managing and viewing inventory for deployment tasks.
  3. Validating playbook syntax before execution to prevent errors.
  4. Previewing tasks to understand playbook execution flow.

FAQ from Ansible MCP Server?

  • What are the requirements to run Ansible MCP Server?

Node.js 18 or higher, npm or yarn, and Ansible installed in your PATH.

  • Is there a license for Ansible MCP Server?

Yes, it is licensed under the MIT License.

  • How can I contribute to the project?

You can contribute by modifying the source code, adding new features, and submitting pull requests.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tarnover
Star
1
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago