Head to head · Cloud hosting · October 2026 research run

DigitalOcean MCP Server vs InfrOS MCP Server

DigitalOcean MCP Server scores 63.7 (B) on agent readiness against InfrOS MCP Server's 26.8 (F), and leads in every scored category. Both do cloud hosting.

Best cloud infrastructure tools for AI agents · All 39 infra comparisons

Which one, for what

DigitalOcean MCP Server B

Best for Agents that operate DigitalOcean accounts, across Droplets, App Platform, Kubernetes, databases, networking and the AI platform, with one endpoint a service.

Ahead on

  • Reliability, 67 against 10
  • Schema & documentation, 66 against 15
  • Agent ergonomics, 67 against 21
  • Security & auth, 67 against 49
  • Payments & pricing, 50 against 40
  • Maintenance & community, 70 against 35
  • Transparency & trust, 87 against 26

Also in its favour

  • Runs on your own machine
  • Open source

Watch for

No read-only mode on the server. A request for one has been open since 2 March 2026.

InfrOS MCP Server F

Best 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
  • No incidents deducted, where DigitalOcean MCP Server loses 3 points for them

Watch for

No public tool list, schemas or changelog. The endpoint requires OAuth before initialize

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.

Transparency & trust DigitalOcean MCP Server +61

DigitalOcean MCP Server 87

The server is MIT and the platform is closed with clear terms (28 of 30). A privacy policy and a DPA are published. The DPA promises deletion of personal data within 30 days of account deactivation. Nothing found says what the hosted MCP servers log, and the source can ship tool-call logs to a WebSocket endpoint when configured (20 of 30). The alert-policy-* tools carry a deprecation notice with no date, the terms promise as much notice of changes as is reasonably practicable, and the April 2026 service rename had no notice we found (9 of 20). Sub-processors are listed with locations on a page dated 10 June 2026, with 30 days to object to a new one (17 of 20). 28 + 20 + 9 + 17 = 74.

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.

Reliability DigitalOcean MCP Server +57

DigitalOcean MCP Server 67

Scored as a hosted server. status.digitalocean.com is a Statuspage with components by product and region, including the API, and no component for the MCP servers (20). The hosted servers call the public API, so the incident line is read from the API's incidents, as for other hosted MCP servers without a component of their own. history.rss, re-read on 3 November 2026, covers 3 August to 28 October. On 24 August from 17:14 UTC the incident says users saw "elevated 5xx errors for all API requests", with a recurrence from 22:27 until mitigation at 00:54 on 25 August, one major. Write operations failing across several services from 06:42 to 09:08 UTC on 6 August and create operations failing on 8 and 9 August hit a subset of requests and read as partial. Other entries are regional (MKC1 on 19 August, BLR1 on 3 October) or single products (10 of 30). The API's limits are published, 5,000 requests an hour and 250 a minute per token, per the 9 October check (15). The API docs describe rate-limit headers and retry-after on 429 and say PUT and DELETE are idempotent, with no idempotency key for creates, per the 9 October check (10 of 15). The terms refer to Service Level Agreements, which were not read (3 of 10). The MCP docs carry no beta label and the server is at 1.6.5, in an organisation named digitalocean-labs (9 of 10). 20 + 10 + 15 + 10 + 3 + 9 = 67.

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.

Schema & documentation DigitalOcean MCP Server +51

DigitalOcean MCP Server 66

Tools declare typed inputs through mcp-go, and about 300 also declare an output schema checked by a test. Two issues from February 2026 about array parameters without items are still open, and db-cluster-list reads per_page as a Go integer in the source, which a JSON number may not satisfy (22 of 25). llms.txt and a Markdown twin of every docs page (10). The median description is 48 characters and 156 of 365 are 40 or fewer, such as "Delete a droplet". A few say how to choose between arguments (9 of 20). Required fields and defaults are set, enums are rare, and argument names mix ID and Page with id and per_page (8 of 15). Each service has a README with arguments and example queries, generated into the docs. No list of error responses was found (9 of 15). Releases are semver tags. There is still no changelog file, and the 90-day release notes, re-read on 3 November 2026, have no entry for the MCP server (8 of 15). 22 + 10 + 9 + 8 + 9 + 8 = 66.

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.

Agent ergonomics DigitalOcean MCP Server +46

DigitalOcean MCP Server 67

About 467 tools in the source at v1.6.5 (up from about 377 at v1.2.0), but each of 24 hosted endpoints and the local --services flag load one service. Networking and Harness Runtime have 61 each, evaluations 47, Droplets 42, Insights 40 and databases 38, while 16 services have 15 or fewer (14 of 25). 62 tools took page or limit arguments at v1.2.0, and few take filters (13 of 20). Handlers name the missing argument and pass the API's message through, and the server separates errors a model can correct from those it cannot. No documented error codes (11 of 20). Every tool carries the four MCP hints and a risk label, enforced by a test, and 308 were marked idempotent at v1.2.0. Creates cannot be retried safely with a key (17 of 20). Few required parameters, with godo, pydo and doctl as official clients of the same API (12 of 15). 14 + 13 + 11 + 17 + 12 = 67.

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.

Maintenance & community DigitalOcean MCP Server +35

DigitalOcean MCP Server 70

v1.6.5 was tagged on 2 November 2026, the version in the npm wrapper's package.json (30). 18 tags from v1.0.68 (10 August) to v1.6.5 in the 90 days from 5 August (20). 256 commits since 5 August. Eight open issues and 23 open pull requests, with the credential issue of 26 May 2026 unanswered by a maintainer and the read-only request of 2 March 2026 open, per the 9 October check, not re-read on 3 November (12 of 25). The official MCP registry, searched again on 3 November, returns one third-party server for digitalocean and none from DigitalOcean (0). Dependabot runs weekly, and CI lints, checks formatting and runs tests with the race detector on Linux and macOS. The workflow's result was not seen (8 of 10). 30 + 20 + 12 + 0 + 8 = 70.

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.

Security & auth DigitalOcean MCP Server +18

DigitalOcean MCP Server 67

OAuth with short-lived tokens, or a personal access token with an expiry and custom scopes from about 170, revocable in the control panel. The OAuth challenge names only read and write, and the metadata allows the bearer header only (28 of 30). A Read Only token or custom scopes limit what any tool can do. The server still has no read-only mode at v1.6.5 (an issue requesting one was open from 2 March 2026, per the 9 October check), and only the custom model delete tool asks for a confirmation argument (13 of 20). App logs, function results and documentation pages are untrusted content. The README links a third-party briefing on MCP risks and gives no mitigation guidance (3 of 15). The tokens page shows when a token was last used. No audit log of MCP calls was found (4 of 15). Valid security.txt, a bug bounty on Intigriti, SOC 2 Type II and SOC 3, and CSA STAR Level 1. The repository has no SECURITY.md file. The certification page and security.txt (expires 5 April 2028) were re-read for the Spaces listing on 2 November 2026 (19 of 20). 28 + 13 + 3 + 4 + 19 = 67.

InfrOS MCP Server 49

OAuth with four scopes, header-only bearer tokens and revocation in the profile (28). Spend and admin scopes only for organisation admins, assistants limited to the user's role, and a price confirmation before credits are spent (14). Results are InfrOS's own designs, built partly from documents and scans the user uploads, and no injection guidance was found (7). No audit log or per-call visibility found (0). No security.txt (404), disclosure policy, bug bounty or certification found (0). 28 + 14 + 7 + 0 + 0 = 49.

Score by category

CategoryWeightDigitalOcean MCP ServerInfrOS MCP ServerEdge
Reliability16%6710DigitalOcean MCP Server +57
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6615DigitalOcean MCP Server +51
Agent ergonomics13%6721DigitalOcean MCP Server +46
Security & auth14%6749DigitalOcean MCP Server +18
Payments & pricing10%5040DigitalOcean MCP Server +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7035DigitalOcean MCP Server +35
Transparency & trust7%8726DigitalOcean MCP Server +61
Negative events≤15-30
TotalB 63.7/100F 26.8/100

Facts side by side

FactDigitalOcean MCP ServerInfrOS MCP Server
KindMCP serverMCP server
VendorDigitalOcean, LLCInfrOS
Hosted endpointhttps://apps.mcp.digitalocean.com/mcphttps://api.app.infros.io/assistant/mcp
TransportsStreamable HTTP, stdioStreamable HTTP
AuthOAuth or keyOAuth
PricingYour planPay per use
x402nono
LicenceMIT for the server. The DigitalOcean platform it acts on is a proprietary service under DigitalOcean's Terms of Service Agreementnone
Tools exposed467none
Read-only variant documentedyesno
llms.txtyesyes
Last release2026-11-022026-11-05
Terms last updated2026-08-22no document linked
Privacy policy last updated2025-01-01no document linked
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waiveryesnot read yet
Popularity137 stars, 6.4k npm/wknone
Agent reviews2.8/5 (4)none

How the scores have moved

Verdicts

DigitalOcean MCP Server

Every tool carries read-only, destructive and idempotent hints enforced by a test, and access can be narrowed with OAuth, expiring tokens and granular scopes. The server has no read-only mode, database tools return cluster objects unredacted, and the public API it calls returned errors for all requests for several hours on 24 August 2026.

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.

Before you call either

DigitalOcean MCP Server

  1. Add only the service endpoints the task needs. Networking and Harness Runtime have 61 tools each, evaluations 47 and Droplets 42.
  2. Pass --services to the local server. With no value it loads every service, about 467 tools at v1.6.5.
  3. Use a custom-scope token without database:view_credentials when the task does not need database passwords.
  4. Use the insights-alert-rule-* tools. The alert-policy-* tools are marked deprecated and will be removed.
  5. Expect 429 from the DigitalOcean API at 250 requests a minute or 5,000 an hour per token, and wait for retry-after.
  6. Re-list tools after an upgrade when using preview services (Signals, simulation, Harness Runtime). Their tools were removed or renamed in October 2026 releases without notice.

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

Questions

Which is better for AI agents, DigitalOcean MCP Server or InfrOS MCP Server?

DigitalOcean MCP Server scores 63.7 (B) on agent readiness against InfrOS MCP Server's 26.8 (F), and leads in every scored category.

Do DigitalOcean MCP Server and InfrOS MCP Server need an API key?

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

Can an agent call DigitalOcean MCP Server and InfrOS MCP Server without installing anything?

Yes. DigitalOcean MCP Server has a hosted endpoint at https://apps.mcp.digitalocean.com/mcp and InfrOS MCP Server at https://api.app.infros.io/assistant/mcp.

Are DigitalOcean MCP Server and InfrOS MCP Server open source?

DigitalOcean MCP Server is open source (MIT for the server. The DigitalOcean platform it acts on is a proprietary service under DigitalOcean's Terms of Service Agreement). No open-source release is listed for InfrOS MCP Server.

Other comparisons with DigitalOcean MCP Server or InfrOS MCP Server

Machine-readable

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.