# Avoma — how to use (mcp.ai)

Connect your Avoma account and use 16 tools for meeting assistants straight from your AI agent. Connect with your own API key. Avoma is an AI meeting assistant for recording, transcribing, analyzing, and managing meetings, calls, notes, scorecards, and conversation intelligence.

## Option A — via MCP (recommended)
Remote MCP endpoint (HTTP, streamable): `https://api.mcp.ai/p_avoma?ms=1787291280000`
Add it as a custom/remote MCP connector in your client (Claude, Cursor, VS Code…), then authenticate when prompted. Once connected, ask the agent to use the server's tools (e.g. `avoma_create_call`).

## Option B — via direct REST API
Base URL: `https://api.mcp.ai/api/avoma`
Auth: `Authorization: Bearer sk_live_…` — create a workspace API key at https://mcp.ai/settings/api-keys
Discover endpoints: `GET https://api.mcp.ai/api/avoma/_endpoints`

### Endpoints
- `POST https://api.mcp.ai/api/avoma/create/call` — Submit an externally hosted call recording to Avoma for asynchronous processing. This persistently creates external call state, and Avoma will download the recording from the supplied publicly reachab
  - body: { end_at?: string, source: string, to_name?: string, answered?: boolean, start_at: string, direction: string, from_name?: string, to_number: string, user_email: string, external_id: string, from_number: string, is_voicemail?: boolean, participants: object[], recording_url: string, crm_associations?: object[], additional_details?: object }
- `POST https://api.mcp.ai/api/avoma/get/call` — Retrieve one externally ingested Avoma call by the dialer system's external ID.
  - body: { external_id: string }
- `POST https://api.mcp.ai/api/avoma/get/engagement/summary` — Aggregate Avoma engagement metrics across visible users for a required UTC date range and optional meeting and user filters.
  - body: { is_call?: boolean, to_date: string, from_date: string, is_internal?: boolean, user_emails?: string[], is_impromptu?: boolean, meeting_type_uuids?: string[], shared_meetings_only?: boolean, meeting_outcome_uuids?: string[], recording_duration_gte?: number, recording_duration_lte?: number }
- `POST https://api.mcp.ai/api/avoma/get/meeting` — Retrieve one meeting by UUID, including processing/readiness state and optionally CRM associations.
  - body: { meeting_uuid: string, include_crm_associations?: boolean }
- `POST https://api.mcp.ai/api/avoma/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.
  - body: { meeting_uuid: string }
- `POST https://api.mcp.ai/api/avoma/get/recording` — Get time-limited audio and video URLs for a meeting recording.
  - body: { meeting_uuid: string }
- `POST https://api.mcp.ai/api/avoma/list/calls` — List externally ingested calls in a required UTC date range, optionally filtered by inbound or outbound direction. Returns one page and a cursor.
  - body: { to_date: string, direction?: string, from_date: string, next_cursor?: string }
- `POST https://api.mcp.ai/api/avoma/list/configuration/resources` — List one Avoma configuration catalog: custom categories, smart categories, scorecards, templates, meeting types, or meeting outcomes.
  - body: { order?: string, page_size?: integer, next_cursor?: string, resource_type: string }
- `POST https://api.mcp.ai/api/avoma/list/engagement/metrics` — List per-user Avoma engagement metrics over a required UTC date range with meeting and user filters. Returns one page and an opaque cursor.
  - body: { order?: string, is_call?: boolean, to_date: string, from_date: string, page_size?: integer, is_internal?: boolean, next_cursor?: string, user_emails?: string[], is_impromptu?: boolean, meeting_type_uuids?: string[], shared_meetings_only?: boolean, meeting_outcome_uuids?: string[], recording_duration_gte?: number, recording_duration_lte?: number }
- `POST https://api.mcp.ai/api/avoma/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. Returns one page and an opa
  - body: { order?: string, is_call?: boolean, to_date: string, from_date: string, page_size?: integer, is_internal?: boolean, next_cursor?: string, crm_lead_ids?: string[], attendee_emails?: string[], crm_account_ids?: string[], crm_contact_ids?: string[], crm_opportunity_ids?: string[], recording_duration_gte?: number, include_crm_associations?: boolean }
- `POST https://api.mcp.ai/api/avoma/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.
  - body: { order?: string, to_date: string, from_date: string, page_size?: integer, next_cursor?: string, meeting_uuid?: string, output_format?: string, custom_category_uuid?: string }
- `POST https://api.mcp.ai/api/avoma/list/scorecard/evaluations` — List Avoma scorecard evaluations, optionally filtered by UTC date range, scorecard templates, meeting, or evaluated users. Returns one page at a time.
  - body: { to_date?: string, from_date?: string, page_size?: integer, next_cursor?: string, user_emails?: string[], meeting_uuid?: string, scorecard_uuids?: string[] }
- `POST https://api.mcp.ai/api/avoma/list/snippets` — Find user-created or AI-generated meeting snippets by meeting UUID or by a UTC date range of at most 180 days. Returns one page at a time.
  - body: { to_date?: string, from_date?: string, page_size?: integer, next_cursor?: string, meeting_uuid?: string, is_ai_generated?: boolean }
- `POST https://api.mcp.ai/api/avoma/list/transcriptions` — Find full meeting transcriptions by meeting UUID or by a UTC date range, with attendee and CRM filters. Returns one page because transcript payloads can be large.
  - body: { to_date?: string, from_date?: string, page_size?: integer, next_cursor?: string, crm_lead_ids?: string[], meeting_uuid?: string, attendee_emails?: string[], crm_account_ids?: string[], crm_contact_ids?: string[], crm_opportunity_ids?: string[] }
- `POST https://api.mcp.ai/api/avoma/list/users` — Return users visible in the Avoma organization, including their UUID, email, role, teams, and active status.
- `POST https://api.mcp.ai/api/avoma/list/webhooks` — Audit the connected organization's active Avoma webhook subscriptions without reading signing secrets.

## Example prompts
- "What can I do in Avoma?"
- "Show me a summary of my Avoma account"

## More
- Page: https://mcp.ai/avoma
- Agent spec (llms.txt): https://mcp.ai/avoma/llms.txt
- Postman collection: https://mcp.ai/avoma/postman.json