Shipstatic MCP vs Infrawise
A side-by-side look at the Shipstatic MCP 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 Shipstatic MCP 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 Shipstatic MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SHIP_TOKEN. - You want tools like
deployments_upload, deployments_list, deployments_get.
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 | 65/100 · Great | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | SHIP_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 22 |
| Directory activity | 3 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 15 | 22 |
| Full listing | View Shipstatic MCP | View Infrawise |
Tools & capabilities
Shipstatic MCP tools 15
deployments_uploadDeploy a static site instantly: free, no account or API key required. Returns the live URL, file count, and size. Without SHIP_TOKEN, the response also includes a one-time claim URL, and the site expires in 3 days unless claimed. Pass `password` to make the site private.deployments_listList all deployments with their URLs, status, labels, and password protection state. The response's `cursor` is null on the last page; pass it back as `cursor` to fetch the next.deployments_getGet deployment details including URL, status, file count, size, labels, and password protection state.deployments_setUpdate deployment labels. Replaces all existing labels.deployments_deletePermanently deletes a deployment and its files.domains_setCreate or update a custom domain. Can reserve a name (omit deployment), link it to a deployment, switch deployments, or update labels. domains_records then returns the DNS records to configure.domains_listList all domains with their URLs, linked deployment, and `status`. The response's `cursor` is null on the last page; pass it back as `cursor` to fetch the next.domains_getGet domain details including URL, linked deployment, labels, and `status`: the one word saying what the domain needs from its owner (`unverified`, `unlinked`, `live`, `paused`).domains_recordsReturns the DNS records to configure at the domain's DNS provider. Call after domains_set. Custom domains only: a ShipStatic domain has no records to configure.domains_dnsReturns the DNS provider recorded for the domain, if known (e.g. Cloudflare, Namecheap): where its DNS records are configured. Custom domains only, and only while the domain is unverified; once its DNS is right there is nothing left to locate.domains_shareReturns a shareable DNS setup URL that needs no API key, for whoever manages the domain's DNS. Custom domains only, and only while the domain is unverified; a verified domain has no setup left to share.domains_validateCheck if a domain name is valid and available before creating it. Returns the normalized form and availability.- +3 more on 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.
Shipstatic MCP
{
"mcpServers": {
"shipstatic-mcp": {
"command": "npx",
"args": [
"-y",
"@shipstatic/mcp"
],
"env": {
"SHIP_TOKEN": "YOUR_SHIP_TOKEN_HERE"
}
}
}
}
Infrawise
{
"mcpServers": {
"sidd27-infrawise": {
"command": "npx",
"args": [
"-y",
"infrawise"
]
}
}
}
Frequently asked questions
Shipstatic MCP is categorized under Cloud Platforms and uses a local stdio subprocess. Infrawise belongs to Cloud Platforms and uses a local stdio subprocess. Pick Shipstatic MCP 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.
Shipstatic MCP has no declared pricing — check the project's own site. 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 shipstatic-mcp and sidd27-infrawise as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Shipstatic MCP has a quality signal of 65/100 (Great) with 3 views, 0 installs and 6 GitHub stars. Infrawise has 64/100 (Good) with 3 views, 0 installs and 22 GitHub stars.