Terraform Registry▌
by thrashr888
Integrate Terraform Registry with infrastructure as code tools for seamless provider lookup, module recommendations, and
Integrates with the Terraform Registry API to enable provider lookup, resource usage examples, module recommendations, and schema details retrieval for infrastructure-as-code development.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / DevOps engineers writing Terraform configurations
- / Infrastructure developers exploring new providers
- / Teams standardizing on Terraform modules
capabilities
- / Search for Terraform modules and policies
- / Get provider details and documentation
- / Retrieve resource usage examples
- / List data sources for providers
- / Get resource argument specifications
- / Access provider upgrade guides
what it does
Connects to the Terraform Registry API to look up provider details, resource examples, module recommendations, and schema information for infrastructure-as-code projects.
about
Terraform Registry is a community-built MCP server published by thrashr888 that provides AI assistants with tools and capabilities via the Model Context Protocol. Integrate Terraform Registry with infrastructure as code tools for seamless provider lookup, module recommendations, and It is categorized under cloud infrastructure, developer tools. This server exposes 10 tools that AI clients can invoke during conversations and coding sessions.
how to install
You can install Terraform Registry in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport. This server supports remote connections over HTTP, so no local installation is required.
license
MIT
Terraform Registry is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
Terraform Registry MCP Server
A Model Context Protocol (MCP) server that provides tools for interacting with the Terraform Registry API. This server enables AI agents to query provider information, resource details, and module metadata.
[!IMPORTANT] This project was used as a PoC for a new official Terraform MCP server. This repo has been archived in favor of that one.
Installation
Installing in Cursor
To install and use this MCP server in Cursor:
-
In Cursor, open Settings (⌘+,) and navigate to the "MCP" tab.
-
Click "+ Add new MCP server."
-
Enter the following:
- Name: terraform-registry
- Type: command
- Command: npx -y terraform-mcp-server
-
Click "Add" then scroll to the server and click "Disabled" to enable the server.
-
Restart Cursor, if needed, to ensure the MCP server is properly loaded.
Installing in Claude Desktop
To install and use this MCP server in Claude Desktop:
-
In Claude Desktop, open Settings (⌘+,) and navigate to the "Developer" tab.
-
Click "Edit Config" at the bottom of the window.
-
Edit the file (
~/Library/Application Support/Claude/claude_desktop_config.json) to add the following code, then Save the file.
{
"mcpServers": {
"terraform-registry": {
"command": "npx",
"args": ["-y", "terraform-mcp-server"]
}
}
}
- Restart Claude Desktop to ensure the MCP server is properly loaded.
Tools
The following tools are available in this MCP server:
Core Registry Tools
| Tool | Description |
|---|---|
providerDetails | Gets detailed information about a Terraform provider |
resourceUsage | Gets example usage of a Terraform resource and related resources |
moduleSearch | Searches for and recommends Terraform modules based on a query |
listDataSources | Lists all available data sources for a provider and their basic details |
resourceArgumentDetails | Fetches comprehensive details about a resource type's arguments |
moduleDetails | Retrieves detailed metadata for a Terraform module |
functionDetails | Gets details about a Terraform provider function |
providerGuides | Lists and views provider-specific guides and documentation |
policySearch | Searches for policy libraries in the Terraform Registry |
policyDetails | Gets detailed information about a specific policy library |
Terraform Cloud Tools
These tools require a Terraform Cloud API token (TFC_TOKEN):
| Tool | Description |
|---|---|
listOrganizations | Lists all organizations the authenticated user has access to |
privateModuleSearch | Searches for private modules in an organization |
privateModuleDetails | Gets detailed information about a private module |
explorerQuery | Queries the Terraform Cloud Explorer API to analyze data |
listWorkspaces | Lists workspaces in an organization |
workspaceDetails | Gets detailed information about a specific workspace |
lockWorkspace | Locks a workspace to prevent runs |
unlockWorkspace | Unlocks a workspace to allow runs |
listRuns | Lists runs for a workspace |
runDetails | Gets detailed information about a specific run |
createRun | Creates a new run for a workspace |
applyRun | Applies a run that's been planned |
cancelRun | Cancels a run that's in progress |
listWorkspaceResources | Lists resources in a workspace |
Resources
The MCP server supports the following resource URIs for listing and reading via the resources/* methods:
| Resource Type | Example URI(s) | Description |
|---|---|---|
| Providers | terraform:providers | List all namespaces/providers |
terraform:provider:<namespace>/<name> | Get details for a specific provider | |
| Provider Versions | terraform:provider:<namespace>/<name>/versions | List available versions for a provider |
| Provider Resources | terraform:provider:<namespace>/<name>/resources | List resources for a provider |
terraform:resource:<namespace>/<name>/<resource_name> | Get details for a specific resource type | |
| Provider Data Sources | terraform:provider:<namespace>/<name>/dataSources | List data sources for a provider |
terraform:dataSource:<namespace>/<name>/<data_source_name> | Get details for a specific data source | |
| Provider Functions | terraform:provider:<namespace>/<name>/functions | List functions for a provider |
terraform:function:<namespace>/<name>/<function_name> | Get details for a specific function |
The server also supports resources/templates/list to provide templates for creating:
terraform:providerterraform:resourceterraform:dataSource
Prompts
The following prompts are available for generating contextual responses:
| Prompt | Description | Required Arguments |
|---|---|---|
migrate-clouds | Generate Terraform code to migrate infrastructure between cloud providers | sourceCloud, targetCloud, terraformCode |
generate-resource-skeleton | Helps users quickly scaffold new Terraform resources with best practices | resourceType |
optimize-terraform-module | Provides actionable recommendations for improving Terraform code | terraformCode |
migrate-provider-version | Assists with provider version upgrades and breaking changes | providerName, currentVersion, targetVersion, terraformCode (optional) |
analyze-workspace-runs | Analyzes recent run failures and provides troubleshooting guidance for Terraform Cloud workspaces | workspaceId, runsToAnalyze (optional, default: 5) |
Known Issues with Prompts
Note: There is a known issue with the getPrompt functionality that can cause server crashes. The server properly registers prompts and can list them, but direct requests using the getPrompt method may cause connectivity issues. This is being investigated and may be related to SDK compatibility or implementation details. Until resolved, use listPrompts to see available prompts but avoid direct getPrompt calls.
Running the Server
The server runs using stdio transport for MCP communication:
npm install
npm start
Configuration with Environment Variables
The server can be configured using environment variables:
| Environment Variable | Description | Default Value |
|---|---|---|
TERRAFORM_REGISTRY_URL | Base URL for Terraform Registry API | https://registry.terraform.io |
DEFAULT_PROVIDER_NAMESPACE | Default namespace for providers | hashicorp |
LOG_LEVEL | Logging level (error, warn, info, debug) | info |
REQUEST_TIMEOUT_MS | Timeout for API requests in milliseconds | 10000 |
RATE_LIMIT_ENABLED | Enable rate limiting for API requests | false |
RATE_LIMIT_REQUESTS | Number of requests allowed in time window | 60 |
RATE_LIMIT_WINDOW_MS | Time window for rate limiting in milliseconds | 60000 |
TFC_TOKEN | Terraform Cloud API token for private registry access (optional) |
Example usage with environment variables:
# Set environment variables
export LOG_LEVEL="debug"
export REQUEST_TIMEOUT_MS="15000"
export TFC_TOKEN="your-terraform-cloud-token"
# Run the server
npm start
Testing
See the TESTS.md file for information about testing this project.
FAQ
- What is the Terraform Registry MCP server?
- Terraform Registry is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Terraform Registry?
- This profile displays 53 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.7 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Extended AI Capabilities
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Context Enhancement
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Workflow Automation
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Implementation Guide▌
Prerequisites
- ›Claude Desktop 0.7.0+ or Cursor IDE with MCP support
- ›Basic understanding of MCP architecture and capabilities
- ›Access credentials for integrated services (if required)
- ›Willingness to experiment and iterate on configuration
Time Estimate
15-60 minutes depending on server complexity
Installation Steps
- 1.Install MCP server: npm install -g [package-name] or via GitHub
- 2.Add server configuration to ~/.claude/mcp.json
- 3.Provide required credentials and configuration
- 4.Restart Claude Desktop to load new server
- 5.Test basic functionality with simple prompts
- 6.Explore capabilities and experiment with use cases
- 7.Document successful patterns for reuse
Troubleshooting
- ⚠MCP server not loading: Check config syntax, verify installation
- ⚠Connection errors: Check network, firewall, credentials
- ⚠Feature not working: Read server docs, check required parameters
- ⚠Performance issues: Monitor resource usage, check for network latency
- ⚠Conflicts with other servers: Check port assignments, namespace collisions
Best Practices▌
✓ Do
- +Read server documentation thoroughly before setup
- +Start with simple use cases to validate functionality
- +Test in non-production environment first
- +Monitor resource usage and performance
- +Keep servers updated for bug fixes and new features
- +Document configuration for team members
- +Use environment variables for sensitive configuration
✗ Don't
- −Don't grant overly permissive access to MCP servers
- −Don't skip reading security considerations in docs
- −Don't expose sensitive data without proper controls
- −Don't run untrusted MCP servers without code review
- −Don't ignore error messages—investigate root cause
💡 Pro Tips
- ★Combine multiple MCP servers for powerful workflows
- ★Create custom MCP servers for your specific needs
- ★Share successful configurations with team
- ★Use MCP inspector for debugging
- ★Join MCP community for tips and troubleshooting
Technical Details▌
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
- Model Context Protocol (MCP)
- JSON-RPC 2.0
- stdio or HTTP transport
Compatibility
- Claude Desktop
- Cursor IDE
- Custom MCP clients
When to Use This▌
✓ Use When
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid When
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
Integration▌
- →Tool composition: Chain multiple MCP tools in workflows
- →Context augmentation: Provide AI with relevant external data
- →Action delegation: Let AI execute tasks on external systems
- →Bidirectional sync: Keep AI context and external systems in sync
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.7★★★★★53 reviews- ★★★★★Shikha Mishra· Dec 16, 2024
Terraform Registry is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
- ★★★★★Emma Jackson· Dec 16, 2024
Terraform Registry has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Emma Abbas· Dec 8, 2024
Terraform Registry is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
- ★★★★★Alexander Singh· Nov 27, 2024
Useful MCP listing: Terraform Registry is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Yash Thakker· Nov 19, 2024
I recommend Terraform Registry for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Rahul Santra· Nov 7, 2024
Useful MCP listing: Terraform Registry is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Zara Tandon· Nov 7, 2024
We evaluated Terraform Registry against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Pratham Ware· Oct 26, 2024
Terraform Registry reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Tariq Thompson· Oct 26, 2024
Terraform Registry is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Alexander Jain· Oct 18, 2024
Terraform Registry reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
showing 1-10 of 53