Connect Whipscribe to ChatGPT — Custom GPT vs MCP Connector Setup
Two ways to use Whipscribe inside ChatGPT: the Custom GPT, which works for everyone on any plan, and the MCP Connector, which adds Whipscribe to every chat for Plus and Pro accounts. This is the canonical setup guide for both, with a decision matrix and the troubleshooting answers we've actually hit in testing.
Which path should you pick?
Most people start with the Custom GPT. It works on every ChatGPT plan, including the free tier, and it shows up as its own conversation in the GPT store. The MCP Connector is the second-stage upgrade for ChatGPT Plus and Pro users who want Whipscribe available in every chat without switching to a specific GPT.
Custom GPT
Anyone with a ChatGPT account, on web or mobile.
- Works on Free, Plus, Pro, Team, Enterprise
- Open the GPT, sign in once, transcribe
- Mobile-friendly: drop a voice memo from your phone
- 21 actions: transcribe, search, library, recipes, workflows
MCP Connector
ChatGPT Plus and Pro accounts only.
- Available in every chat, no GPT switch
- Discoverable by ChatGPT in tool-use mode
- Same OAuth, same actions, same account
- Configured once in Settings → Connectors
Path 1 — Custom GPT setup (3 steps)
This is the path that works for everyone. About 90 seconds end-to-end the first time, near-zero on subsequent uses.
Open the Whipscribe GPT in ChatGPT
Go to the Whipscribe GPT page and click Start Chat. The GPT lives in the OpenAI GPT store under the name "Whipscribe."
Authorize Whipscribe (one-time)
The first time you ask the GPT to transcribe something, ChatGPT shows an authorization prompt. Click Sign in to Whipscribe, sign in with the same email you use on whipscribe.com, and approve the connection. Your credits and library stay on the same account.
Send the file or paste a URL
Drop an audio or video file directly into the ChatGPT message box, or paste a URL to a file you host. Then ask anything: "Transcribe this with speaker labels", "Pull the action items", "Save this to my Knowledge folder named Q3 customer interviews". Whipscribe runs the transcription, returns the text, and ChatGPT does the rest.
Drop an audio file in the message box, ask for the transcript. Free tier covers 30 minutes a day.
Open the Whipscribe GPT →What the GPT can do once it's connected
The Whipscribe GPT exposes 21 actions — the same surface area as the Claude integration we ship at https://whipscribe.com/mcp. The most-used ones in practice:
- Transcribe a file with speaker diarization and word-level timestamps.
- Transcribe a URL you host — your own podcast feed, your own meeting recording, your own video file.
- Search across past transcripts by keyword, then quote the matching turn back into the chat.
- Save items to a Knowledge folder for project-by-project organization.
- Run a Recipe — a saved prompt-template — across the transcript (e.g. "extract action items as a markdown table").
- Run a Workflow — a multi-step pipeline like "transcribe → extract decisions → save to folder → return summary."
None of this requires you to leave the chat. Everything happens inline.
Path 2 — MCP Connector setup (Plus / Pro)
The MCP (Model Context Protocol) Connector is OpenAI's way to let any chat — not just a specific GPT — call out to an external service. Once you add Whipscribe as a Connector, ChatGPT can decide on its own to use Whipscribe whenever it's the right tool for the question.
Open ChatGPT Settings → Connectors
On chatgpt.com (web), click your profile icon → Settings → Connectors. The Connectors tab is where you wire up MCP servers.
Add a new MCP server
Click Add and enter the Whipscribe MCP endpoint:
https://whipscribe.com/mcp
ChatGPT auto-discovers the tool list and the OAuth flow via Dynamic Client Registration — you don't paste a client ID or secret. Give the connection a name like "Whipscribe" so you recognize it later.
Authorize once and you're done
ChatGPT redirects you to Whipscribe to authorize. Sign in with the same email as your Whipscribe account; approve. After that, Whipscribe tools are available in every conversation. Ask "Can you transcribe this voice memo?" in any chat and ChatGPT picks the right tool.
Decision matrix — which to pick when
| What you want | Custom GPT | MCP Connector |
|---|---|---|
| Free ChatGPT plan | Yes | — |
| Plus / Pro / Team | Yes | Yes |
| Mobile (iOS / Android) | Yes | Yes |
| Enable in every chat by default | — | Best fit |
| Discoverable by your team via the GPT store | Best fit | — |
| Drop-and-transcribe a voice memo from your phone | Best fit | Yes |
| Setup time, first run | ~ 90 sec | ~ 90 sec |
| Setup repeats per chat | None | None |
| Tools exposed | 21 | 21 |
Both surfaces share the same backend, the same OAuth, and the same 21 actions. The choice is about where the tool lives in your ChatGPT habit, not about feature breadth.
Sample chat — what the conversation actually looks like
Here's a real exchange you can run today in either path. The specific quotes are paraphrased for length, but every action shown is one Whipscribe ships:
You: I've got a 45-min product call. Can you transcribe and pull
decisions, action items, and open questions?
ChatGPT: I can. Drop the file or share a URL.
[you upload meeting.m4a]
ChatGPT: Sending that to Whipscribe with speaker diarization.
(~90 seconds — 45-min audio.)
ChatGPT: Done. Here's a structured summary:
Decisions (3)
- Move launch to Sept 12 (Sarah, 00:08:14)
- Use Stripe Atlas for the EU entity (Mark, 00:22:01)
- Skip the Q4 partnership track this year (Sarah, 00:38:40)
Action items (5)
- Mark: file Atlas paperwork by Friday
- Sarah: brief the design team on Sept 12 timeline
- …
Open questions (2)
- VAT registration in Germany — who owns this?
- Whether to keep a soft launch internal-only
Want me to save this transcript to your "Product calls"
Knowledge folder so it's searchable later?
You: Yes please. And run the "weekly recap" Recipe on it.
ChatGPT: Saved. Running weekly-recap…None of that required leaving ChatGPT. The transcript is now in your Whipscribe library at whipscribe.com/home, the action-item summary is in the chat, and a saved Recipe just produced your weekly note.
Troubleshooting — the four issues we've actually hit
"OAuth callback URL doesn't match"
If the consent screen appears but the redirect back to ChatGPT throws an error, the most common cause is an outdated OpenAI redirect host. The Whipscribe shim allow-lists both chat.openai.com/aip/ and chatgpt.com/aip/. If OpenAI introduces a new host, retry once — the allow-list is updated centrally and propagates within minutes.
"GPT visibility is set to Only me — my team can't open it"
This affects organization rollouts only. The public Whipscribe GPT (the one linked above) is visible to anyone with the link. If you forked or cloned the GPT under your own account, switch its visibility to "Anyone with the link" in the GPT editor before sharing internally.
"MCP Connector says Connected but tools don't show up in chat"
ChatGPT discovers MCP tools via Dynamic Client Registration on first authorize. If the tool list is empty after a successful connect, click Refresh in the Connector detail view, or remove and re-add the connector. We've also seen this resolve itself on the next ChatGPT app restart.
"Long transcription jobs time out in the chat"
The Whipscribe GPT and MCP both use a long-polling pattern: ChatGPT calls getJob?wait=N and the server holds the connection up to N seconds, returning the moment status flips to done. If a job is unusually long (large file, queue depth) the chat may show "still working" — ask ChatGPT to check status again; the polling resumes from where it left off.
Privacy and account details
A few specifics worth knowing up front:
- One ChatGPT email = one Whipscribe email. The shim creates a 1:1 mapping between your ChatGPT identity and your Whipscribe account. If you sign in to ChatGPT with one address and Whipscribe with another, you'll have two separate libraries. Use the same email both places.
- Files are processed by Whipscribe, not by OpenAI. When you drop a file into the GPT, ChatGPT hands the file to Whipscribe over the authorized connection. Transcription happens on Whipscribe infrastructure. The transcript text comes back to the chat for ChatGPT to reason over.
- OpenAI training is off on this GPT. The Whipscribe Custom GPT is configured so user-uploaded files are not used to train OpenAI models. Your audio stays your audio.
- 7-day retention default. Audio files dropped via the GPT or MCP follow the same 7-day deletion default as direct Whipscribe uploads. Anything you save to a Knowledge folder is kept indefinitely; raw audio not saved to a folder is purged.
If you don't have a Whipscribe account yet
You don't need one to try the GPT — the first authorize will create one for you using your ChatGPT email. The free tier covers 30 minutes of transcription per day, which is enough to run the workflows above end-to-end on a real meeting. Beyond that, pay-as-you-go is $1 per hour of audio and credits never expire.
No subscription required. Top up only when you cross 30 free minutes a day.
See credits →Related blog posts on the ChatGPT workflow
If you got here from a "use ChatGPT for X" search, these are the deeper guides on each downstream artifact:
- Transcribe Audio & Video in ChatGPT — The Complete 2026 Guide
- Turn Meeting Recordings into Action Items Inside ChatGPT
- Generate Show Notes for Your Podcast Inside ChatGPT
- Transcribe Research Interviews in ChatGPT
Ready to connect Whipscribe to ChatGPT?
Two paths, one Whipscribe account behind both. Start with the Custom GPT — works on every plan including free — then add the MCP Connector if you're on Plus or Pro and want Whipscribe in every chat.