IaC Memory MCP Server

Created By
AgentWonga year ago
This is a personal project to see if Claude 3.5 Sonnet can write a moderately complex MCP Server in Python.
Overview

what is IaC Memory MCP Server?

IaC Memory MCP Server is a Model Context Protocol (MCP) server designed to enhance Claude AI's capabilities by providing persistent memory storage for Infrastructure-as-Code (IaC) components, focusing on version tracking and relationship mapping for Terraform and Ansible resources.

how to use IaC Memory MCP Server?

To use the IaC Memory MCP Server, set up the server with the required environment variables, and utilize the provided commands to manage and analyze IaC components through a structured URI system.

key features of IaC Memory MCP Server?

  • Persistent storage and version tracking for IaC components
  • Hierarchical resource organization with URI-based access
  • Comprehensive relationship mapping between components
  • Version-specific documentation management
  • Automated relationship analysis and insights

use cases of IaC Memory MCP Server?

  1. Managing Terraform and Ansible resources with version control.
  2. Analyzing relationships between different IaC components.
  3. Providing a structured approach to access and manage infrastructure entities.

FAQ from IaC Memory MCP Server?

  • What platforms does the server support?

The server supports Terraform and Ansible for managing IaC components.

  • How can I configure the server?

Configuration is done through environment variables, including the database location and debug settings.

  • Is there a license for this project?

Yes, the project is licensed under the MIT License.

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