Avoma MCP server for AI agents and assistants

Securely connect your AI agents and chatbots (Claude, ChatGPT, Cursor, etc) with Avoma MCP or direct API to summarize meetings, analyze calls, manage notes, review scorecards, and query conversation intelligence through natural language.

Avoma logoAvoma
Api Key

Avoma is an AI meeting assistant for recording, transcribing, analyzing, and managing meetings, calls, notes, scorecards, and conversation intelligence. It helps teams turn conversations into searchable notes, follow-ups, coaching insights, and revenue intelligence.

16 Tools

Try Avoma now

Type what you want done — sign in and watch it run live in the Tool Router playground.

TOOL ROUTER PLAYGROUND
Avoma
Try asking
TOOLS

Supported Tools

Every Avoma action and event your agent gets out of the box.

Create Call

Submit an externally hosted call recording to Avoma for asynchronous processing.

Get Call

Retrieve one externally ingested Avoma call by the dialer system's external ID.

Get Engagement Summary

Aggregate Avoma engagement metrics across visible users for a required UTC date range and optional meeting and user filters.

Get Meeting

Retrieve one meeting by UUID, including processing/readiness state and optionally CRM associations.

Get Meeting Analysis

Return Avoma's AI insights, topical and speaker segments, and sentiment records for one processed meeting in a single read-only invocation.

Get Recording

Get time-limited audio and video URLs for a meeting recording.

List Calls

List externally ingested calls in a required UTC date range, optionally filtered by inbound or outbound direction.

List Configuration Resources

List one Avoma configuration catalog: custom categories, smart categories, scorecards, templates, meeting types, or meeting outcomes.

List Engagement Metrics

List per-user Avoma engagement metrics over a required UTC date range with meeting and user filters.

List Meetings

Find meetings visible to the connected Avoma user within a required UTC date range, with optional attendee, CRM, call-type, privacy-context, duration, and ordering filters.

List Notes

Retrieve Avoma notes for meetings in a required UTC date range, optionally narrowed to a meeting or custom category and rendered as JSON, HTML, or Markdown.

List Scorecard Evaluations

List Avoma scorecard evaluations, optionally filtered by UTC date range, scorecard templates, meeting, or evaluated users.

List Snippets

Find user-created or AI-generated meeting snippets by meeting UUID or by a UTC date range of at most 180 days.

List Transcriptions

Find full meeting transcriptions by meeting UUID or by a UTC date range, with attendee and CRM filters.

List Users

Return users visible in the Avoma organization, including their UUID, email, role, teams, and active status.

List Webhooks

Audit the connected organization's active Avoma webhook subscriptions without reading signing secrets.

SETUP GUIDE

Connect Avoma MCP Tool with your Agent

1

Install Composio

typescript
npm install @composio/core ai @ai-sdk/mcp @ai-sdk/openai
Install the Composio SDK and your agent framework
2

Create a session with MCP enabled

typescript
import { Composio } from "@composio/core";

const composio = new Composio();
const { mcp } = await composio.create("your-user-id", {
  toolkits: ["avoma"],
  mcp: true,
});
Create a session scoped to Avoma and read its MCP URL and headers
3

Connect your agent to the MCP server

typescript
import { createMCPClient } from "@ai-sdk/mcp";
import { openai } from "@ai-sdk/openai";
import { generateText, stepCountIs } from "ai";

const client = await createMCPClient({
  transport: { type: "http", url: mcp.url, headers: mcp.headers },
});

const { text } = await generateText({
  model: openai("gpt-5.6-sol"),
  tools: await client.tools(),
  prompt: "Summarize my latest Avoma meeting and list action items",
  stopWhen: stepCountIs(10),
});

console.log(text);
await client.close();
Pass the session's MCP URL and headers to your agent and run a Avoma request
SETUP GUIDE

Connect Avoma API Tool with your Agent

1

Install Composio

typescript
npm install @composio/core @composio/openai openai
Install the Composio SDK, the OpenAI provider, and the OpenAI SDK
2

Create a Composio session

typescript
import OpenAI from "openai";
import { Composio } from "@composio/core";
import { OpenAIResponsesProvider } from "@composio/openai";

const composio = new Composio({ provider: new OpenAIResponsesProvider() });
const client = new OpenAI();

const session = await composio.create("your-user-id", { toolkits: ["avoma"] });
const tools = await session.tools();
Initialize Composio with the OpenAI Responses provider and create a session scoped to Avoma
3

Run Avoma tools with your agent

typescript
let response = await client.responses.create({
  model: "gpt-5.6-sol",
  tools,
  input: [{ role: "user", content: "Summarize my latest Avoma meeting and list action items" }],
});

while (response.output.some((o) => o.type === "function_call")) {
  const outputs = await composio.provider.handleToolCalls(session, response.output);
  response = await client.responses.create({
    model: "gpt-5.6-sol",
    tools,
    previous_response_id: response.id,
    input: outputs,
  });
}

console.log(response.output_text);
Send a request, execute the Avoma tool calls through the session, and print the final answer

Why Use Composio?

AI Native Avoma Integration

  • Supports both Avoma MCP and direct API based integrations
  • Structured, LLM-friendly schemas so agents can work with meetings, calls, notes, and scorecards reliably
  • Rich coverage for reading, writing, and querying Avoma conversation data without bespoke integration code

Managed Auth

  • Secure API key handling so you don't have to hard-code Avoma credentials in your agent
  • Central place to manage, scope, and revoke Avoma access across users and environments
  • Per-user and per-environment credentials for safer production deployments

Agent Optimized Design

  • Avoma tools are shaped for language models, so agents can understand meeting and call workflows more easily
  • Tools are tuned using real error and success rates to improve reliability over time
  • Comprehensive execution logs so you always know which Avoma action ran, when, and on whose behalf

Enterprise Grade Security

  • Fine-grained RBAC so you control which agents and users can access Avoma
  • Scoped, least-privilege access to Avoma meeting, notes, and conversation data
  • Full audit trail of agent actions to support review, coaching, and compliance workflows

Rolling this out across your team?

Give your team centralized access control across every framework with Composio’s MCP Gateway.

EXPLORE MCP GATEWAY
FAQ

Frequently asked questions

Yes, Avoma requires you to configure your own API key. Once set up, Composio handles secure credential storage and API request handling for you.

Yes! Composio's Tool Router enables agents to use multiple toolkits. Learn more.

Yes. Composio is SOC 2 Type II compliant and is built to keep your Avoma connection and credentials secure. OAuth tokens and API keys are encrypted, and sensitive customer data is protected at rest and in transit.

Composio also undergoes independent security testing and continuously monitors its systems for security threats. You can review the latest reports and policies in the Composio Trust Center.

Composio maintains and updates all toolkit integrations automatically, so your agents always work with the latest API versions.

Create the key in your Avoma account settings, then paste it once on Composio's connection page. Composio stores it encrypted and uses it only for the Avoma actions your agent runs. Nobody else in your workspace can read it, and you can revoke it inside Avoma at any time.

When you connect a Avoma account through Composio, every action runs under that account, so anything the agent creates, sends, or changes shows up in Avoma as done by you. Keep an approval step in your prompt for actions with side effects, such as sending or deleting, and have the agent draft first.

Whatever the credentials you connect allow inside Avoma. If Avoma lets you scope a key to specific permissions, create a scoped one so the agent can only do what you intend. You can revoke the key inside Avoma at any time.

Yes. Composio supports multiple connected accounts for the same app, and that works in Claude, ChatGPT, or any other assistant you connect through Composio. Give each Avoma connection a name such as work or personal, and the assistant uses the one you mention in the request. Each account keeps its own credentials and nothing is merged.

The connection stops working the moment Avoma rejects the old key. Create a new key in Avoma and reconnect the account from the Composio dashboard or by asking your agent to reconnect Avoma. Nothing else changes.

Composio's free Hobby plan includes 100,000 tool calls per month with no credit card, which covers most personal Avoma use. Paid plans add higher limits and team features. Your Avoma plan and its API limits still apply as usual.

Built-in connectors usually give one AI access to a limited set of apps. Many people use Composio because it lets their AI connect to more apps than it normally supports, or connect to multiple accounts for the same app (e.g. connect Claude to multiple Avoma accounts).

With Composio, you connect Avoma once and then use it across different AI assistants without setting it up separately in each one. Connect your apps to Composio once, then connect Composio to whichever AI you use, whether that's Claude, ChatGPT, Hermes, or your own custom assistant.

Start with Avoma.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Avoma tool your agent needs.Free to start.

Start building