Listenbox
Skip to article
Browse guides
On this page

Connect your agent to Listenbox with MCP

By Listenbox

Published · Updated

Should I use MCP or the CLI?

Use MCP when your agent supports remote MCP servers and you want to manage Listenbox from a conversation. Sign in through your browser; there is no CLI to install. Use the Listenbox CLI when your agent needs to upload a local recording or run YouTube synchronization on your computer. MCP can open the existing dashboard upload screen for you, but it does not transfer large media files through the conversation.

Connect your client

You need a Listenbox account and a client that supports remote MCP over Streamable HTTP with OAuth browser sign-in.

  1. Open your client's MCP server or connector settings.

  2. Add Listenbox with this server URL:

    https://mcp.listenbox.app

  3. Choose OAuth or browser sign-in if your client asks for an authentication method.

  4. Sign in to Listenbox in the browser that opens.

  5. Review the client, account, requested permissions, and return address. Approve only a connection you started yourself.

  6. Return to your agent and ask it to list your podcasts.

The server provides OAuth discovery. A client with configurable scopes can request listenbox:read for reading, or add listenbox:write to make changes. The consent screen shows the requested access. If your client asks for no scopes, the screen asks you to approve read and write access.

An example conversation starter:

List my Listenbox podcasts and the latest episodes in my interview podcast. Ask before changing or deleting anything.

Manage your podcasts

The server exposes separate tools for listing and creating podcasts, editing podcast details, listing episodes, changing episode order, managing collaborators, and importing an RSS feed. Deletion tools permanently remove episodes or podcasts; review those actions carefully before approving them in your client.

Your Listenbox permissions still apply. A connection does not turn a viewer into an editor or give a manager owner permissions. It can access podcasts across your teams and directly shared podcasts. Team member operations and RSS imports use the default team shown by auth_status; creating a podcast accepts an explicit team ID.

Lists return bounded pages. An agent should follow next_cursor or next_offset when it needs more results. RSS imports and deletions return a run ID immediately; the corresponding status tool reports progress or completion.

Upload a large recording

Ask your agent to open the upload page for the podcast. The episodes_upload_link tool returns that podcast's existing episode creation screen.

Open the link, select your audio or video file, and finish the upload in your browser. You can review the episode and choose when to publish it there. The video upload guide explains that workflow. Afterward, ask the agent to list the podcast's episodes to check its state.

Do not paste video bytes, upload credentials, or YouTube cookies into tool arguments. YouTube synchronization and its local cookie storage belong to the CLI or desktop app.

Disconnect or reconnect

Open MCP connections, find the client, and choose Disconnect. Its dedicated API credential is revoked, so it can no longer use your account through that connection.

Connections expire after 30 days. Start browser sign-in again from your client when you need to reconnect. If a read-only connection cannot make a change, reconnect with listenbox:write and review the new consent screen.

If sign-in cannot complete, check that your client supports remote OAuth and PKCE, then start a fresh connection. An expired consent page or an authorization code that has already been used cannot be reused.