Connect and use Avoma MCP in Claude web and mobile (Members)

Each team member connects to Avoma MCP through their own Claude settings once the admin has connected it via OAuth. This is a one-time step.

Before you begin

Your organization’s Claude admin must have already set up the Avoma MCP Connector using oAuth. If they haven’t, share the admin setup article with them.
You need an active Avoma account to complete the OAuth connection.

Connect to Avoma MCP

Go to Settings → Connectors → Customize in Claude

Claude → Settings menu — personal settings, not Organization Settings
Search for Avoma MCP in the search box if you don't see it listed.
Click Avoma MCP, then click the Connect button below it.
Review the permission scopes shown on the OAuth consent page. Select the appropriate scope for your use case.

OAuth consent page — three permission scopes listed for Avoma MCP
Click Allow Access. You’ll see a confirmation message: Connected to Avoma MCP.

Settings → Connector — Avoma MCP showing “Connected” status

NOTE: The permission scopes control what Avoma data Claude can access on your behalf. You can adjust these later in Settings → Connector.

Use Avoma MCP in Claude chat

Once connected, you can request meeting data directly in Claude chat. Here are some examples to get started:

List my meetings
Show my upcoming three meetings
Get details about my last meeting

NOTE: You may need to explicitly mention Avoma MCP in your first few requests — for example, “List my meetings using Avoma MCP.” After a few uses, if memory is enabled in your workspace, Claude may not require the mention.

Managing tool permissions

After connecting, you can control how Claude handles each Avoma MCP action. Go to Settings → Connector and select Avoma MCP to review and adjust permissions.

For each tool call, you can choose one of three options:

Permission	What it means
Blocked	Avoma MCP cannot perform this action.
Ask permission	Claude will ask you before performing this action.
Always allow	Avoma MCP performs this action without asking.

Tip: For sensitive actions like retrieving meeting notes, consider setting permission to “Ask permission” so you have oversight over which meetings are accessed.

Tips

If Claude doesn’t seem to use Avoma MCP automatically, mention it explicitly in your request until memory learns the preference.
You can disconnect and reconnect Avoma MCP at any time from Settings → Connector without losing your permission settings.
If you switch Avoma accounts, disconnect and reconnect to refresh your credentials.

Troubleshooting and FAQs

I don’t see Avoma MCP in my Connector list.

Your org admin needs to add Avoma MCP first. Ask them to follow the admin setup guide. Once they’ve added it, refresh your Settings page.

The OAuth page isn’t loading or shows an error.

Make sure you’re signed in to your Avoma account in the same browser session. If the issue persists, try opening the OAuth page in a fresh browser tab or contact help@avoma.com.

Claude isn’t using Avoma MCP even after I connected.

Try mentioning Avoma MCP explicitly in your request, for example: “Using Avoma MCP, list my meetings from last week.” After a few explicit uses with memory enabled, Claude should recognize the preference.

How do I disconnect Avoma MCP?

Go to Settings → Connector, find Avoma MCP, and click Disconnect. You can reconnect at any time by clicking Connect again.

What’s next

Try asking Claude to list your recent meetings or show details about a specific call.
Adjust your tool permissions in Settings → Connector to match your privacy preferences.
Contact help@avoma.com if you run into issues with your Avoma account or connection.

Recap

You’ve connected your Avoma account to Claude and know how to request meeting data in chat and manage which actions require your permission.

If you have any questions, contact our team at help@avoma.com