Your data. Your chosen assistant.

Technology spend intelligence beyond the dashboard.

Cloud Ctrl connects cloud, AI and service spend with ownership, budgets and available pricing context. Work in the portal, share reports and alerts, or bring that context into your chosen AI agent through MCP.

Book a demo Read MCP setup docs (opens in a new tab)

MCP is tenant-scoped and read-oriented; it cannot change budgets or cloud infrastructure.

From connected spend and Cloud Ctrl context to the interfaces your team chooses
Connected spendCloud · AI usage · custom services
Cloud Ctrl contextOwnership · allocation · budgets · forecasts · pricing
Portal, reports & alerts
In-product Copilot
Your assistant via MCP
Data, context, interface

Give every answer a better starting point.

An agent can be useful only if the underlying question is grounded in the right data and business context. Cloud Ctrl does that work for the interfaces your team uses.

  1. 01

    Connect the data

    Bring supported cloud billing, AI service usage and custom service costs into one reporting model. Available detail and refresh timing depend on each connection.

  2. 02

    Add business context

    Map spend to owners, customers, products and cost centres. Compare trends and forecasts with budgets, and include customer pricing where configured.

  3. 03

    Put it to work

    Explore in the portal, share scheduled reports and alerts, ask the in-product Copilot, or connect your own assistant through MCP.

More than one way in

The same context. Different ways to work.

MCP extends access to your own agent; it does not replace Cloud Ctrl’s portal, reporting or in-product assistant.

For your team

Portal

Investigate usage, ownership, forecasts and budgets in Cloud Ctrl. Schedule reports and use alerts to bring changes to the right people.

Inside Cloud Ctrl

In-product Copilot

Ask questions in the product using its connected cost context. This is Cloud Ctrl's own assistant, not a requirement to change the assistant your team already uses.

In your chosen client

MCP for your assistant

Connect an MCP-capable client such as VS Code, Claude Code or Cursor to tenant-scoped, read-oriented cost tools. You choose and configure the client.

An organisation’s question

“Why is this month’s spend off plan?”

A finance lead asks their connected assistant to prepare for a variance review. These read-oriented MCP tools give the team a traceable investigation path; they do not make a decision on its behalf.

  1. 01get_import_history

    Check the source

    Start with import history so the team knows which connected billing data has arrived before drawing conclusions.

  2. 02get_top_movers

    Find the change

    Identify the services or accounts driving a period-on-period movement, then decide what needs a closer look.

  3. 03get_spend

    Inspect the spend

    Look at spend over the relevant period and available ownership or allocation context to discuss the variance with the responsible team.

  4. 04get_budgets_at_risk

    Review the plan

    Check budgets at risk and use the evidence to prepare a finance conversation. People still decide whether a budget or workload should change.

For service providers

Bring one customer’s story to the service review.

A provider team can connect its assistant for a specific customer tenant, review that tenant’s spend movement and budgets at risk, then prepare questions for the customer. MCP requests use a tenant-specific endpoint and require read access to that tenant’s data; this is not a cross-customer query or an automatic change to customer budgets.

Explore the service-provider platform
A practical integration boundary

Your client connects. Access stays scoped.

Cloud Ctrl provides a stateless Streamable HTTP MCP endpoint at https://mcp.cloudctrl.com.au/mcp/{tenantId}. Configure your MCP-capable client with OAuth or an API key. Access to data is checked for the requested tenant.

See the MCP setup guide (opens in a new tab)

Tenant-specific read access

Each endpoint identifies a tenant; access to that tenant’s data is checked before read-oriented tools return it.

Useful investigation tools

Explore spend, forecasts, budgets, recommendations, reservations, Watchdog signals and data freshness where available.

People remain in control

Approval-gated write tools are not exposed through this adapter. Your assistant cannot change budgets or provider infrastructure through MCP.

Three different questions

Know what each capability is for.

Understand AI services

AI Cost Management

Track supported AI provider usage and costs alongside cloud spend, with attribution detail where the provider supplies it.

Explore AI costs
Understand cloud resources

Cloud Intelligence

Use AI-assisted explanations to interpret cloud resources and costs, then review that context with the people responsible.

Explore Cloud Intelligence
Use your own assistant

MCP access

Let a client you choose query permitted tenant cost context through Cloud Ctrl’s read-oriented MCP tools. It is an interface, not a new source of AI usage data.

Explore MCP setup (opens in a new tab)
Keep your agent, add the context

Build the experience your team wants. Don’t rebuild the spend model underneath it.

Connecting bills is only the beginning. Maintaining imports, allocations, budgets, forecasts and customer pricing context is ongoing work. Cloud Ctrl gives your team a product for that work and a documented interface for your chosen assistant; you still decide how the assistant is configured, what to ask and what action to take.

Book a demo