tfmcp: Terraform Model Context Protocol Tool

Created By
nwiizoa year ago
🌍 Terraform Model Context Protocol (MCP) Tool - An experimental CLI tool that enables AI assistants to manage and operate Terraform environments. Supports reading Terraform configurations, analyzing plans, applying configurations, and managing state with Claude Desktop integration. ⚡️
Overview

What is tfmcp?

tfmcp is an experimental command-line tool that enables AI assistants to manage and operate Terraform environments through the Model Context Protocol (MCP). It allows users to read Terraform configurations, analyze plans, apply configurations, and manage state effectively.

How to use tfmcp?

To use tfmcp, install it via Cargo with cargo install tfmcp, and then run commands like tfmcp analyze to analyze configurations or tfmcp mcp to launch it as an MCP server. Integration with Claude Desktop is also supported for enhanced functionality.

Key features of tfmcp?

  • Deep integration with Terraform CLI for executing operations.
  • Runs as an MCP server for AI assistants.
  • High-speed processing powered by Rust.
  • Automatic setup of sample Terraform projects for new users.

Use cases of tfmcp?

  1. Managing Terraform configurations through AI assistants.
  2. Analyzing and applying Terraform plans efficiently.
  3. Automating infrastructure management tasks with AI integration.

FAQ from tfmcp?

  • Is tfmcp stable?

No, tfmcp is experimental and features may change without notice.

  • What are the requirements?

You need Rust, Terraform CLI, and Claude Desktop for full functionality.

  • Can I contribute to tfmcp?

Yes, contributions are welcome! Please follow the guidelines in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
nwiizo
Star
295
Language
Rust
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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