Skip to main content

​
CloudX MCP

CloudX provides a hosted Model Context Protocol server for reporting, auction inspection, configuration, and documentation workflows. It lets AI clients query CloudX data, safely manage inventory configuration, and search CloudX docs directly. Server URL:

Installation

Install the CloudX ChatGPT app or add CloudX MCP to Claude Code, Cursor, and Codex.

Tool Reference

Exact tool names, parameters, enums, and response shapes.

Examples

Real prompts and payloads you can adapt directly.

​
When To Use MCP

Use CloudX MCP when you want an AI client to:
  • compare bidder, app, ad unit, and dashboard performance
  • build custom report breakdowns and inspect A/B test results
  • filter reports by country, platform, test traffic, or app bundle
  • export tabular rows for downstream analysis
  • investigate individual auctions, rounds, bids, and impression-level revenue data
  • inspect, validate, edit, and publish inventory configuration
  • search CloudX documentation before answering product or integration questions
  • answer reporting questions in natural language and still use exact CloudX data

​
Available Tools

  • GetReportDashboard
  • GetReportBreakdown
  • GetReportBidders
  • GetReportApps
  • GetReportAdUnits
  • GetReportExport
  • GetReportABTest
  • GetAuctionList
  • GetAuctionShow
  • GetAuctionRounds
  • GetAuctionBids
  • GetConfigShow
  • GetConfigValidate
  • GetConfigHistory
  • PostConfigEdit
  • PostConfigPublish
  • SearchDocs

​
Supported Clients

This guide includes installation steps for:
  • ChatGPT
  • Claude Code
  • Cursor
  • Codex

​
Shared Concepts

  • start_time and end_time are Unix seconds in UTC and are required by most reporting and time-range auction tools.
  • country is an ISO-2 filter such as US or GB.
  • device_os must be exactly iOS or Android.
  • test_mode accepts production, test, or all where supported and defaults to production.
  • Read-only tools require the relevant reports:read, auctions:read, or configuration:read permission. Configuration mutations require configuration:write.
  • PostConfigEdit ordinarily creates or updates a draft. PostConfigPublish validates a draft before making it live.
  • SearchDocs uses a required body.query string and does not use reporting filters.