Build on Meetily

What "local" means here

The Agent API talks to a Meetily desktop app that is already running on this machine - it is not a hosted service. It listens on loopback (127.0.0.1) by default. "Nothing leaves the machine" is true for those loopback calls; opting into LAN access, or approving a webhook destination, sends data to a target you specifically chose. There is no hosted relay and no NAT traversal - only your own LAN or your own VPN.

What it is

The Agent API is a local HTTP API that a running Meetily Pro instance exposes so your own code, scripts, or an AI assistant can drive it: start and stop recordings, read transcripts and summaries, manage webhooks, and more. It is Pro-gated and off by default - you turn it on in Settings > Integrations (the toggle there is labeled Automation API; "Agent API" is the capability, "Automation API" is the in-app switch), and it only serves requests while Meetily itself is running.

Availability

The Agent API is a Meetily Pro feature today. Support for the Community (open-source) edition is coming soon.

There are three ways to reach it:

HTTP API - call the endpoints directly, from any language that can make an HTTP request.
meetily-pro CLI - the supported command-line client, for scripting and quick calls.
MCP server - lets an MCP-compatible AI assistant use Meetily as a tool.

Get started

Enable & connect

Turn on the Automation API, mint a key, and pair a remote client.

Quickstart

Locate your token and make one authenticated call.

CLI

Drive Meetily from the command line with meetily-pro.

MCP server

Connect an MCP-compatible assistant to your meetings.

Webhooks & SSE

Get notified when a recording, job, or summary finishes.

Meetily APIs

The OpenAPI manifest, error codes, and route groups.

Local-first, LAN-optional

Meetily's API surface follows the same privacy posture as the rest of the app. The loopback listener never touches your network. Enabling LAN access, or approving a webhook destination, sends data only to a place you specifically approved - there is no hosted relay and no NAT traversal. And the API is not a background service: quit Meetily, and it stops serving immediately.