Integrations
IaC Memory MCP Server
A Model Context Protocol (MCP) server that enhances Claude AI's capabilities by providing persistent memory storage for Infrastructure-as-Code (IaC) components, with a focus on version tracking and relationship mapping for Terraform and Ansible resources.
Note
This was a personal project to determine the state of AI's ability if the person using it (me)
doesn't have subject matter expertise (lack of Python knowledge). Since it has become rather cost
prohibitive, I do not intend to develop or maintain this project further.
Overview
The IaC Memory MCP Server addresses the challenge of maintaining accurate, version-aware context for IaC components by providing:
- Persistent storage and version tracking for IaC components
- Hierarchical resource organization with URI-based access
- Comprehensive relationship mapping between components
- Version-specific documentation management
- Schema validation and temporal metadata tracking
- Automated relationship analysis and insights
Core Components
Resource Management
The server implements a sophisticated resource management system with hierarchical URIs:
Resource URI Structure
Supported platforms:
- terraform
- ansible
- iac (for general infrastructure entities)
Example URIs:
Resource Templates
The server provides dynamic resource templates for standardized access patterns:
- Terraform provider information:
resources://terraform/providers/{provider_name}
- Resource type details:
resources://terraform/resources/{provider_name}/{resource_type}
- Ansible collection data:
resources://ansible/collections/{collection_name}
- Module information:
resources://ansible/modules/{collection_name}/{module_name}
Prompts
The server implements four specialized prompts for IaC component discovery and analysis:
search_resources
- Purpose: Search for IaC resources
- Arguments:
provider
: Provider nameresource_type
: Resource type
- Returns: Information about specific resources for the given provider
analyze_entity
- Purpose: Analyze an entity and its relationships
- Arguments:
entity_id
: Entity IDinclude_relationships
: Include relationships
- Returns: Detailed entity analysis including name, type, and observations
terraform_provider
- Purpose: Get information about a Terraform provider
- Arguments:
provider_name
: Name of the Terraform provider (required)version
: Specific version to query (optional)
- Returns: Detailed provider information for the specified version
ansible_module
- Purpose: Get information about an Ansible module
- Arguments:
collection_name
: Name of the Ansible collection (required)module_name
: Name of the module (required)version
: Specific version to query (optional)
- Returns: Detailed module information for the specified version
Tools
The server implements comprehensive tooling for IaC component management:
Terraform Tools
get_terraform_provider_info
: Retrieve detailed provider information including version and resourceslist_provider_resources
: List all resources available for a specific providerget_terraform_resource_info
: Get detailed information about a specific resource typeadd_terraform_provider
: Register new providers with versioningadd_terraform_resource
: Add resource definitions with schemasupdate_provider_version
: Update provider versions with new documentation
Ansible Tools
get_ansible_collection_info
: Get detailed information about an Ansible collectionlist_ansible_collections
: List all available Ansible collectionsget_collection_version_history
: View version history of a collectionget_ansible_module_info
: Get detailed information about a specific modulelist_collection_modules
: List all modules in a collectionget_module_version_compatibility
: Check version compatibility of modulesadd_ansible_collection
: Register new Ansible collectionsadd_ansible_module
: Add new modules with validation and documentation
Entity Operations
create_entity
: Create new infrastructure entitiesupdate_entity
: Modify existing entity configurationsdelete_entity
: Remove entities with relationship cleanupview_relationships
: Analyze entity dependencies and relationships
Configuration
The server supports configuration through environment variables:
DATABASE_URL
: SQLite database locationMCP_DEBUG
: Enable debug logging when setMCP_TEST_MODE
: Enable test mode for database resets
For development, create a .env
file:
Integration with Claude Desktop
Development Setup
Production Setup
Development
Local Development
License
This project is licensed under the MIT License - see the LICENSE file for details.
You must be authenticated.
hybrid server
The server is able to function both locally and remotely, depending on the configuration or use case.
Tools
A custom Memory MCP Server that acts as a cache for Infrastructure-as-Code information, allowing users to store, summarize, and manage notes with a custom URI scheme and simple resource handling.
Related Resources
Related MCP Servers
- AsecurityAlicenseAqualityA MCP server for managing and storing code snippets in various programming languages, allowing users to create, list, and delete snippets via a standardized interface.Last updated -34JavaScriptMIT License
- -securityFlicense-qualityA simple note-taking MCP server that allows storing and summarizing notes with custom URI schemes and provides functionality to add notes and generate summaries with different detail levels.Last updated -5Python
- -securityFlicense-qualityAn MCP server that provides tools and resources for managing a coding project's todo list, allowing users to view, add, update, and delete todo items with details like priority, status, and tags.Last updated -1Python
- -securityFlicense-qualityAn MCP server that allows Claude and other LLMs to manage persistent memories across conversations through text file storage, enabling commands to add, search, delete and list memory entries.Last updated -2TypeScript