MCP SysOperator

MCP for Ansible, Terraform, LocalStack, and other IaC tools. Create and iterate IaC

typescript

24

GitHub Stars

typescript

Language

6 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": {
    "tarnover-mcp-sysoperator": {
      "command": "node",
      "args": [
        "/absolute/path/to/mcp-sysoperator/build/index.js"
      ]
    }
  }
}

You have an MCP server that acts as a bridge between AI assistants and infrastructure tools. It lets you run Ansible playbooks, manage Terraform workflows, and interact with cloud resources directly from your AI-powered automation tasks, all with a practical, programmable interface.

How to use

You connect to the MCP SysOperator server from your MCP client and choose the tool you want to run. Practical workflows include executing Ansible playbooks with custom inventory and variables, previewing or validating playbooks, listing AWS resources, and running Terraform operations such as init, plan, and apply. You can also test configurations locally with LocalStack and fetch the default inventory for quick reference.

How to install

Prerequisites you need before installing: a supported runtime and tooling stack, including Node.js 18 or higher, npm or yarn, and Ansible installed and accessible in your system PATH. For AWS operations, ensure the AWS CLI is configured with credentials. If you plan to use LocalStack for local AWS testing, install and run LocalStack and the awslocal CLI.

Step 1: Clone the project repository and navigate into it.

Step 2: Install dependencies.

Step 3: Build the server.

Step 4: Configure MCP settings to register SysOperator as an MCP server. Use the following configuration in your MCP client settings.

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

Additional notes

LocalStack integration is included to enable AWS-related testing without real credentials. It provides a convenient way to validate Ansible playbooks and Terraform configurations against a simulated AWS environment.

A quick LocalStack workflow you can try locally involves starting LocalStack, then running a sample playbook against the LocalStack-enabled AWS services.

# Install LocalStack and awslocal CLI
pip install localstack awscli-local

# Start LocalStack
localstack start

# Run a sample playbook against LocalStack
node localstack/run_sample_playbook.mjs

Available tools

run_playbook

Execute Ansible playbooks with support for parameters like inventory, extra vars, tags, and limits.

list_inventory

View hosts and groups from an Ansible inventory file.

check_syntax

Validate Ansible playbook syntax without executing the playbook.

list_tasks

Preview the tasks that would be executed by a playbook.

inventory_resource

Access the default Ansible inventory via the resource API.

aws_s3

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

terraform

Execute Terraform workflows including init, plan, apply, destroy, and output.

localstack_integration

Test AWS-related operations locally using LocalStack and tflocal workflows.