Skip to main content
MCP server CX Codex

InsideOut (Riley) — Claude Code MCP server: cloud infra from a prompt

Describe your app in plain words and the server proposes an AWS or GCP architecture, prices it, then deploys it. Useful when the backend has to exist today.

Install into Claude Code · Platform CLI: remote server All methods and platforms ↓
claude mcp add --transport http mcp https://app.luthersystems.com/v1/insideout-mcp
Open on GitHub

What InsideOut (Riley) does

InsideOut turns a written description of your application into an architecture. It picks services to fit the job, gives a monthly cost estimate before anything is deployed, writes Terraform, and applies it in your own AWS or GCP account. The same server then inspects environments, flags drift, reads logs and manages resources over time. Compute, databases, networking, storage, security, messaging, observability and CI/CD are covered — over 60 services across the two clouds.

It runs as an MCP server. In Claude the line is claude mcp add --transport http insideout-riley https://app.luthersystems.com/v1/insideout-mcp; in Codex it is codex mcp add insideout-riley --url https://app.luthersystems.com/v1/insideout-mcp. A local Docker option exists too: docker run -i --rm docker.io/luthersystems/insideout-mcp:v0.36.3. Cursor, GitHub Copilot and Gemini CLI take the server through their own config or add command.

Deployment happens in your account, so the permissions and the bill are yours. The Terraform is yours as well: files come out generated and exportable, which means you can drop back to managing it by hand whenever you like. Cost figures arrive before the deploy rather than on the invoice afterwards.

What it helps with

  • stand up a microservices backend without writing Terraform by hand
  • estimate monthly cloud spend before deploying anything
  • match AWS or GCP services to a written app description
  • catch drift between a live environment and its config
  • read logs and manage resources without leaving the editor

Example prompts for the agent

  • Build me a scalable AWS backend for my Go microservices app with a database and auth
  • What would this architecture cost per month?
  • Generate the Terraform and deploy it to my account

How to install InsideOut (Riley)

1Platform CLI: remote server

claude mcp add --transport http mcp https://app.luthersystems.com/v1/insideout-mcp

2Platform CLI

claude mcp add insideout-riley -- docker run -i --rm docker.io/luthersystems/insideout-mcp:v0.36.3

Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more

Questions about InsideOut (Riley)

How do I install InsideOut (Riley) in Claude Code?

Run claude mcp add --transport http insideout-riley https://app.luthersystems.com/v1/insideout-mcp. For a local server instead, use claude mcp add insideout-riley -- docker run -i --rm docker.io/luthersystems/insideout-mcp:v0.36.3.

What does InsideOut (Riley) do?

It designs AWS or GCP architecture from a text description, estimates the cost before deploy, generates Terraform and applies it. The same server later inspects environments, reads logs and manages resources.

Where does it deploy, and who owns the Terraform?

Into your own AWS or GCP account. The generated Terraform can be exported and maintained by hand afterwards.

Similar MCP servers

All MCP servers for DevOps and infrastructure →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor