Skip to content

Developers

Developers

Under the hill after dark: the ground cut away to show a lamp-lit burrow below a screen. A ringtail possum stands by a switchboard of jacks and coloured patch cords, the Player box has plugged its own tail in, and slips hang on a rail of hooks with a bell on a string. Shelves of manuals, a kettle, a round green door ajar on the hillside.

Mestra has three ways in for your own systems and agents. The API and MCP use the same keys, made in Mestra by an owner or a team member.

  • API: call Mestra from your own systems. Read campaigns, formats, brands and runs, and, with the right key, change them. The reference lists every endpoint.
  • MCP: connect an AI agent. It gets ready-made tools for the same work.
  • Webhooks: hear about what happens in Mestra as it happens. Mestra sends a signed message to your address when a run finishes, a review is decided and more.

SDK

The JavaScript SDK, @withmestra/sdk on npm, is a typed client for the API with helpers for editing sizes and masters. See the SDK guide to install it and make your first edit.

Building for screens that run Mestra Player? Its routes are in the API reference (see the Mestra Player API overview), and its webhook events are listed separately.

Start by turning the API on: an owner does that in Developer > API and MCP.

Building an integration and need something that isn’t there? Talk to us.