Avoma MCP and API: Connect Claude, ChatGPT and Webhooks

Avoma connects to Claude and ChatGPT through its own MCP server at mcp.avoma.com/mcp, with an OAuth sign-in, and it opens a REST API and webhooks to your own systems. All three need the Organization plan, which costs $29 per recorder seat per month billed annually or $39 per recorder seat per month billed monthly, or Enterprise. Of these routes, Startup gets only Zapier, alongside its native Slack, Microsoft Teams, ClickUp, CRM and dialer integrations. An admin publishes the connector once, then every teammate links their own Avoma account. The assistant reads meetings, notes, transcripts, scorecard results and usage metrics. It can change just three fields. Our verdict: for a revenue team already on Organization, the MCP route is the fastest payoff, while the API suits teams with a developer on hand.

Check the plan before anyone opens a settings page

Avoma's help center says the MCP connector needs an Organization or Enterprise plan ^[1]. That MCP help page also mentions an API Access add-on; Avoma does not publish a price for it. Webhooks are not available on Startup, and the pricing matrix lists API access from Organization as well. Enterprise costs $39 per recorder seat per month, billed annually only, with a minimum of 10 recorder seats. Every recorder must be on the same plan, so you cannot upgrade only the one manager who wants Claude to read the calls.

The step up is easy to price. Moving from Startup to Organization adds $10 per recorder seat per month at either billing term. By our arithmetic, that is $120 per recorder seat a year at either billing term, and five recorders billed annually go from $1,140 a year on Startup to $1,740 a year on Organization. Viewers stay free on both. The same step also brings custom templates and translation, plus group, round-robin and embedded scheduling, which Startup gets only through the Lead Router add-on (1:1 scheduling links are on every paid plan). Our Avoma pricing breakdown covers billing terms and add-ons in full.

Setting up the connector in Claude and in ChatGPT

Set-up always has two halves. An admin adds or publishes the connector on the AI side, and then each member signs in to their own Avoma account through OAuth, choosing an access scope on the consent screen. The server address is identical for both assistants. Avoma moved its MCP set-up to an OAuth browser flow in July 2026 and added a connections dashboard at the same time, so no member handles a key or runs a script.

Claude

The person adding the connector needs the Owner role in the Claude organization and a paid Claude plan that supports custom connectors. Avoma has also sat in Claude's connector directory as a community connector since August 2026. The steps:

1. The Owner adds a custom connector with the remote MCP server URL mcp.avoma.com/mcp.
2. Publishing is automatic: the connector appears for all team members in Claude, on all devices.
3. Each member connects their Avoma account, signs in through OAuth and picks a scope.
4. Each member sets every Avoma tool to Blocked, Ask permission or Always allow.

One detail trips people up. Scheduled prompts in Claude that call Avoma only run if every tool they use is set to Always allow, because nobody is there to approve a request mid-run.

ChatGPT

Here the admin must run a ChatGPT Business or Enterprise workspace with developer mode, which supports custom connectors, then add mcp.avoma.com/mcp with OAuth and publish it. Members need a ChatGPT Plus, Pro, Team, Business or Enterprise account with Developer Mode switched on. Two quirks matter daily. ChatGPT will not route a question to Avoma on its own, so the prompt has to name Avoma MCP. The connector also disconnects after 30 days without use; members reconnect from their connector settings by clicking Connect. If the admin republishes it, every member must sign in again.

What the assistant can see, and the three fields it can change

The read tools cover most of what a rep or manager asks: list_meetings, get_meeting, get_meeting_transcript, get_meeting_notes, list_scorecard_evaluations, list_team_usage_metrics, list_meeting_outcomes, list_meeting_types, list_deal_stages and list_teams. Scope decides the reach. User limited sees your non-private meetings, User full adds your private ones, and Organization limited sees all non-private meetings in the organization. Access follows the user's own Avoma permissions, so a rep never pulls a call they could not open in the app.

It is not read-only. The write tools are set_meeting_outcome, set_meeting_purpose and set_meeting_privacy, and notes and transcripts cannot be edited through MCP ^[2]. Outcomes include Closed Won, Closed Lost, Renewal and No Show, so you could ask Claude to mark last week's demo as lost. Privacy can be set to Private, Team, Org-wide or Public; the team level exists from Organization, which the connector already requires. CRM updates still travel through Avoma's native sync, not the connector; our Avoma CRM integration guide explains what syncs where.

Big questions have a ceiling. The connector is subject to Avoma's rate limits, and a query spanning a very large number of meetings can time out, so ask about one team, one month or one account at a time. Avoma's MCP page adds that Ask Avoma itself can be called through MCP and the external API.

The REST API: keys, scopes and the endpoints worth knowing

Only admins create, view or revoke API keys, and they do it in Settings → Organization → Developer ^[3]. An organization can hold up to 10 keys at a time; revoking one frees its slot immediately. Each key gets one of the same three scopes as the connector, and neither the scope nor the user it was issued to can change later, so a new scope means a new key. Keys created before scoped keys existed keep full access to the organization and cannot be converted.

Requests carry the key as a bearer token against api.avoma.com. The endpoint groups on dev.avoma.com cover calls, meetings, notes, transcriptions, recordings, scorecards and evaluations, templates, smart categories, meeting types and outcomes, users, snippets, engagement analytics and webhooks. Create Call stands out: it accepts a transcript you already have, and Avoma writes notes from it instead of transcribing the recording. The Revenue Intelligence timeline endpoints are labeled Beta.

Plan jobs around the limits. The API allows 60 requests per minute and stops any request after 60 seconds, so wide date ranges should be split into smaller batches. Organization-wide snippet queries reach back 180 days at most. A script fetching one meeting per request tops out at 3,600 meetings an hour, by our arithmetic. Nightly syncs fit easily. Backfills take patience.

Webhooks and Zapier: pushing events out instead of polling

Webhooks need Organization or Enterprise ^[4], and admins add them on the same Developer page. The target must use HTTPS; you can attach custom headers and limit the trigger to all members or specific teams. Four events exist: AINOTE, when AI notes are ready, plus a meeting booked through the Scheduler and its canceled and rescheduled variants. Deliveries can carry an HMAC-SHA256 signature in the X-Avoma-Signature header. Verify that signature before trusting a payload.

Delivery is best-effort. Your endpoint must answer with HTTP 200, and if it errors or stalls, Avoma retries a limited number of times before the event may be lost, so a daily API pull that catches missed meetings is cheap insurance. Deleting a webhook through the API only deactivates it. The cap on webhooks per event type depends on the plan, and Avoma does not publish it.

Zapier is the one route open on every paid plan, Startup included. An admin goes to Settings → Organization Settings → Integrations and clicks Generate Credentials for a Client ID and Secret. The app offers one trigger, New Conversation, which fires when notes are generated, and one action, Upload a Call, for audio recordings. The payload holds action items with owners, the AI notes as HTML and text, and pre-signed links to the video, audio and transcript. Meetings of people without a paid seat never reach Zapier.

A safety pass before an AI assistant gets in

An assistant widens who can query your calls. Check these first:

• Privacy defaults. Internal meetings default to Private and external ones to Organization, and a meeting counts as external if any invitee sits outside your email domain, gmail.com included. An Organization limited scope therefore reaches most customer calls. Admins can set and lock defaults separately for internal and external meetings.
• Smallest scope. Give User limited unless someone truly needs their private meetings.
• The privacy tool. Keep set_meeting_privacy on Ask permission in Claude.
• Who is connected. The MCP page in Avoma's Settings lists each connection with access level, date, status and tool usage.
• Old keys. Replace legacy keys with scoped ones and revoke the originals.
• Support access. Avoma staff see no customer data unless an admin turns on the support toggle; switch it off after troubleshooting.

The bottom line

Avoma's integrations pay off for teams already on Organization: the connector puts meetings, notes, transcripts and scorecard results into Claude or ChatGPT after a short OAuth set-up, and the API and webhooks give engineers clear, published limits. On Startup, Zapier's single trigger and single action are the only route to your own systems, next to the native Slack, Microsoft Teams, ClickUp, CRM and dialer integrations. Before switching anything on, settle each person's scope, keep the privacy-changing tool behind a confirmation, and review the MCP page every quarter.