Tracker › Call & conversation intelligence
Auditory + Claude / ChatGPT
Auditory's remote MCP server is read-only access to calls and transcripts: search transcripts, list calls, open one call (attendees, AI summary, action items and risks), read a transcript and list deal risks. ChatGPT uses the Auditory app's Connect flow. Claude on the web and desktop uses a custom connector, and Claude Code can add the HTTP server. Accounts in more than one organization aren't supported over MCP yet. This entry is vendor-documentation verification from Nov 9, 2026, not a live account test.
Every field below was confirmed in vendor docs on Nov 9, 2026.
| Category | Call & conversation intelligence |
|---|---|
| Built by the vendor? | Yes |
| Claude | Custom connector (paste URL) Claude on the web and desktop: Customize > Connectors > Add custom connector, name it Auditory, and use https://api.auditory.co/mcp. Claude Code: claude mcp add --transport http auditory https://api.auditory.co/mcp, then /mcp to sign in. Other remote MCP clients that support OAuth Client ID Metadata Documents can use the same URL. |
| ChatGPT | Directory app/plugin Open the Auditory app in ChatGPT and click Connect, then sign in to Auditory and approve access. The Nov 2, 2026 post describes that Connect flow and doesn't describe a developer-mode URL setup. |
| Setup type | Directory listing |
| Read-only or read/write | Read-only Search transcripts, list calls, get a call (attendees, AI summary, action items and risks), read a transcript, and list deal risks. It can't change, delete or share anything in Auditory. OAuth scopes are auditory:calls:read and auditory:transcripts:read, so you can approve calls without transcripts. You only see calls you can already see in Auditory. |
| Admin setup needed? | No Each person connects their own account. The server follows that organization's existing call visibility. If the account can't view recordings, an Auditory admin has to grant call access. That isn't a separate MCP install. Multi-organization accounts aren't supported over MCP yet. |
| Plan / requirements | An Auditory account in an organization, with access to calls. The Nov 2, 2026 post doesn't state which Auditory plan includes MCP, or a separate MCP price. Multi-organization accounts aren't supported over MCP yet. |
| MCP / connector URL | https://api.auditory.co/mcp (OAuth) |
| Last verified | Nov 9, 2026 |
Sources
Vendors change these integrations often. Always check the vendor's docs before you roll anything out to your team. See a mistake? Tell us.
The email
Get the weekly AI Sales Stack email.
Each week you get new connectors, changed permissions and setup gotchas for sales tools. It is short and written for AEs and sales ops.
Free. Unsubscribe anytime.