MCP and AI Cloud Management: What an MCP Server Actually Does

Model Context Protocol (MCP) is the most useful boring protocol in the AI ecosystem. It defines how AI assistants like Claude Desktop, Cursor, and Codex discover and call tools provided by external servers. There is no model magic. There is no proprietary integration. There is a small standardised surface for authentication, schema discovery, and request and response shapes.

The interesting part is what becomes possible once your cloud platform exposes an MCP server. AI assistants stop being a place to copy-paste error messages from. They become a query interface for live data: “Show me the top 10 idle EC2 instances by monthly cost.” “Which teams are over budget this month?” “Which Bedrock provisioned throughput units are below break-even?” Claude calls the right tools, joins the data, and answers in seconds.

This article walks through what the ZopNight MCP server provides, how it stays safe (read-only, RBAC-enforced at the gateway, audit-logged), and the design choices that make it useful at scale (gRPC transport, in-memory TTL cache, boolean filter normalization).

This guide keeps the theory short and spends most of its length on what you can actually do. Every recommendation here is one ZopNight can help you execute, starting from a read-only connection.

What an MCP server provides

An MCP server registers tools with the AI client. Each tool has a schema (input parameters, output shape) and a description. The AI assistant discovers the tools at session start and calls them as needed. ZopNight ships 43 read-only tools covering resources, schedules, costs, recommendations, teams, budgets, audit logs, cloud accounts, overrides, notifications, and billing sync. Read-only enforcement returns operation not permitted on any write attempt.

Authentication and RBAC

PAT tokens (zn_pat_*) authenticate the AI client to the gateway. The gateway enforces RBAC, the MCP server is a stateless proxy. Resource-scoped policies apply to MCP calls the same way they apply to UI calls, so a viewer-role PAT can read what a viewer can read. An org-level MCP toggle controls availability. Audit logs flow through the same gateway middleware as the rest of the API and sync to MySQL via the aggregator.

Performance and reliability

gRPC transport to all 5 backend services (Config, Discoverer, Executor, Aggregator, Recommender) with HTTP fallback per-service via *_GRPC_HOST env vars. In-memory TTL cache for expensive aggregation tools (2-30 min TTLs). Full filter and pagination forwarding on all list tools (provider, status, region, search, sort). Boolean filter normalization handles “1”/“0”/“yes”/“no” so client SDKs do not have to.

What AI cloud management looks like

A FinOps lead asks Claude “Which cloud accounts have the worst waste this month?” Claude calls list_cloud_accounts, get_recommendation_summary per account, and ranks by total reclaimable. A platform engineer asks “Why did EC2 cost spike on Tuesday?” Claude calls get_cost_trends, identifies the spike, and calls get_recommendation for the affected resources. The pattern is simple: AI translates natural language into structured tool calls and synthesizes the answer. The MCP server provides the structure.

Key takeaways

• MCP is a small standardised protocol for AI assistants to discover and call tools provided by external servers.
• ZopNight ships 43 read-only MCP tools covering the operational surface a FinOps or platform team needs.
• Read-only enforcement, RBAC at the gateway, and audit logging make MCP safe to deploy at scale.
• AI cloud management is mostly natural language querying, the MCP server provides the structured tool layer.

Where ZopNight fits

ZopNight turns this from reading into doing. It ships 490 built-in audit rules across AWS (216), GCP (127), and Azure (147), 124 of those recommendations are wired to act end to end, 28 one-click and 96 guided, and it starts read-only so you can see the opportunity before you act on any of it. The most direct place to begin is scheduling non-production resources to your working hours, which is covered in the FinOps guide and shown concretely for AWS EC2.

How ZopNight schedules non-production resources

The loop that does this is deliberately mechanical, and it starts read-only. You connect your cloud provider with a read-only role, and ZopNight discovers every non-production resources across your regions and accounts. It records a per-action permission verdict for each one, so you can see where it can list a resource but not yet stop it, and you review that inventory, filter it by status or type, and search for the specific resources you care about before anything is scheduled.

Scheduling itself is a cron you write once in plain terms, stop at 7 PM, start at 8 AM on weekdays, pinned to your timezone so the jobs fire at local business hours rather than UTC. A weekly 24-hour grid shows the schedule visually so you catch gaps and overlaps before you save, and an estimate of active versus inactive hours appears before you commit. Resources attach individually or bundle into groups like “dev-cluster” or “staging-db” so a whole environment follows one cadence.

Actions run in dependency order, so a database comes up before the app server that depends on it. When something needs to stay up, an override forces a non-production resources ON or OFF for a defined window, carries a reason so teammates understand why it exists, and expires automatically so nothing is left running by accident. If a start or stop fails, ZopNight retries up to three times and falls back to a dead-letter queue rather than silently dropping the action, and every state change lands in an audit trail that records whether a schedule, an override, or a specific user triggered it.

Beyond the schedule: recommendations, rightsizing, and showback

Scheduling is the fastest lever, but it is one of several. ZopNight ships 490 built-in audit rules across AWS (216), GCP (127), and Azure (147) that flag idle, oversized, and orphaned resources, and each recommendation shows the current monthly cost next to the estimated optimized cost so you act on the largest first. 124 of those recommendations are wired to act end to end, 28 one-click and 96 guided: one-click actions run immediately behind an admin-approval gate, and guided actions add a type-to-confirm review so you check the change before it lands. You mark a recommendation applied once you act, or dismiss the ones that do not fit.

Idle detection reads CPU, network, and connection metrics over a rolling window to separate a genuinely idle resource from one with real but intermittent traffic. Rightsizing is guided and computed from measured utilization over a real window, never a flat 24/7 assumption, so the projected figure matches the bill you actually see. For steady-state fleets, VM autoscaling runs in one of three modes derived from the credential’s permissions: monitor, recommend, or autopilot.

What is left after optimization gets attributed rather than hidden. Showback splits shared cost across owning teams and rolls up by cloud tag, GCP label, or Azure tag, with a Sankey cost-flow view that traces spend across provider, account, type, and team and a savings overlay that points straight at the reclaimable flows. A daily anomaly job writes root-cause markers onto the cost trend, an instance resize, a new resource, a reservation expiry, a failed schedule, so a spike explains itself instead of prompting a manual hunt. And 43 read-only tools expose the same data to an AI assistant over MCP, so you can ask an assistant in Claude, Cursor, or Codex for the same numbers.

Best practices that keep the savings

A few habits separate teams that hold onto the savings from teams that watch them drift back:

• Start with non-production and prove it there. Development, staging, QA, and demo environments carry almost no risk and the largest idle share, so they are the right place to build confidence before anyone considers production.
• Schedule by group, not by hand. Bundling an environment into a group like “staging” means one cadence covers every resource in it, and resources you add later inherit the schedule instead of being quietly forgotten.
• Use overrides instead of disabling schedules. When a late deploy needs a box overnight, a time-boxed override with a written reason keeps the schedule intact and expires on its own, so a one-off exception never becomes a permanent leak.
• Watch the audit trail and notifications. Every start, stop, and failure is logged and can post to Slack, Teams, or Google Chat, so a failed action is visible the moment it happens rather than discovered on the next invoice.
• Treat it as an operating rhythm, not a cleanup. The teams that keep the bill down review recommendations on a cadence and let the automation run continuously, instead of a one-off spring-clean that snaps back the moment attention moves on.

Getting started

Getting started is intentionally low-stakes:

• Connect your cloud provider with a read-only role. Nothing is scheduled or changed at this stage.
• Let ZopNight discover your non-production resources and review exactly what it found, filtered by account, region, and status.
• Create a schedule in your timezone and attach the non-production resources or groups you want it to cover.
• Watch the first cycle run, with Slack, Teams, or Google Chat notifications on every start, stop, and failure, then layer in idle cleanup and guided rightsizing.

Production stays excluded by default throughout, and because discovery and recommendations are read-only, you can prove the value before you enable a single action.