Ask your cloud
One command connects Claude Code, Cursor or Codex to zopnight, zopday and zopcloud. Read-only to start.
Works with
- Claude Code
- Cursor
- Codex
claude mcp add zop https://api.zop.dev/mcp-server …Your assistant already reads your code. It cannot see your cloud. Zop MCP connects the two, so you can just ask.
Products
One connection reads
from all three.
Best in class
Four things nobody else
puts in one place.
01
Advice from your bill, not a template
AWS, GCP and Azure advisors give everyone the same advice. Zop reads your accounts, your tags and your real bill, and surfaces the dollars you can actually stop spending.
- Ranked by what it saves, not by severity
- Every finding traced to a resource
- Reversibility stated before you apply it
02
The map of what is actually running
Not a diagram somebody drew last quarter. A live topology of every connected account, built from what the APIs return, and current the moment you open it.
- Every account, every region, one canvas
- Drift visible against what you expected
- Ownership attached to each node
03
168 hours billed, 50 hours used
Your dev environment runs every hour of the week. Your team uses a third of them. The engine schedules the rest off, in the right order and the right timezone, and reclaims the spend.
- Dependency order respected on wake
- Per-team timezones, not one global window
- Overrides when somebody needs it back
04
One shared key is not a strategy
Every team gets its own key with a hard budget, and the cap is enforced at the gateway rather than trusted to a dashboard nobody checks.
- Per-team keys with per-team budgets
- The cap enforced, not merely reported
- Spend by team, model and project
Proof
What Zop manages today.
“Zop has been instrumental in simplifying our multi-cloud operations, a must-have for any organization managing complex cloud environments.”
“Azure Advisor measured 14% of the opportunity. The other 86% was accumulating silently every month, until zopnight surfaced it in four weeks.”
“Manual cost governance turned into a continuously enforced operating model. We got fast value without re-engineering how anything is built.”
FAQ
Questions we get a lot.
Does connecting require an agent or code changes?
No. The server is remote and speaks streamable HTTP, so connecting registers a URL and a bearer token with your client. Nothing is installed on a developer machine, nothing runs in your cluster, and there is no agent to keep patched.
Can an assistant stop my instances?
Not on a new token. Reads are the default and writes are granted deliberately, per organisation and per service, by an admin. Until that happens the server can answer questions about your infrastructure and change nothing about it.
Does it bypass our access controls?
No. Every call goes through the same gateway your dashboard uses, and the gateway decides what the token may do. A token never exceeds the access of whoever issued it, so an assistant cannot reach something its owner could not reach directly.
Does it work across all three products?
Yes. It is one server and one listing, not one per product. The same token reaches zopnight, zopday and zopcloud, scoped to the services you choose when you issue it.
Which clients are supported?
Claude Code, Cursor and Codex ship a setup guide. Windsurf and Antigravity are documented. Because it is a remote MCP server rather than a local binary, any client that speaks MCP over HTTP can connect.
Is any of our data used for training?
No. The server reads your accounts to answer a question and returns the answer. Nothing is copied into a model and nothing is retained for training.
What happens when a token is revoked?
It stops working immediately. Tokens are issued and revoked in Developer Settings and carry an expiry, so an unused connection closes itself rather than lingering.
Bring your cloud.
Read-only connect. First findings in under five minutes.
Connect a cloud account, read-only. First findings in under five minutes, surfaced on your live cross-cloud inventory. Or pick the product that matches where you are today.