Infrastructure analysis for AWS (15 tools) — DynamoDB, Lambda, SQS, SNS, S3, PostgreSQL, MongoDB.
Most database access work still happens through a UI a human drives. Infrawise MCP server moves it into the conversation instead. Infrastructure analysis for AWS (15 tools) — DynamoDB, Lambda, SQS, SNS, S3, PostgreSQL, MongoDB.
Infrawise gives AI coding assistants deterministic infrastructure awareness.
The server publishes 14 tools. What each one is for:
get_infra_overview — Complete snapshot — services, counts, high-severity findings, analysis freshness (age + stale flag), configured flagget_graph_summary — Full infrastructure graph — all nodes, edges, and findingsget_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 permissionssuggest_gsi — Exact GSI config for a DynamoDB table + attributepostgres_index_suggestions — Exact CREATE INDEX SQL for your actual tablesuggest_mongo_index — Exact createIndex command for a MongoDB collection + fieldmysql_index_suggestions — Exact ALTER TABLE ADD INDEX SQL for your MySQL tableget_queue_details — SQS queues — DLQ status, encryption, FIFO type, visibility timeout, message countsget_api_routes — API Gateway APIs (REST, HTTP, WebSocket) — routes, HTTP methods, paths, and Lambda integrationsget_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)Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Infrawise's toolset — get_infra_overview, get_graph_summary, get_table_schema and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Sidd27; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| get_infra_overview | Complete snapshot — services, counts, high-severity findings, analysis freshness (age + stale flag), 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 (no row data) |
| 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 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 |
Add to your editor's MCP config:
```json
{
"mcpServers": {
"infrawise": {
"url": "http://localhost:3000/mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.