Ask ChatGPT or Claude about past sermons
Connect uploads.run to ChatGPT, Claude, or another AI app and ask about the services your church has already uploaded. “What did we preach about Romans last quarter?” “Find the quote about ‘therefore’ and give me the link.” “Which sermons this year mentioned the prodigal son?” Answers come from your own transcripts, and every quote links to the exact moment in the recording on uploads.run.
Use this connector URL in every app:
https://uploads.run/api/mcpSigned in? The same URL is in Settings with a copy button.
What happens when you connect
- Your AI app opens an uploads.run sign-in window. Enter your email and the 6-digit code we send, the same way you sign in to uploads.run. There's no separate password.
- Review the request. It shows which app is asking, the workspace it will read, and where you'll return. Choose Allow read access.
- You're sent back to the app, and it can start answering questions about your services.
ChatGPT
- In ChatGPT, open Settings, then Apps (Connectors on some plans). If your plan shows Developer mode under Advanced settings, turn it on. On Business and Enterprise plans an admin may need to allow custom connectors first.
- Choose Create. Name it uploads.run, paste the connector URL above, and choose OAuth for authentication. Confirm that you trust the app and create it.
- Sign in to uploads.run in the window that opens and choose Allow read access.
- In a new chat, turn on uploads.run from the tools menu and ask your question. Deep research can use it too.
Claude (web and desktop)
- On claude.ai, open Settings, then Connectors, and choose Add custom connector. On Team and Enterprise plans an owner may need to add it for the organization first.
- Name it uploads.run, paste the connector URL above, and choose Add. Then choose Connect, sign in to uploads.run, and choose Allow read access.
- Turn uploads.run on from the tools menu in a chat. The Claude desktop app uses the connectors on your Claude account, so it shows up there too after you sign in.
Cursor, Claude Code, and others
Any app that supports remote MCP servers over Streamable HTTP with OAuth can connect. It opens the same uploads.run sign-in window.
Cursor: add this to ~/.cursor/mcp.json, then choose the sign-in prompt in Cursor's MCP settings.
{
"mcpServers": {
"uploads-run": { "url": "https://uploads.run/api/mcp" }
}
}Claude Code:
claude mcp add --transport http uploads-run https://uploads.run/api/mcpVS Code: add this to .vscode/mcp.json.
{
"servers": {
"uploads-run": { "type": "http", "url": "https://uploads.run/api/mcp" }
}
}For developers: the server publishes OAuth discovery at /.well-known/oauth-protected-resource/api/mcp and /.well-known/oauth-authorization-server, supports dynamic client registration and PKCE (S256), and answers 401 with a WWW-Authenticate header that points to that discovery document.
What it can read
- Search across every transcribed service by words, speaker, part of the service (such as the sermon), topic, scripture, or date.
- Read a service's transcript with timestamps, its title, date, speakers, sections, and suggested titles.
- List your services, speakers, and podcast shows.
The connector can't upload, publish, delete, or change anything. It reads as you: owners, admins, and members each see the same services they already see in uploads.run, and nothing from other churches.
It reads the workspace you're in when you connect. To use a different workspace, switch workspaces in uploads.run. The connector follows within an hour, or disconnect and connect again to switch right away.
Privacy
When you connect ChatGPT, Claude, or another AI app, that company sees the questions you ask and the transcript excerpts uploads.run sends back to answer them. Their privacy terms cover what they do with it. uploads.run sends nothing until you ask, and only from the workspace you connected.
Disconnect
Open Settings and choose Disconnect beside the app. Access stops right away. You can also remove the connector in the AI app. If you leave a workspace or are removed from it, the connector loses access within an hour, the same as uploads.run itself.
If something looks wrong
- No results: only services that have finished transcribing are searchable. Check the service in uploads.run.
- Wrong church or campus: you're connected to a different workspace. Switch in uploads.run, then disconnect and connect again.
- Asked to sign in again: that's expected after you disconnect or sign out everywhere. Sign in and allow access again.