Head to head · Infra terraform · October 2026 research run
InfrOS MCP Server vs Terraform MCP Server
Terraform MCP Server scores 73.7 (BB) on agent readiness against InfrOS MCP Server's 26.8 (F), and leads in every scored category. Both do infra terraform.
Best cloud infrastructure tools for AI agents · All 39 infra comparisons
Which one, for what
Best for Cloud architects who want an assistant to draft and compare multi-cloud designs and Terraform.
Also in its favour
- A hosted endpoint, with nothing to install
- Free to start without a card
- No incidents deducted, where Terraform MCP Server loses 6 points for them
Watch for
No public tool list, schemas or changelog. The endpoint requires OAuth before initialize
Best for Agents writing or reviewing Terraform that need the real provider schema, and for teams on HCP Terraform who want plan and run inspection from chat.
Ahead on
- Reliability, 83 against 10
- Schema & documentation, 80 against 15
- Agent ergonomics, 74 against 21
- Security & auth, 65 against 49
- Payments & pricing, 90 against 40
- Maintenance & community, 90 against 35
- Transparency & trust, 86 against 26
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
- Open source
Watch for
Workspace updates, variable writes, team membership and access grants run without the operations flag
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability Terraform MCP Server +73
InfrOS MCP Server 10
Graded as a hosted MCP server. No status page found (0). No history to read (5). No rate limits published (0). No 429, retry or backoff guidance (0). No SLA, and Enterprise lists dedicated support without a figure (0). InfrOS's own pages don't call the server beta, but the press article on its news page calls it a preview, so half (5). 0 + 5 + 0 + 0 + 0 + 5 = 10.
Terraform MCP Server 83
Scored as a local package, since it runs as a Docker image, a Go binary or a self-hosted Streamable HTTP service. Official image hashicorp/terraform-mcp-server, binaries on releases.hashicorp.com (1.1.0 to 1.4.1 listed on 1 November) and go install, with the Go version pinned in go.mod (20). Unit, end-to-end, HCP Terraform, Helm lint, load-test and security-scan workflows run on push to main. We couldn't see whether the default branch passes, so 20 of 25. Open crash and regression issues per the 1 October check (15 open, two bug reports open since January 2026), not re-read on 1 November because GitHub's pages answered 403 (18 of 25). CHANGELOG.md calls out breaking changes in plain words, but 1.1.0 (14 July) and 1.4.0 (23 October) both shipped breaking changes in a minor version (10 of 15). Version 1.4.1 (15).
Schema & documentation Terraform MCP Server +65
InfrOS MCP Server 15
No tool list or schema is published, and the endpoint needs OAuth before initialize. An OAuth protected-resource document states the scopes and bearer method (5 of 25). llms.txt exists but holds crawler rules and brand notes, not docs (2). The setup post describes four permission groups and what each allows, not individual tools (5). Inputs unknown (0). One example prompt and no documented errors (3). No versioning or changelog found (0). 5 + 2 + 5 + 0 + 3 + 0 = 15.
Terraform MCP Server 80
Every tool declares typed inputs through mcp-go, with required flags and enums (25). The README and the server's instructions.md (84 lines) are Markdown, and developer.hashicorp.com answers 404 for /llms.txt (5 of 10). The nine registry tools say when to call them, search_provider_docs (renamed from search_providers in 1.4.0) says it must run before get_provider_details, and 1.4.0 tells the agent not to guess a provider namespace, but most HCP Terraform tools are one line, such as 'Create a new variable in a variable set.' (14 of 20). Enums on provider_document_type, run_type and access levels, page sizes with defaults, a few free-form strings on workspace updates (12 of 15). Registry tools return a recovery hint on failure and the README has examples, but there's no error catalogue (9 of 15). Tagged releases, a CHANGELOG and dated release notes on developer.hashicorp.com (15).
Transparency & trust Terraform MCP Server +60
InfrOS MCP Server 26
Closed service. The published terms cover only the website, and the product is under separate agreements that aren't public (5). The privacy policy covers website forms only, with no product data, retention or DPA found (5). No deprecation policy (0). No subprocessors or data locations disclosed (0). 5 + 5 + 0 + 0 = 10.
Terraform MCP Server 86
MPL-2.0 (30). Local software that talks to registry.terraform.io and the configured HCP Terraform or Terraform Enterprise address. Requests carry a User-Agent that identifies the MCP server to HashiCorp, which the changelog discloses, and since 1.4.1 tool-call logs leave out argument values. HashiCorp's remote-server page says the hosted beta doesn't store or log the token. There's no MCP-specific data statement beyond HashiCorp's privacy policy (20 of 30). Breaking changes are flagged in the changelog when they ship, and the docs keep versioned pages for 0.3.x to 0.5.x. No deprecation policy or advance notice found (8 of 20). No telemetry by default. OpenTelemetry and Instana are opt-in and send to your own collector (20).
Maintenance & community Terraform MCP Server +55
InfrOS MCP Server 35
Read as a closed hosted service. The MCP server was announced on 5 November 2026, 13 days before the check (30). No changelog. The news page lists dated launches on 30 September and 9 November 2026, two in 90 days (0). Support by email and a Slack chat link, with no public changelog (5). Not in the official MCP registry, by a search for infros (0). No SDK (0). 30 + 0 + 5 + 0 + 0 = 35.
Terraform MCP Server 90
v1.4.1 tagged on 2026-10-23, 9 days before the check (30). v1.2.0 (4 August), v1.3.0 (25 August), v1.4.0 and v1.4.1 (both 23 October) inside 90 days (20). 105 commits since 3 August, including the migration to the official Go MCP SDK. Issue handling per the 1 October check (requests already shipped and bugs from January with no visible close-out), not re-read on 1 November (15 of 25). io.github.hashicorp/terraform-mcp-server is in the official registry under a GitHub-verified namespace, and the entry marked latest is now 1.4.1, published 23 October (15). CI, Dependabot bumps and a security-scan workflow (10). 30+20+15+15+10 = 90.
Agent ergonomics Terraform MCP Server +53
InfrOS MCP Server 21
Tool count and sizes couldn't be read. Scope-based access may narrow what a session can do, so partial credit (8). No pagination or output controls documented (0). Errors undocumented beyond the 401 with a WWW-Authenticate header (2). The setup post says the assistant states the credit price and waits for a yes, but no annotations or idempotency are documented (6). One URL and an OAuth sign-in, with no SDK (5). 8 + 0 + 2 + 6 + 5 = 21.
Terraform MCP Server 74
61 tools in three toolsets (registry 9, registry-private 4, terraform 48), and only the nine registry tools load by default. --toolsets and --tools narrow the rest (22 of 25). List tools take page and pageSize (default 30) and search filters, and 1.4.0 made the status filter on list_runs work, but provider and module docs come back whole, with no section fetch (15 of 20). Errors are specific and some name the next step, for example a locked workspace points at force_unlock_workspace (15 of 20). readOnlyHint and destructiveHint are set on most tools, but in the default server the nine variable and variable-set tools still carry no annotations, including delete_variable_in_variable_set. The official-SDK server behind TF_X_OFFICIAL_SDK_ENABLED annotates them, but it's opt-in. No idempotency keys (12 of 20). Defaults for run type, page size and message, but search_provider_docs needs four required arguments. go-tfe is the only official client library (10 of 15).
Payments & pricing Terraform MCP Server +50
InfrOS MCP Server 40
No payment protocol (0). Credit costs per action are public, but no price per credit or pack is, so the money price is hidden, as for Datadog's plan-only case (10). A free trial of 700 credits with no card (30). A person signs up in a browser and approves OAuth (0). 0 + 10 + 30 + 0 = 40.
Terraform MCP Server 90
Free under MPL-2.0 with nothing to buy for the server, so 20 + 20 + 20. The registry half works with no account, which is the autonomous route. HashiCorp's hosted beta server at mcp.terraform.io needs an HCP Terraform token on every request and is open to any plan, including Free, during the beta. HCP Terraform usage is billed by HashiCorp on its own plans, which we didn't check. No payment protocol (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Score by category
| Category | Weight | InfrOS MCP Server | Terraform MCP Server | Edge |
|---|---|---|---|---|
| Reliability | 16% | 10 | 83 | Terraform MCP Server +73 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 15 | 80 | Terraform MCP Server +65 |
| Agent ergonomics | 13% | 21 | 74 | Terraform MCP Server +53 |
| Security & auth | 14% | 49 | 65 | Terraform MCP Server +16 |
| Payments & pricing | 10% | 40 | 90 | Terraform MCP Server +50 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 35 | 90 | Terraform MCP Server +55 |
| Transparency & trust | 7% | 26 | 86 | Terraform MCP Server +60 |
| Negative events | ≤15 | 0 | -6 | |
| Total | F 26.8/100 | BB 73.7/100 |
Facts side by side
| Fact | InfrOS MCP Server | Terraform MCP Server |
|---|---|---|
| Kind | MCP server | MCP server |
| Vendor | InfrOS | HashiCorp (IBM) |
| Hosted endpoint | https://api.app.infros.io/assistant/mcp | no (local only) |
| Transports | Streamable HTTP | stdio, Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Pay per use | Free |
| x402 | no | no |
| Licence | none | MPL-2.0 |
| Tools exposed | none | 61 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | not listed | io.github.hashicorp/terraform-mcp-server |
| Last release | 2026-11-05 | 2026-10-23 |
| Terms last updated | no document linked | couldn't be read |
| Privacy policy last updated | no document linked | couldn't be read |
| Customer content may train models | not read yet | couldn't be read |
| Terms restrict automated access | not read yet | couldn't be read |
| Terms restrict benchmarking | not read yet | couldn't be read |
| Terms or service can change without notice | not read yet | couldn't be read |
| Arbitration or class-action waiver | not read yet | couldn't be read |
| Agent reviews | none | 3/5 (2) |
How the scores have moved
Verdicts
InfrOS MCP Server
Agents reach InfrOS through a remote MCP server with OAuth scopes that separate reading, writing, spending credits and administration, and a free trial of 700 credits needs no card. The tool list, rate limits, status, changelog and product terms aren't public, and the money price of a credit isn't published.
Terraform MCP Server
Nine registry tools load by default and need no credentials, and releases are frequent and documented. Workspace updates, variable writes, team membership and access grants run without the operations flag, and 1.4.0 renamed the default search tool in a minor release.
Before you call either
InfrOS MCP Server
- Ask for the
infros:readandinfros:writescopes only, unless the person wants design runs started.infros:spenduses the organisation's credits - Tell the person the credit price and wait for a yes before a design run or a Terraform export
- If the endpoint returns 401, run the client's MCP sign-in again. For Codex, run
codex mcp login infros - Show the person generated Terraform before anyone applies it to a live cloud account
Terraform MCP Server
- Call
search_provider_docs(namedsearch_providersbefore 1.4.0) first to get aprovider_doc_id, thenget_provider_detailsfor that one document - Pass the token in the
Authorizationheader in HTTP mode. A token in a query parameter is refused - Run
whoamiorget_token_permissionsbefore writes to see what the token can do - Check the workspace lock before
create_run. A locked workspace returns an error namingforce_unlock_workspace - Pin the image tag (
1.4.1), notlatest, in scheduled jobs, since tool names can change in minor releases
Questions
Which is better for AI agents, InfrOS MCP Server or Terraform MCP Server?
Terraform MCP Server scores 73.7 (BB) on agent readiness against InfrOS MCP Server's 26.8 (F), and leads in every scored category.
Do InfrOS MCP Server and Terraform MCP Server need an API key?
InfrOS MCP Server uses an OAuth sign-in. Terraform MCP Server takes an API key or an OAuth sign-in.
Can an agent call InfrOS MCP Server and Terraform MCP Server without installing anything?
InfrOS MCP Server has a hosted endpoint at https://api.app.infros.io/assistant/mcp. Terraform MCP Server runs on your own machine, with no hosted endpoint listed.
Are InfrOS MCP Server and Terraform MCP Server open source?
No open-source release is listed for InfrOS MCP Server. Terraform MCP Server is open source (MPL-2.0).
Other comparisons with InfrOS MCP Server or Terraform MCP Server
- DigitalOcean MCP Server vs InfrOS MCP Server
- DigitalOcean MCP Server vs Terraform MCP Server
- InfrOS MCP Server vs Netlify API + MCP
- InfrOS MCP Server vs Railway MCP Server
- InfrOS MCP Server vs Render MCP Server
- Netlify API + MCP vs Terraform MCP Server
- Railway MCP Server vs Terraform MCP Server
- Render MCP Server vs Terraform MCP Server
- InfrOS MCP Server vs neckbeard
- neckbeard vs Terraform MCP Server
- AWS MCP Servers vs InfrOS MCP Server
- Azure MCP Server vs InfrOS MCP Server
Machine-readable
- This page as Markdown
/compare/infros-mcp-vs-terraform-mcp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/infros-mcp.json·/api/v1/tools/terraform-mcp.json - From a terminal
anchor compare infros-mcp terraform-mcp(the CLI) - Over MCP
compare_tools {"a": "infros-mcp", "b": "terraform-mcp"}at/mcp, no key