# InfrOS MCP Server (slim)

> The InfrOS MCP server connects AI assistants to InfrOS, a hosted service that designs cloud architectures across AWS, Google Cloud, Azure and Oracle Cloud, validates them by emulation and exports Terraform. It is a remote server behind OAuth.

- Full: https://www.anchorterminal.com/tools/infros-mcp.md (~5,550 tokens) · this version ~1,280 tokens · JSON https://www.anchorterminal.com/tools/infros-mcp.json · canonical https://www.anchorterminal.com/tools/infros-mcp
- 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-18 · pricing https://www.anchorterminal.com/tools/infros-mcp#pricing · reviews https://www.anchorterminal.com/tools/infros-mcp#reviews
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

**F · 26.8/100 · rank #1478 of 1557 · #11 in Cloud & infrastructure · not agent-ready · confidence low** · WARNING: Operator not identified


Assessment: 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.

## Facts

- Kind: MCP server · vendor: InfrOS · category: Cloud & infrastructure · legal entity: Cloudculate Ltd. · provenance 41/100
- Endpoint: `https://api.app.infros.io/assistant/mcp` (Streamable HTTP)
- Auth: OAuth · pricing: Pay per use · x402: no · licence: unknown
- Benchmark probes: not run yet, so Performance is pending
- Live, from our pollers (not part of the score): up at 2026-11-18 23:01 UTC · uptime 30 days 100.0% (14 probes) · p50 375 ms · p95 731 ms over 24 hours
- Surface listed: The remote MCP server at https://api.app.infros.io/assistant/mcp, read from infros.io's setup post, pricing, about, product, news, terms and privacy pages and the OAuth metadata on 18 November 2026. One unauthenticated `initialize` was sent and answered 401, so `tools/list` wasn't sent and no tool was called
- What it does: Read Systems, specifications, landing zones and architecture proposals. Create Systems and versions and edit drafts. Start design runs and Terraform generation. Manage landing zones, standing constraints and GitHub repositories, per the setup post
- Clouds: AWS, Google Cloud, Azure and Oracle Cloud, per the home page
- Credit costs: Architecture design 200 to 1,200 credits, IaC export 100 to 400, fixes and updates 50 to 400. The pricing page's examples run from about 950 to 5,500 credits a month
- Status: Announced on InfrOS's blog on 5 November 2026. A press article listed on InfrOS's news page calls it a preview, and InfrOS's own pages don't say

- Scores: Reliability 10, Performance not tested, Schema & documentation 15, Agent ergonomics 21, Security & auth 49, Payments & pricing 40, Task success not tested, Maintenance & community 35, Transparency & trust 26
- Why: Reliability, Graded as a hosted MCP server. · Schema & documentation, No tool list or schema is published, and the endpoint needs OAuth before `initialize`. · Agent ergonomics, Tool count and sizes couldn't be read. · Security & auth, OAuth with four scopes, header-only bearer tokens and revocation in the profile (28). · Payments & pricing, No payment protocol (0). · Maintenance & community, Read as a closed hosted service. · Transparency & trust, Closed service.
- Sources: 11, open questions: 4, both in the full twin
- Capabilities: infra.terraform, infra.cloud, infra.aws, infra.azure
- JSON: https://www.anchorterminal.com/api/v1/tools/infros-mcp.json
- Its vendor verifies the listing with `verify_listing` or `POST https://www.anchorterminal.com/api/v1/verify` (the full twin says how); no effect on the grade.
- Support: info@infros.io; https://infros.io/blog-posts/mcp-setup-instructions; more in the full twin

## Before you call it

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

## Connect

```bash
claude mcp add --transport http infros https://api.app.infros.io/assistant/mcp
```
Full config and headless snippets are in the full page. Through letme (picks today, calling later): https://letme.dev/infros-mcp

## Similar tools

| Tool | Grade | Score | Shared capabilities | Slim |
| --- | --- | --- | --- | --- |
| neckbeard | B | 66 | infra.terraform, infra.cloud, infra.aws, infra.azure | https://www.anchorterminal.com/tools/neckbeard.min.md |
| Terraform MCP Server | BB | 73.7 | infra.terraform, infra.cloud | https://www.anchorterminal.com/tools/terraform-mcp.min.md |
| Azure MCP Server | BB | 72.1 | infra.azure, infra.cloud | https://www.anchorterminal.com/tools/azure-mcp.min.md |
| AWS Secrets Manager | A | 80.3 | infra.aws | https://www.anchorterminal.com/tools/aws-secrets-manager.min.md |
| Amazon Bedrock AgentCore Identity | A | 78.2 | infra.aws | https://www.anchorterminal.com/tools/agentcore-identity.min.md |


## Panel reviews (0, desk reviews from public material, no calls made)

