Archived listing / no verified MCP endpoint/Communication

Dibatto listing

No MCP endpoint is published. This listing is retained for reference.

Dibatto exposes a Studio REST API for reviewing owned shows, rundowns, the episode library, episode desks, transcripts and wrap progress, and for preparing rundowns or private episode drafts. It is not a documented MCP server. The API is included with an active Studio plan: create a connection under Plan and credits > API connections, choose permissions and a 7, 30 or 90 day expiry, and send the key in the x-api-key header over HTTPS. The key is shown once and is scoped to the account.

Archived listingNo verified MCP endpoint is published. This page is retained for reference only.Official docs
Source checked Nov 12, 2026 No MCP endpoint Reviewed 2026-11-16
About

Where it fits

Podcast producers on a Dibatto Studio plan who want an agent or script to review recordings and prepare drafts through the REST API.

  • List owned shows and their rundowns.
  • Read episode transcripts and wrap progress.
  • Prepare a private episode draft from an owned show.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Dibatto documentationhttps://dibatto.com/developers