Skip to main content

MXMZ Graphics

Learn how to use MXMZ Graphics with the Cuez Automator

What is MXMZ Graphics?

MXMZ Graphics is a web-based graphics solution for creating and controlling customizable overlays from anywhere. Once the integration is configured, MXMZ connects to your playout service so you can trigger, clear, and monitor graphics on a chosen output without leaving Cuez.


More information about MXMZ Graphics on their website.

The MXMZ Graphics integration supports two workflows:

  • Automator device - connects MXMZ as a controllable device in Cuez Automator. Best for automated, cue-driven playout tied to your rundown.

  • MOS plugin - adds MXMZ as a media library so operators can browse and select MXMZ graphics from within the rundown. Best for manual, operator-driven graphics.

Both workflows talk to the same MXMZ playout service. Whichever you choose, start by confirming your region endpoints and setting up an output first.


Prerequisites

Before you begin, make sure you have the following in place:

  • Cuez access - for the MOS plugin you need owner rights (Organization settings are owner-only); for the Automator device you need permission to add devices.

  • MXMZ account access - you can log in to the MXMZ web interface at graphics.mxmz.io.

  • An MXMZ playout service that is provisioned and reachable.

  • MXMZ API credentials - a Secret API Client ID and an API Secret Bearer Token issued for your service.

  • At least one output on the playout service, or permission to create one.

  • A graphics package published to your MXMZ account.

  • Your MXMZ region - EU or US, determined when your service was provisioned.

Set up your MXMZ output

Before configuring Cuez, set up an output to play out on in the MXMZ web interface at graphics.mxmz.io. Go to the Operator tab, click your initials at the bottom left, and select 'Admin Dashboard'. Then open 'Outputs' (Manage outputs).

Click 'Create output' to add a new output, or open an existing one. Each output exposes PGM, Preview, and Sandbox URLs. You do not need to copy any IDs — you simply select the output by name when configuring playout in Cuez, and the rest is managed automatically.

Tip: Use the PGM output for on-air playout and Sandbox or Preview while testing, so a misfire never reaches air.

Workflow 1 - Automator device

Adding MXMZ Graphics to the Automator

In the top right corner of the Automator, we see 'Devices' - this can be either in red or green depending on the status of the configured devices. Click it and select 'Add device'.

Next, select 'MXMZ Graphics' from the 'Device type' dropdown list, then give it a name.

Once the device is selected and given a name, we will see all fields needed to configure it so it can be used with the Automator.

Basic device configuration

On the 'Config' tab, you can enable or disable the device and enter the following settings:

  • 'Playout Service URL' - the Playout Service URL for your region (see below).

  • 'Package Manager URL' - the Package Manager URL for your region (see below).

  • 'Client ID' - your Secret API Client ID.

  • 'API Key' - your API Secret Bearer Token.

Once all fields have been filled in, click outside of the field. The MXMZ Graphics 'device' will now show as 'Online' in green, meaning it is ready to be used with the Cuez Automator.

⚠️ Existing MXMZ users: After updating to Automator Stable v1.30.0, you will need to update your MXMZ Graphics device configuration to add the new 'Playout Service' and 'Package Manager' fields. The device will not connect correctly until these fields are populated. Select the URLs that match your MXMZ region from the list below.

Important: Treat the Client ID and API Key as sensitive credentials. Do not share them or paste them into tickets or chat.

MXMZ service endpoints

Your MXMZ service is hosted in the region it was provisioned in. Use the Playout Service URL and Package Manager URL for your region:

EU Production

  • Playout Service: https://playout-service.mxmz.io

  • Package Manager: https://package-manager-api.mxmz.io

US Production

  • Playout Service: https://playout-service.use2.mxmz.io

  • Package Manager: https://package-manager-api.use2.mxmz.io

EU Pre-Production (Development Partners only)

  • Playout Service: https://playout-service.mxmz.dev

  • Package Manager: https://package-manager-api.mxmz.dev

Where to find your MXMZ Client ID & API Key

Log in to your MXMZ account and go to your settings. In there you should be able to find your Client ID (36 characters) and the API Key (around 344 characters).

Media handling / Downloader tab

If you are using the MOS workflow, the device also needs to know which rundown media to handle and where to download it. Open the device 'Downloader' tab and configure it as follows:

  • Tick 'Handle Media' so the device handles media coming from the rundown.

  • Under 'Download media fields', choose 'Download locally' or 'Send to S3 Bucket', then set the 'Download folder' (a target reachable by both the Automator and the device) and, if needed, the 'Device media folder' (the same path from the device viewpoint).

  • Set the download options as required: 'Downloading enabled', 'Keep filenames', 'Download media instance' (for example Original), and 'Automatically delete files' (for example Never).

  • Click 'Add media field' and select the Block and Field that carries the MOS media - for example Block GRAPHIC, Field Media. This is the field referenced as GRAPHIC.Media in the Execute MOS trigger.

Configuring block triggers

In the Automator, configure each block in its 'Triggers Configuration' on the 'On Cue' tab - more general information on that in this article. There are two ways to drive MXMZ graphics from a block:

Direct function path

Add individual MXMZ functions to the On Cue trigger. Select the desired output, then the graphics package and the graphic required, and map your Cuez fields to the graphic data fields.

Note: All graphics must be in the same graphics package on one output.

Available functions

Graphic In

The 'Graphic In' function brings the graphic on air on the selected output.

Graphic Out

The 'Graphic Out' function takes the graphic off air.

Preview In

The 'Preview In' function brings the graphic up on the preview output.

Preview Out

The 'Preview Out' function takes the graphic off the preview output.

Clear

The 'Clear' function clears the graphic on the current block.

All Graphics Out

The 'All Graphics Out' function takes all graphics off the output at once.

Update

The 'Update' function sends updated field values to the graphic without taking it off air.

Workflow 2 - MOS plugin / media library

The MOS plugin adds MXMZ Graphics to Cuez as a media library, so operators can select and configure MXMZ graphics on any graphics block in the rundown. You add it once at the organisation level - it is then available across your projects.

Step 1 - Get the MOS plugin URL

In a browser, open http://renderer.mxmz.io/mosplugin/config. Set the Graphics package, choosing the graphics package you want the plugin to use. The MOS ID and NCS ID fields are pre-filled.

Copy the generated URL shown at the top of the page and append &origin=https://us.browz.tv to it. The final URL should look like:

https://renderer.mxmz.io/mosplugin?mosID=mxmz.mos&ncsID=nrcs_id&tb=50&origin=https://us.browz.tv

Step 2 - Create the media library in Cuez

In the Cuez App Dashboard, open the projects/organization dropdown (top left) and choose 'Organization settings' (owners only). Go to 'Media library' and click 'Add media library'.

Complete the following fields and click 'Save changes':

  • 'Name' - a name for the library, for example MXMZ MOS.

  • 'Type' - select Mxmz.

  • 'Mos plugin URL' - paste the URL you copied in Step 1.

The MXMZ MOS library will now appear in your Media library list and is available to your projects.

Step 3 - Add a graphic to a rundown block

With the media library in place, operators can add MXMZ graphics directly to graphics blocks. On a graphics block, add a media field (for example 'Add image'). Open the media field and at the top left, set 'Current library' to MXMZ MOS.

Choose the Graphics Package, select the graphic you want (for example a lower third or full-screen image), and configure its fields in the panel. Confirm to add the configured graphic to the block.

Troubleshooting

Device will not connect / Ping not OK

Re-check the Client ID and API Key, and confirm the Playout Service and Package Manager URLs match your region.

No graphics in the MOS library or block panel

In the MOS plugin config (renderer.mxmz.io/mosplugin/config) or the block panel, make sure a graphics package is selected.

Graphics do not appear on air

Create or activate an output in the Outputs panel and make sure the correct output is selected in the trigger or panel.

Media is not downloading

On the device Downloader tab, tick 'Handle Media' and confirm the correct Block and Field mapping is set.

MXMZ not in the Devices dropdown

The integration may not be enabled for your Cuez workspace. Contact your Cuez administrator or get in touch with us at support@cuez.app.

Cannot open Organization settings

Organization settings are owner-only. Ask an owner to add the MXMZ MOS media library, or ask them to grant you owner rights.

💡 MOS functions (Mos Graphic In/Out, Mos Preview In/Out) require Automator Stable v1.30.0 or above (released 14 July 2026). Download the latest release from https://download.cuez.app/automator/.

Did this answer your question?