Zopdev MCP server
{
"mcpServers": {
"zopdev": {
"type": "http",
"url": "https://api.zop.dev/mcp-server"
}
}
}{
"mcpServers": {
"zopdev": {
"type": "http",
"url": "https://api.zop.dev/mcp-server"
}
}
}{
"mcpServers": {
"zopdev": {
"type": "http",
"url": "https://api.zop.dev/mcp-server"
}
}
}{
"servers": {
"zopdev": {
"type": "http",
"url": "https://api.zop.dev/mcp-server"
}
}
}{
"mcpServers": {
"zopdev": {
"type": "http",
"url": "https://api.zop.dev/mcp-server"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.1.1
What it does
ZopDev is a hosted MCP server that provides read-only access (by default) to cloud cost, inventory, and governance data across AWS, Azure, and GCP. It serves teams managing cloud estates through ZopNight (FinOps) and ZopDay (build and deploy), with optional scoped write capabilities.
- Query which non-production databases ran during weekends and what they cost.
- Analyze month-to-date cloud spend broken down by service and cloud provider.
- List open cost recommendations over a specific threshold that can be applied without disrupting services.
Tools this server exposes
| Tool | Does |
|---|---|
| list_organisations | Returns the organisations accessible to the authenticated session. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.