MCP SysOperator

An MCP server enabling AI-driven Ansible and Terraform workflows for IaC operations.

typescript

0

GitHub Stars

typescript

Language

5 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "mcp-mirror-tarnover_mcp-sysoperator": {
      "command": "node",
      "args": [
        "/absolute/path/to/mcp-sysoperator/build/index.js"
      ]
    }
  }
}

MCP SysOperator is an MCP server that lets you drive Infrastructure as Code tasks through AI assistants. You can run Ansible playbooks, manage inventories, validate syntax, and execute Terraform workflows, including local testing with LocalStack, all from a single, interoperable MCP endpoint.

How to use

You interact with the MCP SysOperator through your MCP client to perform IaC tasks. Use it to run Ansible playbooks with inventories and extra vars, preview or validate playbooks, manage AWS resources, and drive Terraform init, plan, apply, and destroy steps. You can also test AWS-related work locally with LocalStack and tflocal integrations, making it easier to iterate on infrastructure code before deploying to real cloud accounts.

How to install

Prerequisites you need before installation are Node.js 18 or higher and a working npm or yarn. You also need Ansible installed and available on your system PATH. If you plan to use AWS operations, ensure the AWS CLI is installed and credentials are configured. For LocalStack testing, install and run LocalStack and the awslocal CLI.

Step by step install and run flow you can follow exactly:

# 1. Clone the repository
git clone https://github.com/tarnover/mcp-sysoperator.git
cd mcp-sysoperator

# 2. Install dependencies
npm install

# 3. Build the server
npm run build

# 4. Configure MCP settings by adding the SysOperator MCP server to your client configuration (example snippet shown below)

Configuration snippet for MCP client

{
  "mcpServers": {
    "sysoperator": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-sysoperator/build/index.js"],
      "env": {}
    }
  }
}

Usage notes

After configuration, your MCP client can send tool requests to sysoperator to perform actions such as running playbooks, listing inventories, checking syntax, and managing Terraform workflows. Use the available tools to compose high-level IaC automation scenarios without manually invoking each underlying tool.

Additional sections

LocalStack integration provides a way to test AWS-related operations locally without real credentials. You can run sample playbooks against LocalStack and use awslocal to interact with the simulated services.

Development

Project structure and future extension guidance are provided to help you add new capabilities to the MCP server. If you want to add features, modify the server entry, implement new tool handlers, add type definitions, and rebuild with the standard build command.

Available tools

run_playbook

Execute an Ansible playbook with optional inventory, extra vars, tags, and limits.

list_inventory

List hosts and groups from an Ansible inventory file.

check_syntax

Validate Ansible playbook syntax without executing tasks.

list_tasks

Preview the tasks that would run within a playbook.

inventory_resource

Access the default Ansible inventory via a resource API.

aws_s3

Perform AWS S3 operations such as listing buckets and managing objects.

terraform

Run Terraform actions including init, plan, apply, and destroy with optional variables.