GetReportDashboard
Summary KPIs plus chart data
LABSCO SUMMARY
Mostly reading, but two tools change what runs in production.
Most of the surface answers questions: how US iOS traffic did last week, which bidders win, which banner placements fill worst, what happened in one auction. PostConfigEdit and PostConfigPublish are different. Ordinary edits land as a draft, and publishing validates the draft before it goes live, but A/B test changes made through PostConfigEdit publish immediately, and an agent with configuration:write can change your live inventory setup. Give that permission only to the connection that needs it.
What it is
CloudX's hosted server for its mobile ad monetization platform. The address says provisioning, but the tools are about reporting, auctions and inventory configuration for your apps, plus a search over CloudX's own documentation.
What you get
Five groups of tools: eight for reporting (dashboard KPIs, custom breakdowns, bidders, apps, ad units, raw export, A/B tests, and Total Publisher Revenue across CloudX and your connected mediation platforms), four for inspecting auctions, rounds and bids, five for showing, validating, editing and publishing inventory configuration and reading its recent history, six for Tasks — recurring prompts you can list, create, change, delete or run at once — and SearchDocs for CloudX's documentation.
Requirements
A CloudX account, signed in over OAuth when you connect. Read tools need reports:read, auctions:read or configuration:read on that account; PostConfigEdit and PostConfigPublish need configuration:write. Task tools need the Tasks feature: reading Tasks needs configuration:read, and creating, changing, deleting or running them needs editor access and configuration:write. CloudX documents setup for ChatGPT (as a published app), Claude Code, Cursor and Codex.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Checking how a slice of traffic performed
Ask for dashboard revenue, fill rate and CTR for, say, US iOS production traffic over a week, then break it down by country or app.
02
Finding out why revenue moved
Compare bidders by revenue, bid rate and win rate, then open individual auctions and their bids to see what happened.
24 tools
Listed in project docs. Your client may show a different list.
GetReportBreakdown
Custom grouped report rows
GetReportBidders
Bidder-level performance
GetReportApps
App-level performance
GetReportAdUnits
Ad unit-level performance
GetReportExport
Raw export rows in JSON shape
GetReportABTest
Control and test-variant performance
GetReportTotalRevenue
Total Publisher Revenue across CloudX and connected mediation platforms
GetAuctionList
Recent auctions matching filters
GetAuctionShow
One auction with optional related details
GetAuctionRounds
Auction rounds or aggregate round metrics
GetAuctionBids
Bid and non-bid rows
GetConfigShow
Live, published, or draft configuration
GetConfigValidate
Server-side config validation
GetConfigHistory
Recent config history
PostConfigEdit
Typed inventory configuration edits
PostConfigPublish
Validate and publish a draft
ListScheduledAgents
List accessible Tasks, newest first
GetScheduledAgent
Get one Task
CreateScheduledAgent
Create a recurring Task
UpdateScheduledAgent
Change a Task
DeleteScheduledAgent
Delete a Task
RunScheduledAgent
Queue an immediate run
SearchDocs
CloudX documentation search
BEFORE YOU INSTALL
What to know first
Tools you get
24 tools named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- A CloudX account with reports:read, auctions:read or configuration:read permission; configuration:write to edit and publish configuration
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://provisioning.cloudx.io/mcpRequirements
- OAuth 2.1 (Bearer token)
MCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add --transport http cloudx https://provisioning.cloudx.io/mcpThen open Claude Code in your project; if CloudX asks you to sign in, run /mcp and complete the browser sign-in.
Cursor
CURSOR · JSON
{
"mcpServers": {
"cloudx": {
"url": "https://provisioning.cloudx.io/mcp"
}
}
}Put this in .cursor/mcp.json for one project, or ~/.cursor/mcp.json for all of them.
Codex
CODEX · TERMINAL
codex mcp add cloudx --url https://provisioning.cloudx.io/mcpChatGPT
Sign in to ChatGPT on the web, then open the CloudX ChatGPT app.
Click Connect and complete the CloudX authorization flow.
In a new conversation, mention @CloudX, or click + → More and pick CloudX.
