Skip to content
actionlake
Start free

Connectors · CRM & sales

Avoma MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Avoma and the rest of your systems. It gives your agent 54 Avoma actions (36 reads, 11 writes and 7 that wait for a confirmation) and holds the Avoma credential itself, so the agent never does. It paces Avoma's limits and records every call.

Connect Avoma freeSee pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "avoma.users.list",  intent: "check which Avoma account is connected"}# List users · read · 1 upstream call
  • 54actionsin one signed file
  • 36readlook, never change
  • 11writecreate and update
  • 7wait for a yesdestructive, confirmed first

Set up

Connect Avoma in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Avoma.

    Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.

    • access_tokenAvoma API key (Settings > Integrations > API)
    account { op: "connections.requirements", service: "avoma" }
# free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "avoma.users.list" }# list users · read · 1 upstream callcheck { action: "avoma.calls.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Avoma at a glance

Sign-in
Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide
access_token
Limits we pace to
60 calls a minute, per connection
API covered
Avoma API v1 (OpenAPI 3.0.0, info.version 1.0.0)api.avoma.com
Built from
Avoma's documentation, read 23 October 2026dev.avoma.comdev.avoma.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
33 of 36 reads, for up to 5 minutes; a write clears what it affects
Shared entities
1, so ask can line Avoma up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Avoma.

54 actions in 18 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 36readlook, never change
  • 11writecreate and update
  • 7destructivewait for a confirmation

  1. Meetings

    6

    5 read · 0 write · 1 destructive

    List meetings · Get Meeting · Get Meeting Insights · Get Meeting segments

  2. Meeting outcomes

    5

    2 read · 2 write · 1 destructive

    List Meeting Outcomes · Get Meeting Outcome · Create Meeting Outcome · Update Meeting Outcome

  3. Meeting types

    5

    2 read · 2 write · 1 destructive

    List Meeting Types · Get Meeting Type · Create Meeting Type · Update Meeting Type

  4. Calls

    4

    2 read · 2 write · 0 destructive

    List calls · Get Call · Create Call · Update Call

  5. Engagement

    4

    4 read · 0 write · 0 destructive

    List Engagement Metrics for All Users · Get Engagement Metrics for Specific User · Get Overall Engagement Summary for All Users · Get Engagement Summary for Specific User's Participants

  6. Smart categories

    4

    2 read · 2 write · 0 destructive

    List Smart Categories · Get Smart Categories · Create the smart category settings · Update the smart category settings

  7. Templates

    4

    2 read · 2 write · 0 destructive

    List Templates · Get Templates · Create Template · Update Template

  8. Webhook signing secret

    4

    1 read · 0 write · 3 destructive

    Get Webhook Signing Secret · Clear Webhook Signing Secret · Rotate Webhook Signing Secret · Set Webhook Signing Secret

10 more areas · 18 actions
  • Webhooks 3
  • Custom categories 2
  • Recordings 2
  • Revenue intel 2
  • Scorecards 2
  • Transcriptions 2
  • Users 2
  • Notes 1
  • Scorecard evaluations 1
  • Snippets 1

Top actions

The Avoma API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 11 of Avoma's 11 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
avoma.users.listList usersList users.readidentity.user.list474 connectors
avoma.users.getGET /v1/users/{uuid}/GET /v1/users/{uuid}/.readidentity.user.get399 connectors
avoma.calls.listList callsList calls.readcomm.call.list44 connectors
avoma.calls.getGet CallGet Call.readcomm.call.get40 connectors
avoma.transcriptions.listList TranscriptionsList Transcriptions.readcomm.meeting_transcript.list8 connectors
avoma.webhooks.listList Webhook SubscriptionsList Webhook Subscriptions.readautomation.webhook.list202 connectors
avoma.calls.createCreate CallCreate Call.writecomm.call.create38 connectors
avoma.transcriptions.getGet TranscriptionGet Transcription.readcomm.meeting_transcript.get11 connectors
avoma.calls.updateUpdate CallUpdate Call.writecomm.call.update25 connectors
avoma.webhooks.createCreate Webhook SubscriptionCreate Webhook Subscription.writeautomation.webhook.create209 connectors
avoma.webhooks.deleteDelete (Deactivate) Webhook SubscriptionDelete (Deactivate) Webhook Subscription.destructiveautomation.webhook.delete211 connectors
avoma.notes.listList NotesList Notes.readthis connector

Try it

Prompts to paste into Claude.

Each one names the Avoma actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    Who has access in Avoma? List every user and their role.

    callsavoma.users.list

  2. Writewrite

    Create Call in Avoma. Show me exactly what you will send before you save it.

    callsavoma.calls.create

Governance for Avoma

Destructive actions wait for a yes.

7 Avoma actions are destructive. These are all of them:

  • Delete (Deactivate) Webhook Subscriptionavoma.webhooks.delete
  • Drop Meetingavoma.meetings.drop
  • Delete Meeting Typeavoma.meeting_types.delete
  • Delete Meeting Outcomeavoma.meeting_outcomes.delete
  • Set Webhook Signing Secretavoma.webhook_signing_secret.set
  • Clear Webhook Signing Secretavoma.webhook_signing_secret.clear
  • Rotate Webhook Signing Secretavoma.webhook_signing_secret.rotate

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

doavoma.webhooks.deleteconfirm_policy: human

Delete (Deactivate) Webhook Subscription?

intent: the user asked me to delete (Deactivate) Webhook Subscription

run suspended · waiting for a named person · key avoma-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "avoma-agent",  allowed_actions: ["avoma.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "avoma.webhooks.delete", approver: "[email protected]" },    { match: "avoma.meetings.drop", approver: "[email protected]" },    { match: "avoma.meeting_types.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to Avoma only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Avoma costs on actionlake.

Every Avoma action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Avoma refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 54 Avoma actions
  • 10actions pageeach page of a long list is one call
  • 33reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Avoma action.

54 actions by area: the id your agent calls, what it does, and its effect.

Meetings6
  • avoma.meetings.dropDrop Meetingdestructive
  • avoma.meetings.getGet Meetingread
  • avoma.meetings.get_insightsGet Meeting Insightsread
  • avoma.meetings.get_segmentsGet Meeting segmentsread
  • avoma.meetings.get_sentimentsGet Meeting Sentimentsread
  • avoma.meetings.listList meetingsread
Meeting outcomes5
  • avoma.meeting_outcomes.createCreate Meeting Outcomewrite
  • avoma.meeting_outcomes.deleteDelete Meeting Outcomedestructive
  • avoma.meeting_outcomes.getGet Meeting Outcomeread
  • avoma.meeting_outcomes.listList Meeting Outcomesread
  • avoma.meeting_outcomes.updateUpdate Meeting Outcomewrite
Meeting types5
  • avoma.meeting_types.createCreate Meeting Typewrite
  • avoma.meeting_types.deleteDelete Meeting Typedestructive
  • avoma.meeting_types.getGet Meeting Typeread
  • avoma.meeting_types.listList Meeting Typesread
  • avoma.meeting_types.updateUpdate Meeting Typewrite
Calls4
  • avoma.calls.createCreate Callwrite
  • avoma.calls.getGet Callread
  • avoma.calls.listList callsread
  • avoma.calls.updateUpdate Callwrite
Engagement4
  • avoma.engagement.get_summaryGet Overall Engagement Summary for All Usersread
  • avoma.engagement.get_user_summaryGet Engagement Summary for Specific User's Participantsread
  • avoma.engagement.listList Engagement Metrics for All Usersread
  • avoma.engagement.list_for_userGet Engagement Metrics for Specific Userread
Smart categories4
  • avoma.smart_categories.createCreate the smart category settingswrite
  • avoma.smart_categories.getGet Smart Categoriesread
  • avoma.smart_categories.listList Smart Categoriesread
  • avoma.smart_categories.updateUpdate the smart category settingswrite
Templates4
  • avoma.templates.createCreate Templatewrite
  • avoma.templates.getGet Templatesread
  • avoma.templates.listList Templatesread
  • avoma.templates.updateUpdate Templatewrite
Webhook signing secret4
  • avoma.webhook_signing_secret.clearClear Webhook Signing Secretdestructive
  • avoma.webhook_signing_secret.getGet Webhook Signing Secretread
  • avoma.webhook_signing_secret.rotateRotate Webhook Signing Secretdestructive
  • avoma.webhook_signing_secret.setSet Webhook Signing Secretdestructive
Webhooks3
  • avoma.webhooks.createCreate Webhook Subscriptionwrite
  • avoma.webhooks.deleteDelete (Deactivate) Webhook Subscriptiondestructive
  • avoma.webhooks.listList Webhook Subscriptionsread
Custom categories2
  • avoma.custom_categories.getGet Custom Categoryread
  • avoma.custom_categories.listList Custom Categoriesread
Recordings2
  • avoma.recordings.getGet Recording using recording uuidread
  • avoma.recordings.get_for_meetingGet Recordingread
Revenue intel2
  • avoma.revenue_intel.get_timelineGet aggregated timeline engagement metricsread
  • avoma.revenue_intel.list_timeline_detailsGet detailed engagement records with paginationread
Scorecards2
  • avoma.scorecards.getRetrieve a Specific Scorecard Templateread
  • avoma.scorecards.listList Scorecard Templatesread
Transcriptions2
  • avoma.transcriptions.getGet Transcriptionread
  • avoma.transcriptions.listList Transcriptionsread
Users2
  • avoma.users.getGET /v1/users/{uuid}/read
  • avoma.users.listList usersread
Notes1
  • avoma.notes.listList Notesread
Scorecard evaluations1
  • avoma.scorecard_evaluations.listList Scorecard Evaluationsread
Snippets1
  • avoma.snippets.listList Meeting Snippetsread

Questions

The Avoma MCP server, answered.

Is there an Avoma MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 54 Avoma actions across meetings, meeting outcomes, meeting types and calls, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Avoma.

What do I need to connect Avoma?

Avoma API key (Settings > Integrations > API). The free call account { op: "connections.requirements", service: "avoma" } lists exactly what to paste.

Can an AI agent delete or change things in Avoma?

Only if its key allows it, and only with an explicit confirmation. 7 Avoma actions are destructive, including delete (Deactivate) Webhook Subscription, drop Meeting and delete Meeting Type. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Avoma API limit?

actionlake paces every call to the limits in the Avoma service file: 60 calls a minute per connection. Repeated reads are answered from cache (33 Avoma actions can be), which never reaches Avoma.

What does an Avoma action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (10 Avoma actions page). Cache hits, searches, dry runs and calls Avoma refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Avoma API does it cover?

The Avoma API v1 (OpenAPI 3.0.0, info.version 1.0.0) at api.avoma.com. It is built from Avoma's documentation as read on 23 October 2026. 54 actions in 18 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Avoma data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Avoma credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

More connectors like Avoma

Shares the most action names with

Joins with, on shared entities

Browse

actionlake is independent. It is not made or endorsed by Avoma; the name is the vendor's own. Counts are from the Avoma service file, version 1.0.0.

Give your agent Avoma today.

Connect Avoma freeSee pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.