Skip to content
English
Home
  • There are no suggestions because the search field is empty.

How to set up Avoma MCP in ChatGPT web & mobile

Configure Avoma MCP using OAuth. No scripts or desktop installation required. Settings → Workspace settings → Apps

This guide shows ChatGPT workspace admins how to set up and publish the Avoma MCP connector for use in ChatGPT Web and Mobile.

Before you begin

  • You must have the Admin role in your ChatGPT workspace.
  • Your workspace must be on a ChatGPT Business or Enterprise plan that supports custom connectors.
  • Avoma MCP setup in ChatGPT is currently available to admins only.
  • This guide applies to ChatGPT Web and Mobile.

Important: OAuth authentication is designed primarily for web and mobile experiences. Many desktop MCP clients, including AI desktop applications, do not fully support OAuth or require additional manual configuration to make it work.

If you're using a desktop client, we recommend using the API key authentication method instead. See our API Key Setup Guide for details.

Step 1: Enable developer mode

Before configuring Avoma MCP, you need to enable developer mode in ChatGPT.

  1. Click “Settings” in the bottom left corner.
  2. Go to the “App” section.
  3. Select “Advanced settings”.
  4. Enable “Developer mode”.
  5. Enable “Enforce CSP in developer mode”.
  6. Close Settings.

Enable developer mode in ChatGPT

ChatGPT Settings → App → Advanced settings — Developer mode and Enforce CSP toggles enabled

 

Step 2: Create the Avoma MCP app

  1. Go to → Workspace settings → Apps in ChatGPT web or mobile.
  2. Click “Create”.


    Settings → Workspace settings → Apps — Create button visible


  3. Fill in the following details:
    1. Name: Avoma MCP
    2. Description: Integration for accessing meeting data and insights
    3. URL: https://mcp.avoma.com/mcp
    4. Authentication method: OAuth
  4. Click “I understand and want to continue” to confirm.
  5. Scroll to the bottom and click “Create”.
  6. Wait for the system to register the app.


Enter the Avoma MCP app details and select OAuth authentication.


Step 3: Authorize with OAuth

After the app is created, you’ll be redirected to an OAuth consent page to connect your Avoma account.

  1. Review the three permission scopes displayed on the consent page:

    Scope

    Tied to

    What it can access

    Best for

    User – limited access

    One user

    That user’s non-private meetings only. Private meetings are always excluded.

    Tools that should never receive private recordings.

    User – full access

    One user

    Everything that user can see in Avoma, including their private meetings.

    Integrations that need to act as a specific person.

    Organization – limited access

    Org-wide

    All non-private meetings across the org. Private meetings are excluded.

    Reporting or analytics tools that should only use shared data.
  2. Select the scope appropriate for your organization.
  3. Click “Allow Access”. 

    NOTE: Avoma MCP is now connected to your admin account. Your team members will connect their own accounts after you publish the app in Step 4.


    Step 4: Publish the app to your workspace

    Publish the app so all members of your workspace can find and use it.

    1. Go to Settings → Workspace settings → Apps
    2. Click “Drafts” to find the connector you just created.
    3. Click on the Avoma MCP connector, then click “Publish”.

      Workspace settings → Apps → Drafts — Avoma MCP connector with Publish button
      Workspace settings → Apps → Drafts — Avoma MCP connector with Publish button

    4. A “Publish Avoma MCP” dialog appears. Expand each of the two risk review sections:
      1. Review potential risk: Unauthorized data access — expand and acknowledge.
      2. Review potential risk: Malicious app — expand and acknowledge.
        Avoma MCP Publishing
    5. Click “Publish” to make Avoma MCP available to all workspace members.

    Published Avoma MCP

     

    Important: Both risk review sections must be expanded and acknowledged before the Publish button becomes active. The app will not publish if either section is left in the “Not reviewed” state.

     

    NOTE: After publishing, members can find and connect to Avoma MCP by searching for it in Settings → Apps. Share the “Using Avoma MCP in ChatGPT” help article with your team so they can complete their own setup.

     

    Troubleshooting and FAQs

    Why is the Publish button grayed out?

    The Publish button remains inactive until both risk review sections in the publish dialog are expanded and acknowledged. Expand each section, review the information, and confirm both before clicking Publish.

     

    Why can’t my team members find the Avoma MCP connector?

    After publishing, it may take a few minutes for the connector to appear for workspace members. If it’s still not visible after 10 minutes, check that the app status in Workspace settings → Apps shows “Published” (not “Draft”).

     

    Which OAuth scope should I choose?

    Choose based on what data the integration needs access to. For org-wide reporting or analytics, use “Organization – limited access”. For individual user workflows that do not require private meeting data, use “User – limited access”. Use “User – full access” only when the integration specifically needs access to private meetings.

    What’s next

    • Share the “Using Avoma MCP in ChatGPT” help article with your team so each member can connect their own Avoma account.
    • Verify the connector appears as “Published” in Workspace settings → Apps.
    • Test the integration by opening a new chat, adding Avoma MCP, and asking a meeting-related question.

    Recap

    You’ve enabled developer mode, created the Avoma MCP connector, authorized it with OAuth, and published it to your workspace. Your team can now connect and use Avoma MCP in ChatGPT.

    Related articles

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