Transistor MCP Server

MCP server for the Transistor.fm podcast hosting API — manage shows, episodes, analytics, download summaries, transcripts, subscribers, and webhooks.

Local serverstdioTypeScript

What is the Transistor MCP MCP server?

MCP server for the Transistor.fm podcast hosting API — manage shows, episodes, analytics, download summaries, transcripts, subscribers, and webhooks. Exposed over MCP by the transistor mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

This MCP server provides tools to interact with the Transistor.fm API, allowing you to manage podcasts, episodes, and view analytics.

Its toolset

Everything the assistant can do here goes through one of these:

  • get_authenticated_user — The get_authenticated_user tool exposed by this server
  • authorize_upload — Get a pre-signed URL for uploading an audio file. Use this before creating an episode with a local audio file
  • list_shows — List all shows in your Transistor.fm account, ordered by updated date (newest first). Returns a paginated list with 10 items per page
  • list_episodes — The list_episodes tool exposed by this server
  • get_episode — The get_episode tool exposed by this server
  • get_analytics — Get analytics for a show or specific episode. Defaults to the last 14 days if no dates are provided
  • create_episode — The create_episode tool exposed by this server
  • update_episode — The update_episode tool exposed by this server
  • get_all_episode_analytics — Get analytics for all episodes of a show. Defaults to the last 7 days if no dates are provided
  • list_webhooks — The list_webhooks tool exposed by this server
  • subscribe_webhook — The subscribe_webhook tool exposed by this server
  • unsubscribe_webhook — The unsubscribe_webhook tool exposed by this server

Configuration

You will need one environment variable: TRANSISTOR_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Transistor MCP's toolset — get_authenticated_user, authorize_upload, list_shows and 11 more — is a fair guide to whether it matches your workflow. It is maintained by gxjansen; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Transistor MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Transistor MCP.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the transistor mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
get_authenticated_userThe get_authenticated_user tool exposed by this server.
authorize_uploadGet a pre-signed URL for uploading an audio file. Use this before creating an episode with a local audio file.
list_showsList all shows in your Transistor.fm account, ordered by updated date (newest first). Returns a paginated list with 10 items per page.
list_episodesThe list_episodes tool exposed by this server.
get_episodeThe get_episode tool exposed by this server.
get_analyticsGet analytics for a show or specific episode. Defaults to the last 14 days if no dates are provided.
create_episodeThe create_episode tool exposed by this server.
update_episodeThe update_episode tool exposed by this server.
get_all_episode_analyticsGet analytics for all episodes of a show. Defaults to the last 7 days if no dates are provided.
list_webhooksThe list_webhooks tool exposed by this server.
subscribe_webhookThe subscribe_webhook tool exposed by this server.
unsubscribe_webhookThe unsubscribe_webhook tool exposed by this server.
get_showThe get_show tool exposed by this server.
update_showUpdate a show. json show_id: string // Required author: string // Optional category: string // Optional copyright: string // Optional description: string // Optional explicit: boolean // Optional image_url: string // Opt

How to install the Transistor MCP MCP server

{
  "mcpServers": {
    "transistor": {
      "command": "node",
      "args": ["path/to/Transistor-MCP/build/index.js"],
      "env": {
        "TRANSISTOR_API_KEY": "your-api-key-here"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
TRANSISTOR_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Transistor MCP to get authenticated user.
  • Use Transistor MCP to authorize upload.
  • Use Transistor MCP to list shows.

Frequently asked questions

It connects Transistor MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (get_authenticated_user, authorize_upload, list_shows, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Transistor MCP directly.