ZopDev MCP server

ZopDev MCP

Cloud cost, inventory and governance on AWS, Azure and GCP — read-only by default, with optional scoped writes.

A hosted, remote Model Context Protocol server that gives an AI assistant grounded access to your ZopDev organisation's cloud estate: what is running, what it costs, what is wasted, what is scheduled, who owns it, and what shipped.

Point Claude Code, Claude Desktop, Cursor or Codex at it and ask questions that previously took six browser tabs and a spreadsheet — which non-production databases ran all weekend, what is our month-to-date Azure spend, show me every open recommendation over $500 a month we can apply without stopping anything.

One server covers both ZopDev products:

• ZopNight — cloud cost and FinOps: resource discovery, spend analysis, recommendations, budgets, and scheduled start/stop.
• ZopDay — build and deploy: projects, services, environments, deploys, rollbacks, databases, and cluster provisioning.

Remote and hosted — there is nothing to install, build or run.

• Learn more — https://zop.dev/learn/mcp-server
• Protocol reference — https://zop.dev/developer-docs/integrations/mcp-server/overview
• Claude setup guide — https://zop.dev/learn/how-to/set-up-zopnight-mcp-for-claude

Before you connect

MCP is enabled per organisation and is off by default. An admin (anyone with the Organisation Update permission) turns it on in Settings → Organisation → MCP Server, and chooses a write access level. That is the one step you may need to ask someone else for.

Once it is on, most clients will sign you in — there is nothing to copy by hand.

Install

OAuth — recommended, and no token to copy

Any client that can open a browser discovers the sign-in flow by itself. Add the URL and approve the consent screen; the client handles registration, PKCE and token refresh.

Claude Code

claude mcp add zopdev https://api.zop.dev/mcp-server -t http

Cursor / Claude Desktop / Codex

{
  "mcpServers": {
    "zopdev": {
      "url": "https://api.zop.dev/mcp-server"
    }
  }
}

VS Code

{
  "servers": {
    "zopdev": {
      "type": "http",
      "url": "https://api.zop.dev/mcp-server"
    }
  }
}

The -t http flag on Claude Code is required — it selects Streamable HTTP transport. Without it, Claude Code treats the URL as a command to execute rather than a server to call.

On first use you are sent to a ZopDev consent screen listing the scopes requested (mcp:read, mcp:write) and the exact write tools each admits. Approve, and you are connected. The client then appears under Connected Apps, where you can revoke it at any time.

Personal access token — for CI, scripts and non-browser clients

Create one under your profile → Developer Settings → Create Token, ticking the write capabilities it should carry. It is shown once and starts znpat.

claude mcp add zopdev https://api.zop.dev/mcp-server -t http \
  -H "Authorization: Bearer YOUR_TOKEN"

{
  "mcpServers": {
    "zopdev": {
      "url": "https://api.zop.dev/mcp-server",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

Shortened. The full README is on GitHub.