This article is a follow-up to Springcast MCP: Getting Started and explains how to connect Springcast to Claude.
You no longer need an API token or a configuration file. You add Springcast as a connector in Claude and sign in with your own Springcast account. This works in Claude on the web (claude.ai), in the Claude Desktop app, and in the mobile apps once the connector is added.
Good to know
- Every workspace member can connect, not just owners. What Claude can see and do depends on your role and your show access in Springcast. If you can't edit a show in Springcast, Claude can't edit it either.
- One connection = one workspace. If you're a member of several workspaces, you choose one while connecting. To use another workspace, add the connector again and choose that workspace.
- The MCP server must be available on your plan. If it isn't, Springcast shows a message during sign-in.
- SSO workspaces: if your workspace uses single sign-on, sign in to Springcast with SSO during the connection.
Step 1: Add Springcast as a connector in Claude
- In Claude, go to Settings → Connectors.
- Click Add custom connector.
- Fill in:
-
Name:
Springcast -
URL:
https://work.springcast.app/mcp
-
Name:
- Click Add.
Claude Team or Enterprise? An owner of your Claude organization first adds the connector under Admin settings → Connectors. Each member then connects it with their own Springcast account via Settings → Connectors.
Step 2: Sign in and allow access
After you click Connect, a Springcast window opens.
Sign in to Springcast, or use SSO if your workspace requires it.
Choose a workspace if you're a member of more than one.
-
Review what Claude may do. You'll see a switch for each area:
- Content: Read, or Read + write (create, edit and publish shows and episodes)
- Analytics: view statistics
- Courses: Read, or Read + write
You can turn off or limit anything you don't want Claude to do. Only the options your role and plan allow are shown. If your access is limited to certain shows, the screen lists exactly which shows and courses Claude will be able to reach.
Accept the terms and click Allow.
You're sent back to Claude, and Springcast now shows as connected.
Step 3: Test it
Start a new chat and ask, for example:
- "Which podcast shows do I have in Springcast?"
- "Show me the latest five episodes of my show and their listen counts."
Claude asks for your permission the first time it uses a Springcast tool. In the connector's settings you can choose whether Claude must always ask first or may use a tool without asking.
Managing and disconnecting
In Springcast, go to Workspace settings → Developers → Connected apps. There you see which apps are connected, who connected them, what they're allowed to do, and when they were last used.
- Revoke disconnects an app immediately. To use it again, you'll have to reconnect it from Claude.
- Members see their own connections. Workspace owners see and can revoke every connection in the workspace.
- If someone leaves your workspace, their connection stops working automatically. If their role or show access changes, the connection follows that change right away.
Changes made through Claude are recorded in the workspace audit log under the name of the person who connected.
Troubleshooting
"This workspace does not have the MCP server enabled."
The MCP server isn't available on your workspace's current plan. Contact us if you'd like to use it.
"Your role in this workspace does not allow connecting apps."
Your role has no permissions that Claude could use. Ask a workspace owner to adjust your role.
The workspace is greyed out in the list.
That workspace requires single sign-on. Sign in to Springcast with SSO, then start the connection again from Claude.
The connection works, but every request fails.
Your workspace may limit API access to allowed IP addresses (Workspace settings → Security center). In that case, Claude's servers must be on the allowlist. Anthropic publishes the IP addresses it uses in its documentation.
Claude asks me to reconnect.
This happens when the connection was revoked in Springcast, when you were removed from the workspace, or when the connection hasn't been used for 30 days. Reconnect it under Settings → Connectors in Claude.
Alternative: API token (advanced)
Workspace API tokens with the MCP scope still work. You can use them with MCP clients that don't support signing in, or for automated workflows that shouldn't depend on one person's account. A token always has access to the whole workspace, regardless of who created it. For Claude, we recommend the connector described above.