terraform-mcp-server
The Terraform MCP Server provides seamless integration with Terraform ecosystem, enabling advanced automation and interaction capabilities for Infrastructure as Code (IaC) development.
Runssource: GitHubGoMPL-2.0commit d8fd44d71426
Go, MPL-2.0 licensed.
terraform-mcp-server runs. An Argusic agent installed it in 9 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
terraform-mcp-server v1.3.0 builds and runs: binary reports version, responds to MCP initialize in stdio mode, and answers HTTP 200 on /health in streamable-http mode
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Go 1.26.6 not installed in container2 minutes
- e2e tests require Docker (not available in container)
- Install time
- 9 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- go test ./... (excluding e2e), 19 packages passed, 0 failures; go build produced bin/terraform-mcp-server; ./bin/terraform-mcp-server --version returned 'Terraform MCP Server Version: 1.3.0'; stdio mode initialized successfully via JSON-RPC; streamable-http mode health endpoint returned HTTP 200
- Model tokens used
- 45,948
- Exact commit tested
- d8fd44d71426
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
ok github.com/hashicorp/terraform-mcp-server/pkg/toolsets 0.158s ok github.com/hashicorp/terraform-mcp-server/pkg/utils 0.076s ok github.com/hashicorp/terraform-mcp-server/test/terraform 0.084s Build exists: YES Binary version: Terraform MCP Server Version: 1.3.0 Stdio mode test: initialize OK, server: terraform-mcp-server 1.3.0 Everything works. Here is the final report: tokens used 45,948 Everything works. Here is the final report:
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MPL-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 9 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.
Of the 6 Go projects Argusic has installed and timed, terraform-mcp-server was the 5th fastest to reach a running state, and 6 of 6 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 9 minutes after the clone.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.05 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.04 |
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/terraform-mcp-server)Questions
- Does terraform-mcp-server run?
- Yes. terraform-mcp-server runs. Argusic installed and launched it on a clean machine in 9 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test terraform-mcp-server?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d8fd44d71426. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test terraform-mcp-server?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does terraform-mcp-server take to install?
- 9 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does terraform-mcp-server need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing terraform-mcp-server?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does terraform-mcp-server compare with the alternatives?
- Of the 6 Go projects Argusic has installed and timed, terraform-mcp-server was the 5th fastest to reach a running state, and 6 of 6 reached one at all.
- Where is the evidence for terraform-mcp-server?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.