# Developers

Drive Mestra from your own systems and agents with the API, MCP server and webhooks.

<DevHero />

Mestra has three ways in for your own systems and agents. The API and MCP use the same [keys](https://withmestra.com/docs/api/authentication/), made in Mestra by an owner or a team member.

- **[API](https://withmestra.com/docs/api/):** call Mestra from your own systems. Read campaigns, formats, brands and runs, and, with the right key, change them. The [reference](https://withmestra.com/docs/api/) lists every endpoint.
- **[MCP](https://withmestra.com/docs/mcp/):** connect an AI agent. It gets ready-made [tools](https://withmestra.com/docs/mcp/tools/) for the same work.
- **[Webhooks](https://withmestra.com/docs/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](https://withmestra.com/docs/developers/sdk/) to install it and make your first edit.

Building for screens that run Mestra Player? Its routes are in the [API reference](https://withmestra.com/docs/api/) (see the [Mestra Player API overview](https://withmestra.com/docs/player/api/)), and its [webhook events](https://withmestra.com/docs/player/webhooks/) 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](https://withmestra.com/talk-to-us/?role=developer).
