With the introduction of the Springcast MCP, we are taking a major step towards automating your podcast workflow.
A few important notes beforehand:
Using the Springcast MCP is entirely optional.
Using the Springcast MCP may mean that your data (for example, when you request information about your podcast) is processed by, for example, ChatGPT or Claude. Depending on your settings and subscription with that provider, this may mean that data is processed outside the EU. Check your AI tool's privacy settings to ensure that they align with your organisation's policies.
Read more about data processing in connection with the Springcast MCP in this article: Springcast MCP: data processing and privacy
What is an MCP?
MCP stands for Model Context Protocol. In simple terms: it is a bridge between an AI (such as Claude) and an external app (such as Springcast). Thanks to this protocol, the AI can retrieve information directly from your account or perform actions, without you having to manually copy and paste data.
What can you do in this first version?
At the moment, MCP functionality is disabled by default. Has it been activated for your workspace? Then you can do the following via an AI client:
Gain insight into your content: Find out directly which podcast shows and episodes you have.
View details: Ask for the specific details of a particular show or episode.
Create new episodes: You can provide a title, description and other metadata to create a draft episode.
💡 Important: It is not yet possible to upload an audio file or artwork directly via the MCP. However, you can provide a public URL (for example, a link to an MP3 file on your Google Drive or Dropbox), which Springcast will then use.
Setting up Springcast MCP
- Would you like to use Springcast MCP with Claude? Follow the instructions in this article: Springcast MCP with Claude
Need help?
Are you experiencing problems or do you have suggestions for new features within the MCP? Send us a message via the support button.
Good luck with automating! 🎙️