How to connect AudioScribe to Claude

AudioScribe speaks MCP (Model Context Protocol), the open standard AI assistants use to connect to outside tools. Connect once and Claude can read your transcripts directly — no copying, pasting, or exporting.

Ask things like "what did we agree in yesterday's client call?" or "find every conversation tagged Sales from last week" and Claude answers from your actual transcripts.

Connect Claude Code

1. Run the connect command in your terminal:

   claude mcp add --transport http --scope user audioscribe https://mcp.audioscribe.io/mcp
   

   
   --scope user makes the connection available in every project. Without it Claude Code uses local scope, which adds the connection to the current project only, so it won't appear when you work somewhere else.
2. Start the connection by typing /mcp and selecting audioscribe.
3. Sign in. Your browser opens the normal AudioScribe login.
4. Check what you're granting. Nothing beyond these three should appear: transcripts:read and workspaces:read, which are the AudioScribe permissions and are both read-only, and offline_access, which is not an AudioScribe permission and grants no access to your data — it lets Claude renew its access token instead of making you sign in again each time one expires. Seeing only the first two is fine. Anything extra is not.
5. Done. Claude Code confirms the connection.

Connect Claude on the web or desktop

Adding the connector is two stages: add it once to your account, then switch it on in the conversations where you want it.

1. Add the connector. In Claude, go to Customize → Connectors, click +, choose Add custom connector, and enter https://mcp.audioscribe.io/mcp. Leave the advanced OAuth fields blank — AudioScribe handles the sign-in.
   On a Team or Enterprise account this lives under Organization settings → Connectors, and only an owner can add it.
2. Sign in and approve, checking the permissions the same way as above.
3. Turn it on in a conversation. Claude keeps connectors off by default in each new chat. Click the + button at the lower left of the chat, choose Connectors, and toggle audioscribe on.

That third step is the one people miss — a connector that's added but not enabled looks connected and does nothing.

Menu names shift between Claude versions; Anthropic's custom-connector guide has their current wording.

What Claude can reach

Once connected, Claude can read transcript text, existing summaries, tags, and conversation details for every workspace your AudioScribe account can access. That is what transcripts:read and workspaces:read cover.

Specifically, it can:

• List your workspaces, with how many completed conversations are in each
• Find conversations by date, by tag, or by searching what was said
• Read a full transcript — with speaker labels and timestamps where the recording was transcribed with them, and as plain text otherwise
• Pull an existing summary without loading the whole conversation

Alongside the text, Claude receives the details attached to each conversation — its title, duration, language, speaker count, workspace, and when it was created.

Your original audio and video files are never shared. The connection carries transcripts and their details, not media.

Some examples that work well:

• "What are my most recent conversations?"
• "Pull everything from yesterday tagged Sales."
• "Search my transcripts for the pricing discussion."
• "Summarize the discovery call from Tuesday."

What Claude cannot do

The connection is read-only, by design. Claude cannot:

• Upload, edit, rename, or delete anything
• Change your account, workspaces, tags, or billing
• Reach conversations in workspaces your account can't already open

Nothing Claude does through this connection can alter your account.

Dates and tags

You can ask in plain language — "yesterday", "last two weeks", "since Monday" — and Claude turns that into a date range before searching.

For tags, two things are always true regardless of how you phrase the request:

• Matching ignores case and accents. Asking for sales finds a tag named Sales; resume finds Résumé.
• Multiple tags narrow, they don't widen. "tagged Sales and Follow-up" returns only conversations carrying both.

Ask "what tags do I have?" to see the full list, which is the surest way to get the name right.

You can also point a request at a single workspace — "search Consulting for onboarding".

Disconnecting

Go to Settings → Connected apps in AudioScribe and click Disconnect. This removes the authorization at its source, which is the only place it can be removed reliably.

Disconnecting takes effect right away but is not instantaneous, and it revokes the authorization rather than preventing a new one:

• That Claude client can no longer obtain new access tokens. This takes effect immediately and is what actually ends the connection.
• An access token already issued keeps working until it expires. These are signed tokens that cannot be withdrawn once issued, so Claude may still read your transcripts for up to an hour after you disconnect. Tokens issued before the token-lifetime change on 7 August 2026 were valid for 24 hours, so during the day following that change an already-issued token can outlive the usual hour.
• Anything Claude already retrieved is outside our reach. Disconnecting cannot undo what was read before it. How long that data persists on Claude's side is up to Claude.

Claude Code and Claude on the web or desktop are authorized separately and appear as separate entries. To cut Claude off entirely, disconnect every entry listed — and note that any access tokens already issued still run until they expire.

Removing or signing out of the connection inside Claude is a separate action, handled by Claude rather than by us, and what it revokes depends on the client and version. If a device is lost or stolen, disconnect from AudioScribe Settings: revoking the authorization there does not depend on the client behaving a particular way. Two caveats apply, and both matter in that situation. The token window above still holds, so treat the cutoff as taking up to an hour rather than being immediate — or up to 24 hours for a token issued before the 7 August 2026 lifetime change. And disconnecting does not stop the connection being set up again: anyone who can still sign in to your AudioScribe account on that device can reconnect it. Securing the account itself is the part that lasts.

Troubleshooting

The consent screen lists anything other than transcripts:read, workspaces:read, and offline_access. Stop, and email support@audioscribe.io. Nothing outside those three should ever appear — no matter what an extra entry is called, or whether it reads, writes, or administers something. You should not have to judge whether an unfamiliar permission is safe. Seeing only the first two, without offline_access, is fine — it is an extra entry that matters.

You signed in but Claude doesn't see your transcripts. On the web or desktop, check the connector is switched on for that conversation: + at the lower left → Connectors → toggle audioscribe on. It's off by default in each new chat. In Claude Code, /mcp shows whether the connection is live.

The connection works in one project but not another. Claude Code scopes connections to a project by default. Re-add it with --scope user, as above.

Login fails or loops. Confirm you can sign in at app.audioscribe.io first. If that works and the connection still fails, email support@audioscribe.io and mention you were connecting via MCP.

What it costs

Nothing extra from us. MCP uses your existing AudioScribe account on any plan, including free, and there's nothing to install beyond the connect command above.

Claude sets its own terms for custom connectors, and those can differ by Claude plan — free Claude accounts are limited in how many connectors they can add, and on team or enterprise accounts only an owner can add them. If Claude won't let you add one, that's Anthropic's side rather than ours; their custom-connector guide has the current rules.