IaC Memory MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_terraform_provider_infoC | Retrieve comprehensive information about a Terraform provider |
| list_terraform_providersB | List all cached Terraform providers with basic metadata |
| get_provider_version_historyB | Retrieve version history for a specific Terraform provider |
| get_terraform_resource_infoC | Retrieve comprehensive information about a Terraform resource including schema and documentation |
| list_provider_resourcesC | List all resources associated with a specific Terraform provider |
| get_ansible_collection_infoC | Retrieve comprehensive information about an Ansible collection |
| list_ansible_collectionsC | List all cached Ansible collections with basic metadata |
| get_collection_version_historyA | Retrieve version history for a specific Ansible collection |
| get_ansible_module_infoC | Retrieve comprehensive information about an Ansible module including schema and documentation |
| get_resource_version_compatibilityC | Check resource compatibility across provider versions |
| add_terraform_providerB | Add a new Terraform provider to the memory store with version and documentation information |
| update_provider_versionC | Update an existing Terraform provider's version information and documentation links |
| add_terraform_resourceC | Add a new Terraform resource definition with its schema and version information |
| update_resource_schemaC | Update an existing Terraform resource's schema and related information |
| add_ansible_collectionB | Add a new Ansible collection to the memory store with version and documentation information |
| update_collection_versionC | Update an existing Ansible collection's version information and documentation links |
| add_ansible_moduleC | Add a new Ansible module definition with its schema and version information |
| update_module_versionC | Update an existing Ansible module's schema and related information |
| get_module_version_compatibilityC | Check module compatibility across collection versions |
| create_entityC | Create a new entity in the knowledge graph with optional initial observations |
| update_entityC | Update an existing entity's properties and add new observations |
| delete_entityC | Remove an entity and its relationships from the knowledge graph |
| view_relationshipsC | Retrieve all relationships and observations for a specific entity |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| search_resources | Search for IaC resources |
| analyze_entity | Analyze an entity and its relationships |
| terraform_provider | Get information about a Terraform provider |
| ansible_module | Get information about an Ansible module |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Terraform Provider | Access Terraform provider information and resources |
| Terraform Resource | Access specific Terraform resource type information |
| Ansible Collection | Access Ansible collection information and modules |
| Ansible Module | Access specific Ansible module information |
| Entity | Access entity information including observations and relationships |
| Entity Relationships | Access entity relationship information |
TDQS
Scored across 23 tools
Most tools have distinct purposes targeting specific IaC components (Ansible vs. Terraform) and operations (add/get/list/update). However, there is some potential overlap between 'create_entity' and the various 'add_' tools, as both involve storing information, though 'create_entity' seems more generic for a knowledge graph. The descriptions help clarify boundaries, but an agent might need to infer when to use 'create_entity' versus the specific 'add_' tools.
Tool names follow a highly consistent verb_noun pattern throughout, with clear and predictable conventions. All tools use snake_case, and verbs like 'add', 'get', 'list', 'update', 'delete', and 'view' are applied consistently across similar resource types (e.g., 'add_ansible_collection', 'get_ansible_collection_info', 'list_ansible_collections'). This makes the tool set easy to navigate and understand.
With 23 tools, the count is on the higher side for an MCP server, bordering on heavy. While the server covers both Ansible and Terraform domains comprehensively, the number of tools might feel overwhelming or lead to redundancy (e.g., separate tools for version history and compatibility checks). A more streamlined set could improve usability without losing functionality, placing it in the borderline range.
The tool surface provides complete CRUD/lifecycle coverage for both Ansible and Terraform components, including adding, retrieving, listing, updating, and deleting entities. It also handles version management, compatibility checks, and relationship viewing for a knowledge graph. No obvious gaps exist; agents can perform all expected operations for managing IaC metadata and entities without dead ends.