MCP Ipfs vs Infrawise
A side-by-side look at the MCP Ipfs and Infrawise MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Ipfs for cloud platforms work as a local process; choose Infrawise for cloud platforms as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Ipfs when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
W3_LOGIN_EMAIL.
Choose Infrawise when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
get_infra_overview, get_graph_summary, get_table_schema.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 39/100 · Fair | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | API key required |
| Pricing | Free | Free |
| Required env vars | W3_LOGIN_EMAIL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 21 | 22 |
| Directory activity | 2 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 22 |
| Full listing | View MCP Ipfs | View Infrawise |
Tools & capabilities
MCP Ipfs tools
No tool names declared yet. Check the project README from the listing page.
Infrawise tools 22
get_infra_overviewComplete snapshot — services, counts, high-severity findings, `configured` flag (data age and per-source status ride the `dataHealth` block on every response)get_graph_summaryFull infrastructure graph — all nodes, edges, and findingsget_table_schemaColumn-level schema for named tables/collections — types, PKs, FKs, indexes, DynamoDB keys/billing mode, cost signal (no row data)analyze_functionIssues 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_gsiExact GSI config for a DynamoDB table + attribute — names the existing index instead when one already covers itpostgres_index_suggestionsExact `CREATE INDEX` SQL for your actual tablesuggest_mongo_indexExact `createIndex` command for a MongoDB collection + fieldmysql_index_suggestionsExact `ALTER TABLE ADD INDEX` SQL for your MySQL tableget_queue_detailsSQS queues — DLQ status, encryption, FIFO type, visibility timeout, message countsget_api_routesAPI Gateway APIs (REST, HTTP, WebSocket) — routes, HTTP methods, paths, and Lambda integrationsget_topic_detailsSNS topics — subscription counts, protocols, and filter policies (required message attributes per subscription)get_secrets_overviewSecrets Manager — names, rotation status, and key names inferred from code (values never included)- +10 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Ipfs
{
"mcpServers": {
"alexbakers-mcp-ipfs": {
"command": "npx",
"args": [
"-y",
"mcp-ipfs"
],
"env": {
"W3_LOGIN_EMAIL": "YOUR_W3_LOGIN_EMAIL_HERE"
}
}
}
}
Infrawise
{
"mcpServers": {
"sidd27-infrawise": {
"command": "npx",
"args": [
"-y",
"infrawise"
]
}
}
}
Frequently asked questions
MCP Ipfs is categorized under Cloud Platforms and uses a local stdio subprocess. Infrawise belongs to Cloud Platforms and uses a local stdio subprocess. Pick MCP Ipfs for cloud platforms work and Infrawise for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Ipfs is listed as free. Auth: other. Infrawise is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add alexbakers-mcp-ipfs and sidd27-infrawise as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Ipfs has a quality signal of 39/100 (Fair) with 2 views, 0 installs and 21 GitHub stars. Infrawise has 64/100 (Good) with 3 views, 0 installs and 22 GitHub stars.