Niches · Cloud & infrastructure
Write or review infrastructure as code
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
Code that validates against the current provider schema with versions pinned, and a plan summarised by resource and action (create, change, destroy) before any apply.
How agents ask for it: write the Terraform for this
, use the latest provider version
, review this plan before apply
, add Terraform tests
Does the job, with a limit 4
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| AWS MCP Servers C Amazon Web Services, Inc. | The IaC server validates CloudFormation with cfn-lint and cfn-guard and analyses failed deployments, but no change-set or plan summary by resource and action is documented; Terraform schemas are not served. source |
| Azure MCP Server BB Microsoft Corporation | Azure Terraform tools return azurerm and AzAPI arguments and Azure Verified Module versions and validate a plan file against policy, but no plan summary by resource and action is documented, and tools were renamed in prereleases. source |
| neckbeard B David Beale (individual, GitHub account bealesh) | Modules come from a catalogue pinned in a hash-verified lockfile, and validate runs static checks, a V1 plan stage and a V2 deploy stage, each reported; but no plan summary by resource and action is documented, and the project is pre-alpha. source |
| Terraform MCP Server BB HashiCorp, Inc. (an IBM Company) | get_latest_provider_version, get_provider_capabilities and get_provider_details give current schemas, and plans are separate from applies; but provider docs come back whole, and plan JSON is too large for context per acc-15. acc-14 recommends it for grounding. source |
Doesn't do this job 6
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Cloudflare CLI (cf) B Cloudflare, Inc. | Not an infrastructure-as-code tool; no provider schema, plan or apply step. source |
| Cloudflare MCP Servers BB Cloudflare, Inc. | No infrastructure-as-code, plan or provider schema tools. source |
| DigitalOcean MCP Server B DigitalOcean, LLC | No infrastructure-as-code, plan or provider schema tools. source |
| Netlify API + MCP BB Netlify, Inc. | No infrastructure-as-code tooling. source |
| Railway MCP Server C Railway Corporation | No infrastructure-as-code tooling. source |
| Render MCP Server B Render Services, Inc. | No infrastructure-as-code tooling in the MCP server. source |
What stops agents finishing
- plan JSON too large for the context
- provider docs returned whole with no section fetch
Around it
Before: infrastructure.cloud-docs. After: infrastructure.change-live-resources, code.open-pr.
Where this comes from
Weight 14 of 100 in Cloud & infrastructure: 5 of 32 accounts; two are feature requests on the Terraform MCP
The same as data: /api/v1/use-cases/infrastructure.write-iac.json, or the MCP tool get_use_case with id infrastructure.write-iac. Other jobs in this category: /api/v1/niches?category=infrastructure.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.