MCP server wrapper for Terraform — access Terraform provider documentation, resource schemas, and module registry data.
Terraform by HashiCorp is the industry-standard infrastructure-as-code tool for provisioning and managing cloud and on-premises resources across 3,000+ providers. This MCP server exposes the Terraform provider registry and documentation — letting AI assistants look up resource schemas, find module examples, explore provider argument references, and assist in writing and debugging .tf configuration files. See hashicorp/terraform-mcp-server for full documentation.
No API keys required — the server queries the public Terraform Registry and runs locally inside the Docker container.
Summary. MCP server wrapper for Terraform — access Terraform provider documentation, resource schemas, and module registry data.
| Tool | Description |
|---|---|
providerDetails | Providerdetails |
resourceUsage | Resourceusage |
moduleSearch | Modulesearch |
listDataSources | Listdatasources |
resourceArgumentDetails | Resourceargumentdetails |
moduleDetails | Moduledetails |
functionDetails | Functiondetails |
providerGuides | Providerguides |
policySearch | Policysearch |
policyDetails | Policydetails |
Here are example prompts you can use with Claude (or any MCP client) when this tool is connected:
docker-compose up -d
docker run -i --rm hackerdogs/terraform-mcp:latest
docker run -d -p 8670:8670 \
-e MCP_TRANSPORT=streamable-http \
-e MCP_PORT=8670 \
hackerdogs/terraform-mcp:latest
Add to your Claude Desktop or Cursor MCP config:
{
"mcpServers": {
"terraform-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"MCP_TRANSPORT",
"hackerdogs/terraform-mcp:latest"
],
"env": {
"MCP_TRANSPORT": "stdio"
}
}
}
}
First, start the server using Docker Compose or docker run with HTTP mode (see Deploy above), then point your MCP client at the running server:
{
"mcpServers": {
"terraform-mcp": {
"url": "http://localhost:8670/mcp"
}
}
}
When to use HTTP mode: HTTP mode is ideal for shared/remote deployments, multi-user setups, and Hackerdogs scheduled prompts. The server runs as a long-lived process and accepts connections from multiple MCP clients concurrently.
| Variable | Default | Description |
|---|---|---|
MCP_TRANSPORT | stdio | Transport mode: stdio or streamable-http |
MCP_PORT | 8670 | HTTP port (only used with streamable-http) |
The fastest way to get started is through Hackerdogs:
Give it a couple of minutes to go live. Then start querying by asking Hackerdogs to use the tool explicitly. If you don't specify, Hackerdogs will automatically choose the best tool for the job.
Want to contribute or chat with the team? Join our Discord.
docker build -t hackerdogs/terraform-mcp:latest .
./test.sh
1. Start the server in HTTP mode:
docker run -d --rm --name terraform-mcp-test -p 8670:8670 \
-e MCP_TRANSPORT=streamable-http \
hackerdogs/terraform-mcp:latest
2. Initialize the MCP session:
SESSION_ID=$(curl -s -D - -X POST http://localhost:8670/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"0.1"}}}' \
2>&1 | grep -i mcp-session-id | awk '{print $2}' | tr -d '\r\n')
curl -s -X POST http://localhost:8670/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "mcp-session-id: $SESSION_ID" \
-d '{"jsonrpc":"2.0","method":"notifications/initialized"}'
3. List available tools:
curl -s -X POST http://localhost:8670/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "mcp-session-id: $SESSION_ID" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}'
4. Clean up:
docker stop terraform-mcp-test
Content type
Image
Digest
sha256:fe7c08fec…
Size
102.7 MB
Last updated
3 months ago
docker pull hackerdogs/terraform-mcp