# Sidd27/infrawise [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/Sidd27/infrawise  
**GitHub Stars:** 21  
**npm Downloads (last month):** 2786  
**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 error patterns and counts (no raw log messages)
- **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 MCP server does

Sidd27/infrawise MCP server analyzes a codebase, AWS resources, and supported database schemas so an MCP client can query infrastructure facts instead of inferring them from source files. The analysis covers service relationships, Lambda usage, database access patterns, infrastructure findings, and selected configuration details.

Its responses can identify high-severity findings, data age, and per-source status through the `dataHealth` information. Database inspection is schema-level: table and collection names, columns, keys, foreign keys, indexes, and selected cost signals are available, but row data is not returned. Secrets Manager and SSM results expose names and metadata without secret or parameter values.

## How it works

Run the command from the project directory. On first use, the CLI probes the environment and creates `infrawise.yaml`; when multiple AWS profiles are available, it asks which profile to use. It then scans AWS services, databases, and source code, writes an editor MCP configuration file, and connects the client to `infrawise serve --stdio`.

Analysis is cached for 24 hours. When the cache is stale, the stdio process refreshes it at session start. Changes to files are detected during a session and update the code graph automatically. An alternative HTTP transport is available at `http://localhost:3000/mcp` when the server is started with `infrawise serve`.

## Setup and configuration

Node.js 22 or later is required. Install the npm package globally with `npm install -g infrawise`, or run it without a global installation using `npx infrawise start --claude`. The `start` command supports Claude Code, Cursor, and VS Code flags, and can also write a generic `.mcp.json` without opening an editor.

Claude Code uses `.mcp.json`, Cursor uses `.cursor/mcp.json`, and VS Code uses `.vscode/mcp.json`. These files are merged with existing MCP server entries. For a manually configured client, point the MCP command at `infrawise serve --stdio --config /path/to/infrawise.yaml`, replacing the path with the project’s actual configuration file.

## Tools and capabilities

Sidd27/infrawise MCP server exposes tools for infrastructure summaries and graph inspection, including service counts, findings, nodes, and edges. Function analysis can report scans, missing indexes, N+1 patterns, trigger event shapes, missing IAM permissions, duplicate function-name matches, and Lambda links that could not be resolved.

AWS-specific tools cover SQS queues, API Gateway routes, SNS topics, Secrets Manager, SSM Parameter Store, Lambda functions, EventBridge rules, S3 buckets, CloudWatch error patterns, Cognito pools, Kinesis streams, MSK clusters, ElastiCache, and CloudFront distributions. Other tools return table schemas or index recommendations for DynamoDB, PostgreSQL, MongoDB, and MySQL. Recommendations include concrete GSI configurations, `CREATE INDEX` statements, `createIndex` commands, or MySQL `ALTER TABLE` statements.

## Limitations and notes

Infrawise is an analysis and context layer, not an infrastructure provisioning tool, AI agent framework, observability platform, or cloud management dashboard. Its outputs are based on scanned code, infrastructure, and schemas, so stale caches and unresolved Lambda links should be considered when interpreting results. Secret values, parameter values, database rows, and cache data are not read or included in the described outputs.

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