> This page is for Docs.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://zuora.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://zuora.ferndocs.com/_mcp/server.

# Manage meters with Mediation MCP

> Use this reference to discover, validate, create, update, import, export, and duplicate Mediation meters.

Use this reference to discover, validate, create, update, import, export, and duplicate Mediation meters.

The `manage_meters` tool manages meter definitions and configuration. It provides 19 operations for event schemas, event stores, connections, task graphs, validation, and meter lifecycle actions.

Start with `meter_guidance` to retrieve workflows and tips. Do not invent operation parameters. Use the guidance operation or the tool schema to determine the supported parameters.

## manage_meters operations

| Operation                 | Access     | Purpose                                                                       |
| ------------------------- | ---------- | ----------------------------------------------------------------------------- |
| `meter_guidance`          | Read       | Retrieve workflows and tips. Start here.                                      |
| `list_meters`             | Read       | List available meters.                                                        |
| `get_meter`               | Read       | Retrieve a meter and its full task graph.                                     |
| `list_event_definitions`  | Read/write | List event schemas.                                                           |
| `create_event_definition` | Read/write | Create an event schema.                                                       |
| `update_event_definition` | Read/write | Update an event schema.                                                       |
| `list_event_stores`       | Read/write | List event stores.                                                            |
| `create_event_store`      | Read/write | Create an event store. An event store can be used as an optional lake target. |
| `update_event_store`      | Read/write | Update an event store.                                                        |
| `list_connections`        | Read       | List connections, including S3, Kafka, Snowflake, and HTTP connections.       |
| `list_data_types`         | Read       | List supported data types.                                                    |
| `get_meter_settings`      | Read       | Retrieve meter settings and unit-of-measure context.                          |
| `get_task_metadata`       | Read       | Retrieve operator and task schemas.                                           |
| `validate_meter`          | Read       | Validate meter tasks without saving them.                                     |
| `create_meter`            | Write      | Deploy a meter with version 0.0.1.                                            |
| `update_meter`            | Write      | Replace the tasks for a meter.                                                |
| `export_meter`            | Read/write | Export a meter for backup or migration.                                       |
| `duplicate_meter`         | Read/write | Clone a meter.                                                                |
| `import_meter`            | Read/write | Import a meter.                                                               |

## Custom meter tasks

Custom meters use tasks with the following properties:

* `nodeType`: `SOURCE`, `PROCESSOR`, or `SINK`.
* `operatorType`.
* `predecessors`.
* `metadata`.

## Updating a meter

An `update_meter` operation replaces the full task set. Before you update a meter, retrieve the current definition and validate the complete replacement task graph. Obtain approval before you execute the update.