zopnight

ZopNight provides a Model Context Protocol (MCP) server that lets AI assistants query your cloud infrastructure data directly. You can ask your AI tool about resources, costs, schedules, recommendations, and more — all through natural language.

What is MCP?

MCP (Model Context Protocol) is an open standard that allows AI tools to connect to external data sources. ZopNight's MCP server uses Streamable HTTP transport — your AI tool sends standard HTTP POST requests to the server. It is not SSE (Server-Sent Events) or WebSocket based.

Prerequisites

Before connecting, you need:

• A ZopNight account with at least one organisation
• Admin or Editor role in the organisation
• MCP Server enabled for your organisation
• A Personal Access Token (PAT)

Follow the How to Connect guide to enable MCP and create your token.

How It Works

1. Your AI tool sends a POST request to the MCP server URL with your PAT token
2. The gateway validates the token and identifies your email
3. The AI tool calls list_organisations to discover your organisations
4. The server checks that MCP is enabled for the requested organisation
5. The server verifies you are a member of that organisation
6. The gateway checks the call against your live role — and, if the tool changes something, against the organisation's write tier
7. Results are returned as JSON to the AI tool

Every check happens at the gateway, on the way in. A tool call is authorized the same way the equivalent action in the UI is: same permissions, same answer. MCP is not a second way in with rules of its own.

Protocol Details

The MCP server speaks JSON-RPC 2.0 over HTTP POST. It supports the initialize, tools/list, and tools/call methods. All responses are application/json. There is no streaming or SSE — each request gets a single JSON response.

Connect Your AI Tool

After completing the setup, connect your preferred AI tool:

• Connect to Cursor
• Connect to Claude Code
• Connect to Codex
• Connect to Windsurf
• Connect to Antigravity

What Can You Do?

The MCP server exposes read tools covering resources, costs, schedules, recommendations, cloud accounts, teams, budgets, metrics, billing, and audit logs, and a set of write tools that change things. See Available Tools for what each class covers, and ask your AI tool to list its ZopNight tools for the authoritative list.

Writes are off by default — and off entirely today

Every organisation starts read-only, and MCP write is currently disabled across the platform while it rolls out: a mutating tool call is refused whatever you configure. When it reaches you, write access is opt-in per organisation via a tier in Settings → Organisation, and an agent can never exceed the permissions of the person whose token it holds.

Before you enable a tier, read the disclosure in How to Connect: enabling MCP write means any content in your cloud environment becomes a potential instruction to your agent.

Having issues? See the Troubleshooting guide for common problems and solutions.