Cloudviz API vs Mumble

Cloudviz API

Diagrams come from the live AWS account through a read-only cross-account role with a per-customer external ID. AWS only, and API access starts at the $49 a month Team plan.

Mumble

Mumble keeps audio on the Mac and stores each conversation as plain files in ~/Mumble, with canvas JSON that diffs cleanly. There is no API or MCP server an outside agent can call today. The documented mumble-mcp has no public download, package or repository, and the app is reached only through an early-access waitlist.

Cloudviz API

1. Call GET /aws/accounts/ first to get the Cloudviz account ID, then request /aws/accounts/{account-id}/{region}/{format}
2. On a 202, wait and repeat the same GET until the diagram is ready
3. Ask for jsonSnapshot or jsonDiagram (there is no plain json format) when the agent has to reason over resources
4. Use a read-only key unless the agent has to add, change or delete AWS accounts

Mumble

1. Don't plan to call Mumble from another agent. Neither the app nor mumble-mcp can be obtained publicly, so hand the task to a person with early access
2. Don't configure /path/to/mumble-mcp from the docs. It is a placeholder, and no binary is published
3. If the person already has Mumble, read ~/Mumble/<capture>/ directly, capture.json for the transcript and diagram.canvas for the map
4. Keep canvas keys in schema order and never rename a node id, or the edges that name it are orphaned and the canvas is refused. Use git as the undo
5. Don't write to a capture that is being recorded. The app doesn't merge the two versions