
Buzzsprout
Manage Buzzsprout podcast hosting: episodes and players via its JSON API.
Install
npx skills add Anil-matcha/awesome-muse-connectors --skill buzzsprout -g -a claude-code -y- Repository
- Anil-matcha/awesome-muse-connectors1.4k
- Category
- Engineering
- Updated
- 22d ago
- License
- MIT
- Context cost
- Lightabout 697 tokens
- Runs scripts
- Yes, review before use
What it does
Manage Buzzsprout podcast hosting: episodes and players via its JSON API. Trigger phrases: buzzsprout, podcast episodes, publish episode, podcast hosting.
Buzzsprout
Purpose
Manage podcast episodes on Buzzsprout: list and fetch episodes, create, update, or delete them, and list embed players. Use when the user wants to publish or manage podcast episodes on a Buzzsprout-hosted show.
Tooling
All commands go through bin/buzzsprout.py. Every command takes --podcast-id because the podcast id is part of the API path:
bin/buzzsprout.py auth --podcast-id 12345 # verify the API token
bin/buzzsprout.py episodes --podcast-id 12345 # list episodes
bin/buzzsprout.py episode-get --podcast-id 12345 --episode-id 6789 # get one episode
bin/buzzsprout.py episode-create --podcast-id 12345 \
--payload '{"title":"Ep 12","description":"...","audio_url":"https://..."}' # create (confirm first)
bin/buzzsprout.py episode-update --podcast-id 12345 --episode-id 6789 \
--payload '{"title":"New title"}' # update (confirm first)
bin/buzzsprout.py episode-delete --podcast-id 12345 --episode-id 6789 # delete (confirm first)
bin/buzzsprout.py players --podcast-id 12345 # list embed players
API quirks handled by the CLI (you do not need to think about them): every URL ends in .json, POST/PUT send Content-Type: application/json; charset=utf-8 (Buzzsprout returns 415 without it), auth is the literal header Authorization: Token token=<token> (no whitespace after token=), and a custom User-Agent is sent on every request (Buzzsprout requires one).
