InsideOut — Riley Infrastructure Agent

Created By
luthersystemsa month ago
Conversational AI agent that designs AWS/GCP architecture, generates Terraform, estimates costs, and deploys — all through MCP.
Overview

InsideOut exposes Riley, an AI infrastructure advisor, as an MCP server. Describe your application in plain English — Riley designs a complete AWS or GCP architecture, generates production-ready Terraform, estimates monthly costs, and deploys.

Key features

  • Conversational infrastructure design across 50+ AWS and GCP services
  • Monthly cost estimation broken down by component before deploy
  • Terraform generated by module (networking, compute, storage, auth, etc.)
  • One-command deployment to AWS or GCP
  • Live deployment monitoring and post-deploy infrastructure management
  • No Terraform expertise required

Install options

  • Claude Code: /plugin marketplace add luthersystems/insideout-claude-code
  • Kiro IDE: insideout-power plugin
  • Cursor / any MCP agent: add https://app.luthersystems.com/v1/insideout-mcp (streamable-http) to MCP config
  • Docker: docker run -i luthersystems/insideout-mcp
  • Agent Skills (30+ tools): npx skills add insideout

Cross-listings

Category

Cloud Infrastructure / DevOps / Terraform

Server Config

{
  "mcpServers": {
    "insideout": {
      "type": "http",
      "url": "https://app.luthersystems.com/v1/insideout-mcp"
    }
  }
}
Project Info
Created At
a month ago
Updated At
a month ago
Author Name
luthersystems
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 hours ago
Gpt Scrambler

2 days ago