Zuora Mediation Model Context Protocol
Learn how Mediation MCP helps you design, operate, monitor, and troubleshoot Mediation pipelines through an AI assistant.
Zuora Mediation turns raw usage events into billable usage records for Zuora Billing. A meter is a streaming pipeline with the following structure:
SOURCE → PROCESSOR(s) → SINK
- SOURCE reads usage events from a system such as Amazon S3, Kafka, or an HTTP endpoint.
- PROCESSOR transforms the events through operators, for example enriching them with subscription data or aggregating them.
- SINK writes the resulting billable records to their destination, such as Zuora Billing.
Mediation MCP exposes Mediation through an AI assistant that supports the Model Context Protocol (MCP). You can use an MCP-compatible client, such as Cursor, Claude Desktop, Claude Code, VS Code Copilot Chat, or Gemini CLI.
The assistant uses the same OAuth identity and permissions as the Mediation user interface and REST APIs. Instead of navigating the Meters UI or calling each REST API by hand, you can ask your AI assistant to list meters, design pipelines, start and stop runs, investigate failures, and export audit data. The assistant carries out these tasks through 40 operations across three tools.
Mediation MCP is part of the broader Zuora Developer MCP, also called Zuora Remote MCP.
What you can do
| Capability area | Examples |
|---|---|
| Discover | List meters, event schemas, event stores, and connections; read tenant settings |
| Author | Create event definitions, event stores, and custom meter pipelines; validate a pipeline before saving it |
| Operate | Start and stop runs, check run status, browse run history and summaries |
| Investigate | Retrieve error audit records, operator summaries, and event store query results; check prefetch status |
| Export | Create audit export jobs and download failure samples for reconciliation |
| Migrate | Export, duplicate, and import meter definitions |
Related systems
| System | Scope |
|---|---|
| Usage management (manage_usage) on the same MCP server | Creating, reading, updating, and deleting Zuora Billing usage records. This is downstream of Mediation and does not configure pipelines. |
| Audit browsing versus run management | Audit records are browsed and exported only through the audit tool. Run control lives in the run tool. |
Scope
Mediation MCP is sufficient for the following:
- Creating and managing meter definitions
- Starting, stopping, and monitoring runs
- Reviewing audit records and exporting them
- Prefetch operations and event store queries
- Operational questions about your own entity, when your credentials allow it
Contact your Zuora support team when:
- Authentication fails or the data returned belongs to an unexpected entity. Verify the Zuora-Entity-Ids header first.
- A run shows missing or inconsistent telemetry that the MCP tools cannot explain.
- You need a root-cause analysis that combines logs, metrics, and tickets across systems.