# Sidd27/infrawise [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/Sidd27/infrawise  
**GitHub Stars:** 22  
**npm Downloads (last month):** 1022  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/sidd27-infrawise

## Description
Cloud infrastructure analysis for AI coding assistants — detects IaC drift, missing indexes, security gaps, and performance anti-patterns across AWS services and databases. 13 tools, works with Claude Code and Cursor.

## Tools
Capabilities this server exposes over MCP:

- **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)
- **analyze_function** — Issues in a specific function — scans, missing indexes, N+1, trigger event shapes, missing IAM permissions; returns every same-named file as a separate match, or bind to one with the optional `file` input; names refused Lambda links and why (`unresolvedLambdas`)
- **suggest_gsi** — Exact GSI config for a DynamoDB table + attribute — names the existing index instead when one already covers it
- **postgres_index_suggestions** — Exact `CREATE INDEX` SQL for your actual table
- **suggest_mongo_index** — Exact `createIndex` command for a MongoDB collection + field
- **mysql_index_suggestions** — Exact `ALTER TABLE ADD INDEX` SQL for your MySQL table
- **get_queue_details** — SQS queues — DLQ status, encryption, FIFO type, visibility timeout, message counts
- **get_api_routes** — API Gateway APIs (REST, HTTP, WebSocket) — routes, HTTP methods, paths, and Lambda integrations
- **get_topic_details** — SNS topics — subscription counts, protocols, and filter policies (required message attributes per subscription)
- **get_secrets_overview** — Secrets Manager — names, rotation status, and key names inferred from code (values never included)
- **get_parameter_overview** — SSM Parameter Store — names, types, tiers (values never included)
- **get_lambda_overview** — Lambda functions — runtime, memory, timeout, execution role ARN, triggers (SQS/SNS/DynamoDB/Kinesis/MSK/EventBridge/S3), env var key names, cost signal, why a Lambda could not be linked to its source (`unresolvedLink`)
- **get_eventbridge_details** — EventBridge rules — name, state, schedule/event pattern, target functions
- **get_s3_overview** — S3 buckets — versioning, encryption, public access, event notifications
- **get_log_errors** — CloudWatch log group names and retention (metadata only; no message bodies)
- **get_stack_outputs** — Stack outputs and cross-stack exports parsed from local IaC files, with staleness flags for orphaned `cdk.out` templates
- **get_cognito_overview** — Cognito user pools — MFA config, app client auth flows, OAuth settings, token validity (secrets never included)
- **get_stream_details** — Kinesis streams (shards, retention, capacity mode) and MSK clusters (state, Kafka version, brokers)
- **get_cache_overview** — ElastiCache clusters — engine, encryption in transit/at rest, replication group, failover, cost signal (data never read)
- **get_cloudfront_overview** — CloudFront distributions — per-behavior path patterns, origins (S3 vs custom, resolved API Gateway name), cache policy, viewer protocol policy

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "infrawise": {
    "command": "npx",
    "args": ["-y","infrawise"]
  }
}
```

## Documentation

## What Sidd27/infrawise does

Sidd27/infrawise gives MCP clients deterministic context about a project's code, AWS resources, and database schemas. It identifies infrastructure relationships and findings such as IaC drift, missing indexes, full-table scans, N+1 access patterns, security configuration gaps, and performance risks.

The server focuses on inspection and recommendations rather than provisioning or mutation. Its tools are annotated as read-only. Results can include service counts, high-severity findings, graph relationships, resource configuration, and data-health details describing snapshot age and source status.

Supported resource coverage includes Lambda, API Gateway, SQS, SNS, EventBridge, S3, CloudWatch Logs, Secrets Manager, SSM Parameter Store, Cognito, Kinesis, MSK, ElastiCache, and CloudFront. Database-oriented inspection covers DynamoDB, PostgreSQL, MongoDB, and MySQL.

## How it works

Run the CLI from the project directory. On first startup, it probes the environment, creates an `infrawise.yaml` configuration file, scans the codebase and AWS sources, and writes an MCP configuration file for the selected editor. The resulting snapshot is cached for 24 hours.

The stdio process can be spawned by an editor without loading the snapshot immediately. The first infrastructure tool call loads the cache; an absent or expired cache triggers a fresh analysis, while concurrent initial calls share that work. Running `infrawise start` before opening the editor prepares the cache and avoids that initial wait.

Local code changes are tracked after the snapshot loads. TypeScript refreshes scan changed files and transitive importers, Python refreshes scan changed Python files, and file additions or deletions update the snapshot. IaC extraction, graph construction, and analyzers continue to evaluate the complete snapshot so cross-resource findings remain available. Cloud metadata remains cached.

## Setup and configuration

Node.js 22 or newer is required. Install the package globally with:

```bash
npm install -g infrawise
```

Or run it without a global installation:

```bash
npx infrawise start --claude
```

For Claude Code, use `infrawise start --claude`; it creates or merges `.mcp.json` and opens Claude Code. Cursor uses `infrawise start --cursor`, which writes `.cursor/mcp.json`. VS Code uses `infrawise start --vscode`, which writes `.vscode/mcp.json` for Copilot agent mode. Running `infrawise start` without an editor flag writes a general `.mcp.json` and exits.

The server can also use HTTP transport:

```bash
infrawise serve
```

This exposes the MCP endpoint at `http://localhost:3000/mcp`. For a manually configured client, stdio can be started with `infrawise serve --stdio --config /path/to/infrawise.yaml`.

## Tools and capabilities

- Inspect an overall infrastructure snapshot or the full resource graph.
- Read table and collection schemas without retrieving row data.
- Analyze a named function, including scans, N+1 patterns, trigger event shapes, IAM gaps, and unresolved Lambda links. An optional file selector distinguishes same-named files.
- Generate exact DynamoDB GSI settings, PostgreSQL `CREATE INDEX` statements, MongoDB `createIndex` commands, and MySQL `ALTER TABLE ADD INDEX` statements.
- Inspect queues, topics, APIs, secrets metadata, parameters, Lambda functions, event rules, buckets, logs, stack outputs, Cognito pools, streams, caches, and CloudFront distributions.
- Preserve sensitive boundaries: secret values, parameter values, log message bodies, and database row data are not returned.

## Limitations and notes

Infrawise is an infrastructure analysis layer, not an agent framework, provisioning system, observability platform, or cloud management dashboard. Its recommendations are based on the scanned code, IaC, schemas, and cloud metadata available to the analysis.

Resource relationships may include an explanation when a Lambda or other source cannot be resolved. Cached analysis can become stale; responses expose data-health information, and stack outputs parsed from local IaC can carry staleness flags for orphaned `cdk.out` templates. The server does not change infrastructure because its MCP tools are read-only.

_Full upstream README: https://allmcps.com/mcp/sidd27-infrawise/readme_