# InfrOS MCP Server vs Netlify API + MCP

> Netlify scores 72.9 (BB) to InfrOS's 26.8 (F) for cloud hosting. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/infros-mcp-vs-netlify
- Markdown: https://www.anchorterminal.com/compare/infros-mcp-vs-netlify.md (~4,400 tokens)
- Slim: https://www.anchorterminal.com/compare/infros-mcp-vs-netlify.min.md (~1,080 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/infros-mcp-vs-netlify.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-18

Netlify API + MCP scores 72.9 (BB) on agent readiness against InfrOS MCP Server's 26.8 (F), and leads in every scored category. Both do cloud hosting.

- InfrOS MCP Server: grade F, 26.8/100, rank #1478 of 1557. Markdown https://www.anchorterminal.com/tools/infros-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/infros-mcp.json
- Netlify API + MCP: grade BB, 72.9/100, rank #200 of 1557. Markdown https://www.anchorterminal.com/tools/netlify.md · JSON https://www.anchorterminal.com/api/v1/tools/netlify.json
- Best cloud infrastructure tools for AI agents: https://www.anchorterminal.com/best/infrastructure/index.md
- All 39 infra comparisons: https://www.anchorterminal.com/compare/infrastructure/index.md

## Which one, for what

### InfrOS MCP Server (F)

Good for: Cloud architects who want an assistant to draft and compare multi-cloud designs and Terraform.

Also in its favour:
- Free to start without a card

Watch for: No public tool list, schemas or changelog. The endpoint requires OAuth before `initialize`

### Netlify API + MCP (BB)

Good for: An agent that builds and deploys web projects, sets environment variables and reads forms or logs on a team's Netlify account, including with no account through anonymous deploys.

Ahead on:
- Reliability, 67 against 10
- Schema & documentation, 79 against 15
- Agent ergonomics, 69 against 21
- Security & auth, 59 against 49
- Payments & pricing, 83 against 40
- Maintenance & community, 87 against 35
- Transparency & trust, 81 against 26

Also in its favour:
- Agent-ready, a grade of BB or better
- Runs on your own machine

Watch for: Personal access tokens and OAuth apps have no scopes, so a token reaches every team its owner belongs to


## Why the edge

### Schema & documentation: Netlify API + MCP +64

- 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.
- Netlify API + MCP (79): A public Swagger 2.0 spec, version 2.63.1, with 124 paths and 188 operations, and MCP tools typed through zod (25). llms.txt and a Markdown twin of every docs page, with agent skills in netlify/context-and-tools (10). Every spec operation has a summary, most one line, and the MCP tool descriptions say what to call first, as the deploy tool does for get-projects, but not when to leave an endpoint alone (14 of 20). 232 parameters with 9 enums; the MCP selector tools take an `operation` literal and a `params` object per operation inside one union, which is typed but nested (9 of 15). The API guide gives curl examples for sites and deploys, a shared `error` object of code and message is the default response, and 422, 404, 409 and 423 are declared on some operations, but the docs' error reference covers builds and domains rather than API codes (8 of 15). The spec carries a version, the API a /v1 path, Netlify a dated changelog, and the MCP server a dated CHANGELOG from release-please (13 of 15). 25 + 10 + 14 + 9 + 8 + 13 = 79.

### Reliability: Netlify API + MCP +57

- 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.
- Netlify API + MCP (67): Read with the hosted lines. Statuspage at netlifystatus.com with component history and an Atom feed (20). From 5 August to 3 November 2026 the feed lists 19 incidents and no maintenance. None names the API or the MCP server. Errors reaching hosted sites and the Netlify application for about 85 minutes on 21 September read as one major outage; errors on the edge network for 55 minutes on 5 October, CDN DNS errors for 34 minutes on 24 September, 6 minutes of 500s on 18 August, and build, Agent Runner, AI Gateway and log-delay incidents read as minor (10 of 30). Limits are published with numbers, about 500 requests a minute, 3 deploys a minute and 100 a day, with X-RateLimit headers (15). The docs say retrying a timed-out upload is safe and give the reset header, but no backoff guidance, no idempotency key for deploys or site creation, and 429 appears in the spec only on agent runner endpoints (7 of 15). A 99.99 per cent SLA is named for Enterprise on the pricing page, with its terms in order forms (5 of 10). The API is generally available (10). 20 + 10 + 15 + 7 + 5 + 10 = 67.

### Transparency & trust: Netlify API + MCP +55

- 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.
- Netlify API + MCP (81): The MCP server is ISC and the CLI MIT, on a closed platform with clear terms naming Netlify, Inc. (25 of 30). A downloadable DPA and subprocessor list, but no retention periods in the privacy statement, which also says content trains AI models only with an opt-in in one section and never in another (18 of 30). Dated deprecation notices in the changelog (Netlify Identity 28 February 2025, Node 18 and 20 build plugins 21 May 2026), no written policy, and the enterprise agreement lets beta services end at any time (12 of 20). Subprocessors named with countries, all US, with CSV, PDF and RSS, and Data Privacy Framework participation (18 of 20). 25 + 18 + 12 + 18 = 73.

### Maintenance & community: Netlify API + MCP +52

- 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.
- Netlify API + MCP (87): @netlify/mcp 1.21.0 tagged on 26 October 2026 (changelog 23 October), a commit on 28 October, the spec at 2.63.1 and changelog entries to 26 October (30). Six MCP tags between 25 September and 26 October 2026 (20). Issue and pull request responsiveness could not be read (github.com refuses our reader and the API answered empty), while the changelog, the answers.netlify.com forum, Discord and a support hub exist and the MCP changelog cites numbered pull requests (12 of 25). Current official SDKs, a Go client, a JS client and netlify-cli 27.16.2, though the server card names com.netlify/mcp and no such entry is in the official MCP registry (15). CI runs typecheck, build and 31 tests on pinned actions, releases through release-please with npm provenance, and the server runs on @modelcontextprotocol/server 2.2.0 (10). 30 + 20 + 12 + 15 + 10 = 87.

### Agent ergonomics: Netlify API + MCP +48

- 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.
- Netlify API + MCP (69): Lists are sized with `per_page` up to 100 and there is no field selection. The hosted MCP server registers about 11 tools by default, a reader and an updater selector per domain plus coding context and design import, and lists all 25 operations one by one only for OpenAI clients, so the context cost is low either way (18 of 25). `page` and `per_page` with a `Link` header, few filters, and MCP pagination bounds enforced since v1.19.0 (15 of 20). Errors return a code and message; the MCP server answers a bad selector with text telling the agent to pick an operation again (12 of 20). No idempotency key for deploys or sites, though timed-out uploads are safe to retry; every MCP tool declares readOnly, destructive, idempotent and openWorld hints since v1.18.0, with project renames marked destructive (12 of 20). Few required parameters, a Go client, a JS client and the CLI (12 of 15). 18 + 15 + 12 + 12 + 12 = 69.

### Payments & pricing: Netlify API + MCP +43

- 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.
- Netlify API + MCP (83): No x402, MPP or L402 (0). Plan prices and per-unit credit prices (deploys, bandwidth, compute, requests, credit packs) are public without a login (20). A Free plan with 300 credits a month and API deploys, and the docs do not say a card is needed (20). `netlify deploy --allow-anonymous` publishes a project and URL with no account, claimable within an hour, but the API, the MCP server and anything past that hour need a person to sign up and approve a token (15 of 20). 0 + 20 + 20 + 15 = 55. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 55 is 83.

## Score by category

| Category | Weight | InfrOS MCP Server | Netlify API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 10 | 67 | Netlify API + MCP +57 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 15 | 79 | Netlify API + MCP +64 |
| Agent ergonomics | 13% | 21 | 69 | Netlify API + MCP +48 |
| Security & auth | 14% | 49 | 59 | Netlify API + MCP +10 |
| Payments & pricing | 10% | 40 | 83 | Netlify API + MCP +43 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 35 | 87 | Netlify API + MCP +52 |
| Transparency & trust | 7% | 26 | 81 | Netlify API + MCP +55 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **26.8 · F** | **72.9 · BB** | |

## Facts side by side

| Fact | InfrOS MCP Server | Netlify API + MCP |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | InfrOS | Netlify, Inc. |
| Hosted endpoint | `https://api.app.infros.io/assistant/mcp` | `https://api.netlify.com/api/v1` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | none | ISC for the MCP server (@netlify/mcp) and MIT for the CLI (netlify-cli). The Netlify platform they act on is a proprietary service under Netlify's terms |
| Tools exposed | none | 11 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-05 | 2026-10-26 |
| Terms last updated | no document linked | 2026-10-14 |
| Privacy policy last updated | no document linked | 2026-04-10 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | none | 58k npm/wk |

## How the scores have moved

### InfrOS MCP Server

- -0.6 on 18 November 2026: correction

### Netlify API + MCP

- +3.5 on 13 November 2026 (B to BB): checklist

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

**Netlify API + MCP.** A public OpenAPI spec with 188 operations, documented rate limits, an anonymous deploy route and an MCP server released weekly through October 2026 with complete tool annotations. Personal access tokens and the OAuth flows carry no scopes, the hosted MCP enforces none on tool calls, and the status feed shows several site-serving incidents in the 90 days to 3 November.

## Before you call either

### InfrOS MCP Server

1. Ask for the `infros:read` and `infros:write` scopes only, unless the person wants design runs started. `infros:spend` uses the organisation's credits
2. Tell the person the credit price and wait for a yes before a design run or a Terraform export
3. If the endpoint returns 401, run the client's MCP sign-in again. For Codex, run `codex mcp login infros`
4. Show the person generated Terraform before anyone applies it to a live cloud account

### Netlify API + MCP

1. Send a `User-Agent` naming your app and `Authorization: Bearer $NETLIFY_AUTH_TOKEN`; watch X-RateLimit-Remaining and stop before 3 deploys a minute or 100 a day
2. Deploy with `netlify deploy --allow-anonymous` when the person has no account yet, and tell them to claim the project within an hour
3. Poll GET /api/v1/deploys/{deploy_id} until `state` is `ready`; a deploy call that runs over 30 seconds is cut off, so send large deploys with `"async": true`
4. Page lists with `page` and `per_page` (100 at most) and follow the `Link` header's `rel="next"`
5. Expect the hosted MCP's deploy tool to hand back a CLI command for the person to run; the local server deploys from the working directory itself

## Questions

### Which is better for AI agents, InfrOS MCP Server or Netlify API + MCP?

Netlify API + MCP scores 72.9 (BB) on agent readiness against InfrOS MCP Server's 26.8 (F), and leads in every scored category.

### Do InfrOS MCP Server and Netlify API + MCP need an API key?

InfrOS MCP Server uses an OAuth sign-in. Netlify API + MCP takes an API key or an OAuth sign-in.

### Can an agent call InfrOS MCP Server and Netlify API + MCP without installing anything?

Yes. InfrOS MCP Server has a hosted endpoint at https://api.app.infros.io/assistant/mcp and Netlify API + MCP at https://api.netlify.com/api/v1.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/infros-mcp-vs-netlify.json, and with the fewest tokens: https://www.anchorterminal.com/compare/infros-mcp-vs-netlify.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "infros-mcp", "b": "netlify"}`. From a terminal: `anchor compare infros-mcp netlify`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/infros-mcp.json and https://www.anchorterminal.com/api/v1/tools/netlify.json

## Other comparisons with InfrOS MCP Server or Netlify API + MCP

- [Azure MCP Server vs Netlify API + MCP](https://www.anchorterminal.com/compare/azure-mcp-vs-netlify.md)
- [DigitalOcean MCP Server vs InfrOS MCP Server](https://www.anchorterminal.com/compare/digitalocean-mcp-vs-infros-mcp.md)
- [DigitalOcean MCP Server vs Netlify API + MCP](https://www.anchorterminal.com/compare/digitalocean-mcp-vs-netlify.md)
- [InfrOS MCP Server vs Railway MCP Server](https://www.anchorterminal.com/compare/infros-mcp-vs-railway-mcp-server.md)
- [InfrOS MCP Server vs Render MCP Server](https://www.anchorterminal.com/compare/infros-mcp-vs-render-mcp-server.md)
- [neckbeard vs Netlify API + MCP](https://www.anchorterminal.com/compare/neckbeard-vs-netlify.md)
- [Netlify API + MCP vs Railway MCP Server](https://www.anchorterminal.com/compare/netlify-vs-railway-mcp-server.md)
- [Netlify API + MCP vs Render MCP Server](https://www.anchorterminal.com/compare/netlify-vs-render-mcp-server.md)
- [Netlify API + MCP vs Terraform MCP Server](https://www.anchorterminal.com/compare/netlify-vs-terraform-mcp.md)
- [Cloudflare CLI (cf) vs Netlify API + MCP](https://www.anchorterminal.com/compare/cloudflare-cli-vs-netlify.md)
- [InfrOS MCP Server vs neckbeard](https://www.anchorterminal.com/compare/infros-mcp-vs-neckbeard.md)
- [InfrOS MCP Server vs Terraform MCP Server](https://www.anchorterminal.com/compare/infros-mcp-vs-terraform-mcp.md)
- [AWS MCP Servers vs InfrOS MCP Server](https://www.anchorterminal.com/compare/aws-mcp-servers-vs-infros-mcp.md)
- [Azure MCP Server vs InfrOS MCP Server](https://www.anchorterminal.com/compare/azure-mcp-vs-infros-mcp.md)

---

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