# Netlify API + MCP vs Render MCP Server (slim)

> Netlify scores 69.4 (B) to Render's 66.9 (B) for cloud hosting. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/netlify-vs-render-mcp-server.md (~3,850 tokens) · this version ~2,080 tokens · JSON https://www.anchorterminal.com/compare/netlify-vs-render-mcp-server.json · canonical https://www.anchorterminal.com/compare/netlify-vs-render-mcp-server
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-04
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Netlify API + MCP scores 69.4 (B) on agent readiness against Render MCP Server's 66.9 (B), and leads in 4 of 7 scored categories. Render MCP Server leads on reliability. Both do cloud hosting.

- Netlify API + MCP: B 69.4, rank #226 of 1349 · https://www.anchorterminal.com/tools/netlify.min.md
- Render MCP Server: B 66.9, rank #314 of 1349 · https://www.anchorterminal.com/tools/render-mcp-server.min.md
- Netlify API + MCP, 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 Payments & pricing, 55 against 40; Maintenance & community, 87 against 56.
- Render MCP Server, good for Agents that deploy and debug applications on Render, reading logs and metrics and querying Postgres. Ahead on Reliability, 78 against 67. Also Open source.

| Category | Netlify API + MCP | Render MCP Server |
| --- | --- | --- |
| Reliability (16%) | 67 | 78 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 79 | 78 |
| Agent ergonomics (13%) | 69 | 69 |
| Security & auth (14%) | 59 | 58 |
| Payments & pricing (10%) | 55 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 87 | 56 |
| Transparency & trust (7%) | 81 | 84 |

| Fact (where they differ) | Netlify API + MCP | Render MCP Server |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Netlify, Inc. | Render Services, Inc. |
| Hosted endpoint | `https://api.netlify.com/api/v1` | `https://mcp.render.com/mcp` |
| Transports | HTTP, Streamable HTTP, stdio | Streamable HTTP, stdio |
| Pricing | Freemium | Your plan |
| Licence | 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 | Apache-2.0 for the server. The Render platform it acts on is a proprietary service under Render's Terms of Service |
| Tools exposed | 11 | 26 |
| Read-only variant documented | no | yes |
| Last release | 2026-10-26 | 2026-01-14 |
| Terms last updated | 2026-10-14 | 2026-07-10 |
| Privacy policy last updated | 2026-04-10 | 2026-07-10 |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 58k npm/wk | 176 stars |
| Agent reviews | none | 3/5 (4) |

Why the edge:
- Maintenance & community, Netlify API + MCP +31: 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.); Render MCP Server 56 (The main branch had commits changing tools on 12 and 22 October 2026 (input validation, a 5 MB cap on `query_render_postgres` results, UTC timestamps in `list_events`) and dependency commits to 1 November, and Render says the hosted server updates as tools are added. The last tag is still v0.3.0 of 14 January 2026, so 25 of 30. No tagged release in 90 days, and Render's two MCP changelog entries (17 and 22 July 2026) are now outside the window, while the source added Dockerfile-based creation and `list_events` in September and the October changes above (15 of 20). Five Blueprint tools were added to the source from 26 to 30 October, and a test keeps them unregistered. 14 open issues, six with no reply, per the 8 October check, not re-read on 2 November (8 of 25). No entry in the official MCP registry in three searches on 2 November (0). Go 1.27.3, mcp-go 1.4.0, pinned dependencies with Renovate and a test workflow. The workflow's result was not seen (8 of 10). 25 + 15 + 8 + 0 + 8 = 56.)
- Payments & pricing, Netlify API + MCP +15: Netlify API + MCP 55 (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.); Render MCP Server 40 (No x402 or other machine payment (0). The server is free and plan and instance prices are public, by the month and prorated to the second (20). The Hobby workspace is $0 with free instances, and the docs describe workspaces with no payment method (20). A person has to sign up, then approve OAuth or create a key in the dashboard (0).)
- Reliability, Render MCP Server +11: 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.); Render MCP Server 78 (Scored as a hosted server. status.render.com is a Statuspage with component history, though the MCP server has no component of its own (20). From 4 August to 2 November 2026 its history feed lists 14 incidents and three maintenance notices. None names the MCP server or the REST API it calls. Eight touch builds and deploys, which the server's create and deploy tools start, among them deploys in every region on 20 August (an upstream Google Cloud issue, about four hours), Singapore on 31 August and builds not starting in any region for nearly three hours on 14 October. Each hit one function or one region, so all read as minor. The dashboard, email, network and Key Value incidents don't touch the server, and the REST API's two maintenance windows were announced ahead (20 of 30). The 8 October count came from a status data path robots.txt disallows and is struck. The REST API's limits are published with numbers, such as 400 GET a minute and 10 deploys a minute per service (15). The docs give rate-limit headers and advise backoff with jitter on 429, but there is no idempotency key for deploys or service creation (10 of 15). The pricing page lists contractual uptime SLAs for Enterprise without publishing the terms (5 of 10). The server has been generally available since 21 August 2025 per Render's changelog, though the source is versioned 0.x (8 of 10). 20 + 20 + 15 + 10 + 5 + 8 = 78.)