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
Each tool has a clearly distinct purpose with no ambiguity. The tools are organized into well-defined categories: Ansible collections/modules, Terraform providers/resources, and knowledge graph entities. Even tools with similar verbs like 'add_' and 'update_' target different resources, making misselection unlikely.
Tool names follow a highly consistent verb_noun pattern throughout. All tools use snake_case with clear prefixes (add_, get_, list_, update_, delete_, view_) followed by specific resource names. This predictable naming convention makes the tool set easy to navigate and understand.
With 23 tools, the count is slightly high but reasonable given the server's scope covering both Ansible and Terraform infrastructure-as-code components plus a knowledge graph. Each tool appears to serve a specific purpose, though the number might feel heavy compared to more focused servers.
The tool surface provides complete CRUD/lifecycle coverage for both Ansible and Terraform domains, plus comprehensive entity management for the knowledge graph. There are no obvious gaps - tools cover addition, retrieval, listing, updating, deletion, version history, compatibility checking, and relationship viewing for all resource types.