Best for
- Teams building on AWS with TypeScript/JavaScript/Python
- Developers who want AI assistants to ground code generation in real infrastructure
- Engineering teams wanting infrastructure anti-pattern gates in CI
I
Infrawise MCP Server
Community
Give your AI coding assistant deterministic awareness of your AWS and database infrastructure
GitHub source repository ↗
64FMRS · C
A well-designed, read-only, local-first deterministic infrastructure analysis MCP server with 21 tools covering AWS, three databases, Kafka, and IaC drift — ideal for grounding AI coding assistants. Code-level correlation is currently limited to TS/JS/Python.
Infrawise is an MCP server for infrastructure analysis. It statically analyzes your codebase, AWS resources, database schemas, and IaC files (Terraform/CloudFormation/CDK), uses a graph engine and 36 rule-based analyzers to detect anti-patterns like full table scans, missing indexes/GSIs, hot partitions, N+1 queries, and missing DLQs, and exposes that context through 21 MCP tools to editors such as Claude Code, Cursor, and GitHub Copilot. Analysis is fully local, read-only, deterministic (no LLM involved in analysis), and telemetry-free. Supports stdio and HTTP (Streamable HTTP on port 3000) transports.
Tools
get_infra_overview
Full snapshot — services, counts, high-severity findings, analysis freshness, and configured flag
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
analyze_function
Issues in a specific function — scans, missing indexes, N+1, trigger event shapes, missing IAM permissions
suggest_gsi
Exact GSI config for a DynamoDB table + attribute
postgres_index_suggestions
Exact CREATE INDEX SQL for your actual PostgreSQL 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, methods, paths, and Lambda integrations
get_topic_details
SNS topics — subscription counts, protocols, and filter policies
get_secrets_overview
Secrets Manager — names, rotation status, and inferred key names (values never included)
get_parameter_overview
SSM Parameter Store — names, types, tiers (values never included)
get_lambda_overview
Lambda functions — runtime, memory, timeout, role ARN, triggers, env var key names, cost signal
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
get_cognito_overview
Cognito user pools — MFA config, auth flows, OAuth settings, token validity
get_stream_details
Kinesis streams (shards, retention, capacity mode) and MSK clusters (state, Kafka version, brokers)
get_cache_overview
ElastiCache clusters — engine, encryption, replication, failover, cost signal
Setup
Requires Node.js 22+. Run npm install -g infrawise or use npx infrawise start --claude (also --cursor, --vscode). The start command generates infrawise.yaml, scans your infrastructure, and writes the editor MCP config. The editor then manages infrawise serve --stdio; for HTTP run infrawise serve and configure url http://localhost:3000/mcp.
claude_desktop_config.json
{"mcpServers":{"infrawise":{"command":"npx","args":["-y","infrawise","serve","--stdio"]}}}
Fit and risk
Not for
- Projects not using AWS or the supported databases/messaging services
- Tooling that must provision or modify infrastructure (Infrawise is read-only)
- Code-level correlation in languages other than TypeScript/JS/Python (infrastructure-level analysis still works)
Required permissions
- AWS credentials via your existing credential chain (minimum dynamodb:ListTables/DescribeTable; full read-only IAM policy in docs)
- Optional read-only PostgreSQL/MySQL/MongoDB connections (read-only user recommended)
- SSO profiles require aws sso login first
Risks and side effects
- Reads infrastructure metadata via AWS APIs and DB connections; read-only and local, but use least-privilege credentials
- Python code scanning requires python3 on PATH
- Some supply-chain scanners may flag the 'infra' prefix as deceptive naming (author states this is a false positive; project is independent and unaffiliated)
- Large monorepos may need future incremental analysis optimization
Troubleshooting
- Run infrawise doctor to validate AWS/DB access, config, and repo scan
- Every service must be explicitly enabled: true in config; unlisted services are never contacted
- Cache expires after 24 hours; run infrawise analyze to force a rescan after major changes
- Dynamically constructed queries may not resolve statically
- Re-probe with infrawise start --rediscover
Use cases
Get real table/index context in Claude Code before generating DynamoDB or PostgreSQL queries
Detect full scans, N+1, hot partitions, and other anti-patterns in code
Gate deployments in CI with infrawise check severity thresholds
Detect drift between IaC files and deployed state
Supported clients
Claude CodeFull support
CursorFull support
VS Code (GitHub Copilot)Full support