get_authenticated_userLABSCO SUMMARY
Publishing an episode without the dashboard.
The upload step is the one that usually forces a browser open; here it is a call that hands back a URL to push the file to, and the episode is created from the same session.
What it is
A client for the Transistor.fm API. It lists your shows and their episodes, reads an episode in detail, hands back a pre-signed URL for an audio upload, creates the episode from it, and returns download analytics.
What you get
- Your shows listed, paginated and searchable, and the account behind the key confirmed
- Episodes for a show listed by status — published, draft or scheduled — and read in detail
- A pre-signed upload URL for an audio file, with the content type to use and how long it lasts
- A new episode created, including from a file just uploaded
- Download analytics for a show or a single episode
Requirements
Node to run the built server, and a Transistor API key set as TRANSISTOR_API_KEY.
Setup effort
Build from source — git clone https://github.com/gxjansen/Transistor-MCP.git
USE CASES
01
Publishing an episode you have just finished
Ask for the upload URL, push the audio to it, and create the episode against the show — the whole release path in one pass.
02
Checking how the last few episodes did
Analytics come back per show or per episode, so a question about whether a topic landed is answered with downloads rather than impressions.
03
Finding an episode you need the details of
List the show's episodes with a search term or a status filter, then read the one you want in full.
04
Seeing what is still sitting in drafts
Filtering by draft or scheduled shows what has been recorded but never went out — the backlog that is easy to lose track of.
05
Confirming which account a key belongs to
Read the authenticated user and the shows it can see, before assuming an empty list means an empty account.
23 tools
Listed in project docs. Your client may show a different list.
authorize_uploadlist_showslist_episodesget_episodeget_analyticscreate_episodeupdate_episodeget_all_episode_analyticslist_webhookssubscribe_webhookunsubscribe_webhookget_showupdate_showpublish_episodeget_download_summarycompare_episodeslist_subscribersget_subscribercreate_subscribercreate_subscribers_batchupdate_subscriberdelete_subscriberBEFORE YOU INSTALL
What to know first
Tools you get
23 tools named in the project's documentation.
Requires
- node on PATH
- TRANSISTOR_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/gxjansen/Transistor-MCP.git
cd Transistor-MCP
npm install
npm run buildMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"transistor": {
"command": "node",
"args": [
"<YOUR_PATH_TO_TRANSISTOR_MCP>/build/index.js"
],
"env": {
"TRANSISTOR_API_KEY": "<YOUR_TRANSISTOR_API_KEY>"
}
}
}
}<YOUR_PATH_TO_TRANSISTOR_MCP>/build/index.js is the absolute path of build/index.js in your clone (npm run build creates it).
