Integration

Supercast integration

Supercast runs paid private podcast feeds. Read a channel's or network's episodes, subscribers, charges, subscription lifecycle events, episode listens, feed changes and churn, visit and conversion analytics; look up a subscriber by e-mail, uuid or customer id; activate a subscriber on a plan or deactivate one. Plans, payouts and channel settings are left to the dashboard. Authentication is a Bearer access token (a manual dashboard token or an OAuth token).

Connect Supercast How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Supercast.Built from the 14 Supercast tools below, on the connection you add once.

What you can do with Supercast

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Subscriber, 4 operations

create_subscriberCreate subscriberPOSTCreates, or reactivates, a subscriber on the current entity and issues their private feed.
deactivate_subscriberDeactivate subscriberDELETECancels the subscriber's subscription to the current entity and deactivates all of its feed tokens, so their private feed stops serving new episodes.
get_subscriberGet subscriberGETReturns a single subscriber of the current entity. `{id}` accepts a Supercast uuid, e-mail address, or `customer_id`.
list_subscribersList subscribersGETLists the current entity's subscribers, most recently subscribed first. For a network token this returns the subscribers of every channel in the network.

Episode, 2 operations

get_episodeGet episodeGETReturns a single episode belonging to the current channel.
list_episodesList episodesGETLists the current channel's episodes, newest first by insertion order. A channel must be in scope: use a channel token, or a network token plus `channel_subdomain`.

Charge, 1 operation

list_chargesList chargesGETLists the current entity's charges, newest first. For a network token this returns the charges of the network **and** all of its channels.

Churn event, 1 operation

list_analytics_churn_eventsList analytics churn eventsGETLists cancellation and save-attempt outcomes for the current entity, newest first.

Conversion, 1 operation

list_analytics_conversionsList analytics conversionsGETLists pre-aggregated **conversion** rollups for the current entity, newest bucket first.

Episode listener, 1 operation

list_episode_listenersList episode listenersGETLists the individual "this subscriber listened to this episode" records for the current entity, newest first.

Event, 1 operation

list_subscription_eventsList subscription eventsGETLists subscription lifecycle events for the current entity, newest first. Use this to build an audit trail of activations, cancellations, charge failures and plan changes.

Me, 1 operation

get_meGet meGETReturns the `User` that owns the access token, along with the subdomains they manage.

Update, 1 operation

list_feed_updatesList feed updatesGETLists the current entity's feed tokens, most recently updated first, together with the field-level changeset from their latest recorded version.

Visit, 1 operation

list_analytics_visitsList analytics visitsGETLists pre-aggregated **visit** rollups for the current entity, newest bucket first.

Use Supercast from Claude Code, Cursor or Codex

Connect Supercast in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Supercast operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Supercast

Create your workspace
Sign up free. Nothing to install.
Connect Supercast once
Add your Supercast connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.