Cloudcostwise vs Stigmer
A side-by-side look at the Cloudcostwise and Stigmer MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cloudcostwise for cloud platforms work as a local process; choose Stigmer for cloud platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Cloudcostwise when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
Choose Stigmer when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
query, policy, authorize.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 36/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing |
Tools & capabilities
Cloudcostwise tools
No tool names declared yet. Check the project README from the listing page.
Stigmer tools 8
querysearch by method name, library, service, error message, or what you're building. Pass `library` to scope to one SDK (boto3, aws-sdk-js).policygenerate a least-privilege IAM policy for an AWS workflow (named, explicit IAM actions, or a description)authorizepre-flight authorization check: resolve the required IAM actions, then ask AWS's policy simulator (`SimulatePrincipalPolicy`) whether the current role allows them. Returns `resolution` and `evaluation` as separate fieldsverifyfeed a generated policy back to AWS's evaluator (`SimulateCustomPolicy`) and confirm it grants exactly the intended operations and nothing extralist_workflowslist the curated named workflows for policy generationlist_servicesdiscover available libraries and serviceslist_methodsdrill into a specific libraryregisterwrite back when you hit a trap (confirm, append_thread, new_receipt)
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.
Cloudcostwise
{
"mcpServers": {
"cloudcostwise": {
"command": "uvx",
"args": [
"cloudcostwise"
]
}
}
}
Stigmer
{
"mcpServers": {
"stigmer": {
"url": "https://stigmer.network/mcp"
}
}
}
Frequently asked questions
Cloudcostwise is categorized under Cloud Platforms and uses a local stdio subprocess. Stigmer belongs to Cloud Platforms and uses a remote HTTP/SSE transport. Pick Cloudcostwise for cloud platforms work and Stigmer 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.
Cloudcostwise has no declared pricing — check the project's own site. Stigmer has no declared pricing — check the project's own site. 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 cloudcostwise and stigmer as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cloudcostwise has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Stigmer has 49/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.