Terraform MCP Assistant

Created By
jashkahara year ago
This project provides an MCP (Model Context Protocol) server that exposes Terraform infrastructure-as-code operations through natural language. It enables LLMs to execute Terraform commands and retrieve information about infrastructure without requiring specific command syntax knowledge.
Overview

What is Terraform MCP Assistant?

Terraform MCP Assistant is a server that provides a natural language interface to Terraform operations, allowing users to manage infrastructure using simple English commands instead of complex Terraform syntax.

How to use Terraform MCP Assistant?

To use the Terraform MCP Assistant, clone the repository, set up a virtual environment, install dependencies, and start the MCP server. You can then issue commands in natural language to manage your Terraform infrastructure.

Key features of Terraform MCP Assistant?

  • Natural language processing of Terraform commands
  • Execution plan visualization
  • State inspection and management
  • Infrastructure deployment and destruction
  • Configuration documentation
  • Automatic workspace validation
  • Error handling and formatted output

Use cases of Terraform MCP Assistant?

  1. Managing Terraform infrastructure without needing to remember command syntax.
  2. Visualizing execution plans for better understanding of changes.
  3. Quickly inspecting the current state of infrastructure.
  4. Simplifying the deployment and destruction of resources.

FAQ from Terraform MCP Assistant?

  • Can I use any natural language command?

Yes! You can issue commands in simple English to manage your Terraform infrastructure.

  • Is there a specific syntax I need to follow?

No, the assistant is designed to interpret natural language commands, making it easier to use.

  • What programming language is the project built with?

The project is built using Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jashkahar
Star
0
Language
Python
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