IAC Memory MCP Server
Related Servers
Alternatives to IAC Memory MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAn MCP server for managing and persisting notes, offering CRUD operations, note summarization, and resource-based access via a note:// URI scheme.47MIT
- FlicenseNot gradedqualityDmaintenanceA simple notes MCP server that enables creating, listing, and summarizing text notes via resources, tools, and prompts.-
- FlicenseNot gradedqualityDmaintenanceA 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.5-
- FlicenseNot gradedqualityDmaintenanceA note management MCP server that enables users to store, retrieve, and summarize personal notes via a custom URI scheme. It provides tools for adding content and prompts for generating brief or detailed summaries of stored information.-
- FlicenseBqualityDmaintenanceThis TypeScript-based MCP server implements a simple notes system, allowing the creation, listing, and summarization of text notes using MCP concepts with note:// URIs and metadata.1-
- AlicenseNot gradedqualityBmaintenanceA local persistent memory and developer scratchpad MCP server that allows AI assistants to store, search, and manage notes across chat sessions.MIT
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.