# Write or review infrastructure as code

> Write or review infrastructure as code: 0 companies fully do it, 4 with a limit, 12 carry the tag. Every listing in Cloud & infrastructure with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/infrastructure.write-iac/
- Markdown: https://www.anchorterminal.com/niches/infrastructure.write-iac/index.md (~950 tokens)
- Slim: https://www.anchorterminal.com/niches/infrastructure.write-iac/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/infrastructure.write-iac/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 4 | 12 | 14 | 5 |

## 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

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.

- **AWS MCP Servers (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.
- **Azure MCP Server (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.
- **neckbeard (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.
- **Terraform MCP Server (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.

- not this job: Cloudflare CLI (cf) (Cloudflare, Inc.): Not an infrastructure-as-code tool; no provider schema, plan or apply step.
- not this job: Cloudflare MCP Servers (Cloudflare, Inc.): No infrastructure-as-code, plan or provider schema tools.
- not this job: DigitalOcean MCP Server (DigitalOcean, LLC): No infrastructure-as-code, plan or provider schema tools.
- not this job: Netlify API + MCP (Netlify, Inc.): No infrastructure-as-code tooling.
- not this job: Railway MCP Server (Railway Corporation): No infrastructure-as-code tooling.
- not this job: Render MCP Server (Render Services, Inc.): No infrastructure-as-code tooling in the MCP server.

## 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

As data: https://www.anchorterminal.com/api/v1/use-cases/infrastructure.write-iac.json, or the MCP tool get_use_case with id infrastructure.write-iac. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
