A
licenseNot graded
qualityF
maintenanceConnects AI models to the Terraform Registry via MCP, enabling provider lookups, resource usage examples, and module recommendations for streamlined Terraform workflows.
448 npm
120
MIT
Terraform Registry MCP Server
by Qvakk
Related Servers
Alternatives to Terraform Registry MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to query an approved Terraform module registry and generate compliant Azure infrastructure code. It provides tools for module discovery, scaffolding, and validation against organizational standards.MIT
OpenTofu MCP Serverofficial
AlicenseAqualityBmaintenanceA Model Context Protocol server that allows AI assistants to search for and retrieve information about OpenTofu providers, modules, resources, and data sources from the OpenTofu Registry.5160 npm108Mozilla Public 2.0- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search and retrieve detailed package information from multiple package registries (NPM, crates.io, NuGet, PyPI, Go).609 npmMIT
- FlicenseBqualityDmaintenanceEnables AI assistants to interact with Terraform Cloud workspaces and runs, including checking run status, listing workspaces, and retrieving detailed information about workspaces and runs.4-
- AlicenseAqualityCmaintenanceEnables AI agents to manage Terraform modules by searching, inspecting, and scaffolding configurations from private GitHub repositories. Also provides backend S3 configuration for generated Terraform code.5MIT
TDQS
A3.9/5.0
Scored across 12 tools
Disambiguation5/5
Every tool has a clearly distinct purpose with no ambiguity. The tools are well-organized into modules vs providers, version retrieval vs detailed documentation, and search vs specific lookups. Even tools like get_provider_docs and get_provider_resource_docs target different documentation scopes (overview vs specific resource).
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with perfect regularity. The naming convention uses get_, list_, and search_ prefixes consistently across modules and providers, making the tool set highly predictable and readable.
Tool Count5/5
With 12 tools, this server is well-scoped for the Terraform Registry domain. It provides comprehensive coverage for both modules and providers, including version management, detailed information retrieval, documentation access, and search capabilities. Each tool earns its place without redundancy.
Completeness5/5
The tool surface offers complete coverage for interacting with the Terraform Registry. It supports the full lifecycle from discovery (search_modules, search_providers) to version management (list/get versions) to detailed documentation (provider docs, resource docs, data source docs). There are no obvious gaps for typical agent workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues