ZopNight MCP Server — Your Cloud Costs, In Your AI Assistant

Ask your AI assistant about your cloud spend, and let it act safely. ZopNight ships a native MCP (Model Context Protocol) server exposing 337 tools over your live estate: costs and trends, budgets, anomalies, recommendations, resource topology, Kubernetes logs and events, deploys and schedules. Reads are instant; writes are governed by a three-layer permission model your org controls.

Every write authorized like the UI action

Point any MCP-capable client (Claude Code, Cursor, Codex, Windsurf, Claude Desktop) at the ZopNight endpoint with a personal access token. Every write is authorized exactly like the equivalent UI action (role checks on reads are still being rolled out): your user RBAC applies, the org-level write tier (off, metadata-only, reversible, irreversible) caps what any assistant can do, and every mutating tool supports idempotency keys so retries are safe. All MCP activity is audit-logged with its source, alongside UI and API actions.

A personal access token and one client config block

1. Create a personal access token: Settings > Developer > New token (choose scopes and expiry; it is shown once).

2. Copy the Server URL from your Organisation Settings page and add it to your client config:

   {"mcpServers":{"zopnight":{"url":"MCP_SERVER_URL","headers":{"Authorization":"Bearer zn_pat_YOUR_TOKEN"}}}}

   Or, in Claude Code:

   claude mcp add zopnight MCP_SERVER_URL -t http -H "Authorization: Bearer zn_pat_YOUR_TOKEN"

3. Ask your assistant for a cost overview to verify.

Read tools, mutating tools, and the three write tiers

337 tools: 186 read, 151 that make changes across three write tiers. Cost analytics, budgets, anomalies, recommendations, topology, K8s observability, deploy management, schedule control, integrations and audit logs. Idempotent writes, progress streaming for long operations, full audit trail with source attribution.