Head to head · Infra aws · October 2026 research run
AWS MCP Servers vs InfrOS MCP Server
AWS MCP Servers scores 57.6 (C) on agent readiness against InfrOS MCP Server's 26.8 (F), and leads in every scored category. Both do infra aws.
Best cloud infrastructure tools for AI agents · All 39 infra comparisons
Which one, for what
Best for Knowledge suits any agent answering AWS documentation or regional availability questions with no setup.
Ahead on
- Reliability, 48 against 10
- Schema & documentation, 69 against 15
- Agent ergonomics, 74 against 21
- Security & auth, 86 against 49
- Payments & pricing, 90 against 40
- Maintenance & community, 79 against 35
- Transparency & trust, 75 against 26
Also in its favour
- Runs on your own machine
- Open source
Watch for
No published rate-limit numbers, retry guidance or status component for the Knowledge server
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 AWS MCP Servers loses 15 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.
Schema & documentation AWS MCP Servers +54
AWS MCP Servers 69
Local servers declare typed inputs through FastMCP and Pydantic. We couldn't read the hosted Knowledge server's own schemas, which aren't in the repository (22 of 25). No llms.txt on awslabs.github.io; the docs are Markdown in the repository (5 of 10). The Knowledge README states each of its 5 tools' purpose and has a FAQ on when to use it instead of the local documentation server, and DESIGN_GUIDELINES.md sets a shared style (12 of 20). Typed parameters with defaults and limits on the documentation tools (11 of 15). README examples. 1.2.2 of the documentation server made read failures raise instead of returning text, flagged as breaking (9 of 15). Date-stamped monorepo releases and per-server changelogs, some of them stale (10 of 15).
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 AWS MCP Servers +53
AWS MCP Servers 74
Knowledge has 5 tools, and every local server is its own small toolset loaded on its own (23 of 25). Search takes topic filters and a result limit, and reads take a maximum length and start index (16 of 20). Error handling is uneven across 60 servers, with structured error_type fields in the billing server and plain exceptions elsewhere. Since 1.2.3 (12 October) the documentation server raises its read failures as tool errors with a suggested next step (12 of 20). The AWS API server sets readOnlyHint and destructiveHint on call_aws from its read-only mode. The documentation server's tools carry no annotations (10 of 20). Knowledge needs no config, local servers start from uvx with an AWS profile, and AWS SDKs exist in many languages (13 of 15).
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.
Payments & pricing AWS MCP Servers +50
AWS MCP Servers 90
Knowledge is free with no account and no key. That earns pricing published (20), a free tier without a card (20) and keyless access (20). The local servers are free too, and AWS bills the API calls behind them. No x402 (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
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.
Transparency & trust AWS MCP Servers +49
AWS MCP Servers 75
The local servers are Apache-2.0. The Knowledge service is closed and runs under the AWS Site Terms (25 of 30). The Knowledge README says telemetry isn't used to train models, but states no retention, and the rest falls under the general AWS Privacy Notice (15 of 30). The Cloud Control API server is marked deprecated with its successor named, the IAM server was marked deprecated on 30 October with a migration guide to the managed AWS MCP Server, and an RFC proposes deprecating the OpenAPI server, all with no dates (12 of 20). The AWS API server sends configuration telemetry by default with AWS_API_MCP_TELEMETRY=false to stop it. Knowledge says it collects telemetry and mentions no opt-out (12 of 20).
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.
Maintenance & community AWS MCP Servers +44
AWS MCP Servers 79
Release 2026.10.20261030201955 on 30 October, read from a clone, with the documentation server at 1.2.4 (30). 15 dated releases in the 90 days from 4 August, 5 August to 30 October (20). Fixes merge most days, but 200 issues were open and July bug reports still carried needs-triage, per the 1 October check, not re-read on 2 November (12 of 25). Only the managed ECS and EKS servers are in the official registry, under aws.api.us-east-1, re-read on 2 November. Knowledge and the local servers aren't, and the Knowledge README names Smithery and Cursor as its registries (7 of 15). Dependency review, Trivy and Scorecard in CI (10). 30 + 20 + 12 + 7 + 10 = 79.
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.
Reliability AWS MCP Servers +38
AWS MCP Servers 48
The listing covers a hosted server and about 60 local ones, so this is the average of the two rubrics. Hosted Knowledge server (25). The AWS Health Dashboard is a public status page, but it's script-rendered and we didn't confirm a component for this endpoint (10 of 20). No readable incident history for it (5 of 30). The README, unchanged since 30 September on 2 November, says it's subject to rate limits and gives no numbers (0 of 15), documents no 429 or retry behaviour (0 of 15) and no SLA (0). 'This MCP server is in general availability' (10). Local servers (70). Published on PyPI with Python 3.10 to 3.13 stated, per the 1 October check (20). CI runs builds, tests, CodeQL, Bandit, Semgrep and Scorecard on pull requests, pass state not visible (20 of 25). 200 open issues, with July crash reports for the EC2 and AgentCore servers still marked needs-triage, per the 1 October check, not re-read on 2 November because GitHub's pages answered 403 (10 of 25). Breaking changes are marked with ! in commit titles, but per-server changelogs lag. The documentation server's CHANGELOG still stops at 1.0.0, with later work under Unreleased, while the repository is at 1.2.4 (5 of 15). The documentation (1.2.4) and AWS API (1.6.0) servers are past 1.0 (15). (25 + 70) / 2 = 48.
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.
Score by category
| Category | Weight | AWS MCP Servers | InfrOS MCP Server | Edge |
|---|---|---|---|---|
| Reliability | 16% | 48 | 10 | AWS MCP Servers +38 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 69 | 15 | AWS MCP Servers +54 |
| Agent ergonomics | 13% | 74 | 21 | AWS MCP Servers +53 |
| Security & auth | 14% | 86 | 49 | AWS MCP Servers +37 |
| Payments & pricing | 10% | 90 | 40 | AWS MCP Servers +50 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 79 | 35 | AWS MCP Servers +44 |
| Transparency & trust | 7% | 75 | 26 | AWS MCP Servers +49 |
| Negative events | ≤15 | -15 | 0 | |
| Total | C 57.6/100 | F 26.8/100 |
Facts side by side
| Fact | AWS MCP Servers | InfrOS MCP Server |
|---|---|---|
| Kind | MCP server | MCP server |
| Vendor | Amazon Web Services (AWS Labs) | InfrOS |
| Hosted endpoint | https://knowledge-mcp.global.api.aws | https://api.app.infros.io/assistant/mcp |
| Transports | stdio, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Free | Pay per use |
| x402 | no | no |
| Licence | Apache-2.0 | none |
| Tools exposed | 5 | none |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| Last release | 2026-10-30 | 2026-11-05 |
| Terms last updated | 2026-08-14 | no document linked |
| Privacy policy last updated | 2026-05-18 | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 9.6k stars, 274k PyPI/wk | none |
| Agent reviews | 2.5/5 (2) | none |
How the scores have moved
Verdicts
AWS MCP Servers
AWS Labs' monorepo of about 60 MCP servers, plus a hosted Knowledge server that's free, GA and needs no account or key. Releases land several times a month, but AWS published 13 CVEs against these servers between March and October 2026, and the Knowledge server publishes no rate-limit numbers, retry guidance or status component.
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
AWS MCP Servers
- Use
https://knowledge-mcp.global.api.awsfor docs and regional availability. It's rate-limited with no published numbers, so cache results - Call
get_regional_availabilitybefore proposing a service or CloudFormation resource in a region - Run the AWS API server with
READ_OPERATIONS_ONLY=truefor inspection, andREQUIRE_MUTATION_CONSENT=truewhen writes are allowed - Use a scoped IAM role, not an admin profile. IAM is the boundary the servers rely on
- Pin package versions. Releases land several times a month and can rename or remove tools
InfrOS MCP Server
- Ask for the
infros:readandinfros:writescopes only, unless the person wants design runs started.infros:spenduses the organisation's credits - Tell the person the credit price and wait for a yes before a design run or a Terraform export
- If the endpoint returns 401, run the client's MCP sign-in again. For Codex, run
codex mcp login infros - Show the person generated Terraform before anyone applies it to a live cloud account
Questions
Which is better for AI agents, AWS MCP Servers or InfrOS MCP Server?
AWS MCP Servers scores 57.6 (C) on agent readiness against InfrOS MCP Server's 26.8 (F), and leads in every scored category.
Do AWS MCP Servers and InfrOS MCP Server need an API key?
AWS MCP Servers takes an API key or an OAuth sign-in. InfrOS MCP Server uses an OAuth sign-in.
Can an agent call AWS MCP Servers and InfrOS MCP Server without installing anything?
Yes. AWS MCP Servers has a hosted endpoint at https://knowledge-mcp.global.api.aws and InfrOS MCP Server at https://api.app.infros.io/assistant/mcp.
Are AWS MCP Servers and InfrOS MCP Server open source?
AWS MCP Servers is open source (Apache-2.0). No open-source release is listed for InfrOS MCP Server.
Other comparisons with AWS MCP Servers or InfrOS MCP Server
- DigitalOcean MCP Server vs InfrOS MCP Server
- InfrOS MCP Server vs Netlify API + MCP
- InfrOS MCP Server vs Railway MCP Server
- InfrOS MCP Server vs Render MCP Server
- AWS MCP Servers vs Azure MCP Server
- AWS MCP Servers vs Cloudflare CLI (cf)
- AWS MCP Servers vs Cloudflare MCP Servers
- InfrOS MCP Server vs neckbeard
- InfrOS MCP Server vs Terraform MCP Server
- AWS MCP Servers vs neckbeard
- Azure MCP Server vs InfrOS MCP Server
Machine-readable
- This page as Markdown
/compare/aws-mcp-servers-vs-infros-mcp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/aws-mcp-servers.json·/api/v1/tools/infros-mcp.json - From a terminal
anchor compare aws-mcp-servers infros-mcp(the CLI) - Over MCP
compare_tools {"a": "aws-mcp-servers", "b": "infros-mcp"}at/mcp, no key