Dibatto

npx add-mcp 'https://dibatto.com/mcp'

Your studio, connected.

Prepare the next conversation and review your recordings from a tool you trust.

Connect your account

API access is included with an active Studio plan. In Plan and credits → API connections, name the connection, choose its permissions and an expiry of 7, 30 or 90 days, then create a key. Copy it when shown; it cannot be retrieved later.

Send the key in the x-api-key header over HTTPS. Keep it in the connecting tool’s secret store. Each request is limited to your own account and checks your current plan. Revoke a key in Dibatto to disconnect the tool immediately. You may still revoke keys after a downgrade.

GET https://dibatto.com/api/shows
x-api-key: <your-private-key>

Download the OpenAPI 3.1 schema for full request and response fields.

Choose only the access you need

• studio:read: read owned shows, rundowns, the episode library, episode desks, transcripts and wrap progress.
• rundown:prepare: generate a rundown using an existing show’s beat, co-host and sources.
• episode:prepare: create a private draft using an owned show and, optionally, its rundown.

Recording with the AI co-host, uploading media, starting a wrap, publishing, changing payments and administering an account stay in the Dibatto app. Review generated claims and the recording before deciding what to publish.

Supported operations

Operation	Permission
GET /api/shows List your shows	studio:read
GET /api/shows/{id} Read a show	studio:read
GET /api/shows/{id}/rundown Read a show rundown	studio:read
POST /api/shows/{id}/rundown Generate a source-backed rundown for an existing show	rundown:prepare
GET /api/episodes List and search your episode library	studio:read
GET /api/episodes/{id} Read an episode desk, notes and review results	studio:read
GET /api/episodes/{id}/transcript Read an existing episode transcript	studio:read
GET /api/episodes/{id}/wrap Read existing wrap progress	studio:read
POST /api/episodes Create a private episode draft for an owned show	episode:prepare

A preparation workflow

1. List shows and select one the owner wants to prepare.
2. Read its current rundown. If requested, generate one with POST /api/shows/{id}/rundown and an empty JSON object. The existing daily rundown is reused by default.
3. Create a draft with POST /api/episodes and JSON fields show_id, optional rundown_id, and optional title. The draft remains private.
4. Return the episode to its owner for recording in Dibatto. After recording and wrapping in the app, read the transcript and review results through the API.

Draft creation is not idempotent. If a request times out, check the episode library before retrying so you do not create a duplicate.

Limits and errors

Each key allows 60 requests per minute. Existing account limits also apply: 12 new rundown generations per hour, at most 6 forced regenerations per hour, 30 draft creations per hour and 25 open drafts. Rundown generation supports the last 45 days through tomorrow. Reading older saved rundowns remains available.

Draft preparation does not start recording or spend an episode credit. Recording and wrap charges follow your plan in the app. A 401 means the key is invalid, expired, revoked or lacks permission; 402 means a plan or product limit; 403 means the action is unavailable; 404 means no owned resource; and 429 means a rate limit. Error bodies contain error.code and error.message.

For help, contact hello@dibatto.com. See the privacy policy, terms and plans.