Sidd27/infrawise

Your AI coding assistant finally knows your infra.
Website ·
Docs ·
Quick start
Infrawise gives AI coding assistants deterministic infrastructure awareness.
It statically analyzes your codebase, cloud infrastructure, and database schemas, then exposes that context through MCP so tools like Claude Code can understand your actual tables, indexes, query patterns, and service relationships instead of guessing from source files alone.
---
Why this exists
New software developers don't write wrong code. Claude Code writes wrong code and they ship it. Infrawise is the only thing standing between Claude Code's generated output and a production incident.
AI coding assistants can read your source files but have no deterministic knowledge of your infrastructure. They do not know which GSIs exist, how tables are partitioned, which functions already trigger scans, or where indexes are missing. So they guess.
Infrawise replaces guessing with infrastructure-aware context.
**Without Infrawise**, an AI assistant might:
- Suggest a .scan() on your Orders table that has 50M rows
- Recommend adding a GSI on status that you already have
- Write a SELECT * when you need to keep query cost low
- Not notice that 5 functions are already hammering the same partition key
**With Infrawise**, it knows:
- Your exact table schemas, partition keys, sort keys, and GSIs
- Which functions query which tables and how
- Which patterns are already flagged as high severity
- The exact CREATE INDEX SQL or GSI config for your tables — not generic advice
---
What Infrawise is not
Infrawise is not an AI agent framework, an infrastructure provisioning tool, an observability platform, or a cloud management dashboard.
It is a deterministic infrastructure intelligence layer for AI-assisted development.
---
Installation
Requires **Node.js 22 or later** (node --version).
or use without installing:
---
Quick start
That's it. Infrawise will:
1. Probe your environment and generate infrawise.yaml (first time only — asks which AWS profile to use only if you have several)
2. Scan your AWS services, databases, and codebase
3. Write .mcp.json so your editor auto-connects on every future launch
4. Open Claude Code with all 22 MCP tools ready
**Every time after:**
Analysis is cached for 24 hours. When the cache is stale, infrawise serve --stdio (spawned automatically by your editor) refreshes it at session start. File changes are detected within the session and the code graph is updated automatically.
---
Using with AI coding assistants
Claude Code (recommended)
Writes .mcp.json to your project root (merging with any MCP servers already configured there) and opens Claude Code. Claude Code reads .mcp.json automatically on every launch and manages the infrawise serve --stdio process — no server to start, no ports to configure.
Infrawise is also installable as a Claude Code plugin. It registers the same MCP server and still needs an infrawise.yaml in the project, which infrawise start creates:
Cursor
Writes .cursor/mcp.json (merging with any existing MCP servers) and opens Cursor. All 22 infrawise tools are available in Cursor's MCP panel.
VS Code
Writes .vscode/mcp.json (merging with any existing MCP servers) and opens VS Code. The tools are available to Copilot agent mode via the MCP servers panel.
Any editor (no flag)
Writes .mcp.json (merging with any existing MCP servers) and exits. Open whichever editor you prefer — point it at infrawise serve --stdio --config /path/to/infrawise.yaml as an MCP server command.
HTTP transport (alternative)
If your editor or workflow requires an HTTP MCP endpoint instead of stdio:
Add to your editor's MCP config:
MCP tools
Every tool is annotated read-only (readOnlyHint: true, openWorldHint: false), so MCP clients that honor annotations can call them without a confirmation prompt.
| Tool | What it provides |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------- |
| get_infra_overview | Complete snapshot — services, counts, high-severity findings, configured flag (data age and per-source status ride the dataHealth block on every response) |
| get_graph_summary | Full infrastructure graph — all nodes, edges, and findings |
| get_table_schema | Column-level schema for named tables/collections — types, PKs, FKs, indexes, DynamoDB keys/billing mode, cost signal (no row data) |