Avoma's AI meeting notetaker MCP server connects Claude and ChatGPT directly to your transcripts, notes, scorecards, and deal outcomes, so your AI workflows runs on meeting intelligence.





Meeting knowledge stays trapped

You've become the context pipeline

AI can read your meetings but can't do anything with them

Messy meeting data breaks reporting downstream
Claude or ChatGPT can fetch any meeting's transcript, notes, summary, or action items by account, rep, date, or topic, in seconds. Ask Avoma is now also available via MCP and External API, so you can ask natural language questions across your meeting history without opening Avoma.

Your AI reads scorecard evaluations across the team, finds who's struggling with specific call moments, and delivers a grounded coaching brief. No list of recordings to manually review.

Avoma MCP lets AI agents classify meetings, log outcomes, and set privacy, keeping your data clean and your pipeline reporting accurate.

Pair Avoma MCP with your agent and any downstream tool. The agent reads the call, applies your stage rules, and writes the right update, wherever it needs to go.

A dedicated MCP page in Settings shows your whole organization who's connected Avoma to Claude, ChatGPT, or other AI tools, and how they're using it.

Check the setup guide. The setup is little different based on your AI tool (ChatGPT or Claude) and your role (workspace admin or team member). Once an admin publishes the connector, each user simply connects their Avoma account to start accessing and updating meeting data directly from their AI chat.
Once connected, your AI can retrieve transcripts, pull notes, search past meetings by account or topic, and surface scorecard data from a single question. The AI meeting notetaker MCP server sits inside your Avoma revenue intelligence stack, so context flows across recording, coaching, and deal tracking.
With write access enabled, agents classify meetings, log outcomes, set privacy, and push interpreted intel to downstream tools as calls complete. Define the rules once in your agent config. Every call that follows gets handled the same way, with no rep input required.
