Stigmer vs Shipstatic MCP
A side-by-side look at the Stigmer and Shipstatic MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Stigmer for cloud platforms work over a hosted endpoint; choose Shipstatic MCP 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 Stigmer when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
query, list_services, list_methods.
Choose Shipstatic MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
SHIP_TOKEN. - You want tools like
deployments_upload, deployments_list, deployments_get.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 55/100 · Good | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | SHIP_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 6 |
| Directory activity | 2 views 0 installs 0 upvotes | 7 views 0 installs 0 upvotes |
| Tools | 8 | 15 |
| Full listing | View Stigmer | View Shipstatic MCP |
Tools & capabilities
Stigmer tools 8
querySearch for verified method contracts for any library. Pass any text -- library name, method, what you're building, or an error you hit.list_servicesList all libraries and services that have verified method contracts. Use this first to discover what's available, then query for specific methods.list_methodsList all methods for a given library or service. Use after list_services to drill into a specific one.policyGenerate a least-privilege IAM policy for an AWS workflow. Pass a named workflow, explicit IAM actions, or a description. Returns the exact policy with confidence tier and any unresolved operations.list_workflowsList the curated named workflows that can generate least-privilege IAM policies.verifyFeed a generated policy back to AWS's own policy evaluation engine (SimulateCustomPolicy) and confirm it grants exactly the intended operations and nothing extra. Returns verified (True|False|unknown), grants_all, grants_extra. Requires AWS credentials; without them verified=unknown with the reason. Wildcarded operations are expanded to concrete actions first.authorizePre-flight authorization check for an AWS operation. Resolves the IAM actions the operation requires, then asks AWS's own policy simulator (SimulatePrincipalPolicy) whether the current role (or a given principal) allows them. Returns resolution (exact|partial|unresolved) and evaluation (allowed|denied|unknown) as separate fields. Requires AWS credentials; without them evaluation=unknown with the reason.registerRegister a fix. Three actions: confirm (it worked), append_thread (variant worked), new_receipt (nothing matched, I fixed it).
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
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.
Stigmer
{
"mcpServers": {
"stigmer": {
"url": "https://stigmer.network/mcp"
}
}
}
Shipstatic MCP
{
"mcpServers": {
"shipstatic-mcp": {
"command": "npx",
"args": [
"-y",
"@shipstatic/mcp"
],
"env": {
"SHIP_TOKEN": "YOUR_SHIP_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Stigmer is categorized under Cloud Platforms and uses a remote HTTP/SSE transport. Shipstatic MCP belongs to Cloud Platforms and uses a local stdio subprocess. Pick Stigmer for cloud platforms work and Shipstatic MCP 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.
Stigmer has no declared pricing — check the project's own site. Shipstatic MCP is listed as free. Auth: no auth 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 stigmer and shipstatic-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Stigmer has a quality signal of 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Shipstatic MCP has 67/100 (Great) with 7 views, 0 installs and 6 GitHub stars.