Model Context Protocol

The Brandscast MCP server

Brandscast exposes a full Model Context Protocol (MCP) server, so any AI agent can run your internal audio channel in plain language — list audio, publish episodes, manage listeners and pull analytics. Claude is just one of the clients that can connect.

An open endpoint for your audio channel

MCP is the emerging open standard for connecting AI models to external systems. Brandscast implements it as a hosted server, so any MCP-compatible client can authenticate and operate your account through a typed set of tools — no scraping, no custom integration, no glue code.

Because it speaks a standard protocol, the same server works with Claude, with your own internal agents, and with anything you build on top of the Anthropic API. You connect once and get programmatic, natural-language access to everything in your private audio channel.

Server details

Endpoint
https://mcp.brandscast.com/api/mcp

Transport
Streamable HTTP

Auth
OAuth 2.0 or personal API token

Standard
Model Context Protocol

What agents can do with it

Connect an agent and it can operate your channel end to end, the same way a member of your team would — but on demand, in any conversation or automation.

Run your channel

Ask an agent to publish a new episode, look up an audio or its episodes, and keep your internal feed moving without opening the dashboard.

Keep membership in sync

Add and remove listeners as people join or leave, straight from your own automations — onboarding flows, HRIS, or a quick natural-language request.

Pull analytics anywhere

Bring listening analytics into weekly digests, reports or dashboards — let an agent fetch the numbers and write them up for you.

Available tools

The server exposes a typed toolset. Each tool maps to a single, auditable action against your account.

ToolWhat it does
list_podcastsReturns all audio in your account
get_podcastReturns details for a specific audio
list_episodesLists episodes for an audio
get_episodeReturns details for a specific episode
publish_episodePublishes an episode
list_membersLists listeners for an audio
get_memberReturns details for a specific listener
add_memberAdds a listener to an audio
remove_memberRemoves a listener from an audio
get_statsReturns listening analytics for your account

Ways to connect

The same server is reachable from several kinds of client. Pick whichever fits how your team already works.

Claude connector

In Claude, open Settings → Connectors, find Brandscast and connect with OAuth. Then use Brandscast tools in any conversation — no setup beyond signing in.

Any MCP client

Point any MCP-compatible client at https://mcp.brandscast.com/api/mcp and authenticate with a personal API token (bcast_…) from your Brandscast settings.

Your own agents

Call the server directly from the Anthropic API or any agent framework via its mcp_servers configuration, and build Brandscast into your own internal tooling.

Authentication and security

Access is authorised per user. The Claude connector uses OAuth 2.0; everything else uses personal API tokens, which are stored hashed (SHA-256), scoped to your account, and can be revoked at any time. Your Brandscast credentials are never shared with Anthropic or any model provider, and every tool call runs with the same permissions as the user who authorised it.

Requirements

You need an active Brandscast account on any paid plan (Starter, Growth or Pro). No technical setup is required to use the Claude connector — it works out of the box once you authenticate. Connecting other clients only takes a personal API token from your settings.

Support

Having trouble connecting, or want a tool the server doesn't expose yet? Email us at hello@brandscast.com and we will help you get set up.

Frequently asked questions

What is the Brandscast MCP server?

It is a hosted Model Context Protocol server that lets any compatible AI agent manage your Brandscast account — audio, episodes, listeners and analytics — through a typed set of tools, using natural language or code.

Do I have to use Claude?

No. Claude is one supported client, but the server speaks the open MCP standard, so any MCP-compatible client or your own agents built on the Anthropic API can connect to the same endpoint.

How do I authenticate?

The Claude connector uses OAuth 2.0. Other clients authenticate with a personal API token generated in your Brandscast settings. Tokens are hashed, scoped to your account and revocable at any time.

What is the server URL?

https://mcp.brandscast.com/api/mcp

Put your internal audio in reach of every agent

Start your channel, connect it to Claude or your own tooling, and manage it in natural language.

Start trial

No credit card required.