How to integrate Avoma MCP with Codex

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Avoma MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

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

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Avoma MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

Also integrate Avoma with

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Avoma MCP in Codex

Run the setup command

Run this command in your terminal to add the Composio MCP server to Codex.

Terminal

It will initiate the authentication in a browser window, authorize Codex to access your Composio account.

Composio authentication page

(Optional) Authenticate with OAuth

To authenticate manually, run the login command to open a browser window and authorize Codex to access your Composio account.

bash
codex mcp login composio

Verify the connection

Run codex mcp list to confirm Composio appears as a registered MCP server.

bash
codex mcp list

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
  2. Fill the header and Key fields with { "x-consumer-api-key" = "ck_*******" }.
  3. The Key is the Composio API key, that you can find on dashboard.composio.dev
  4. Click on Authenticate and authorize Codex to your Composio account and you're all set.
Codex App MCP setup
  1. Restart and verify if it's there in .codex/config.toml
bash
[mcp_servers.composio]
url = "https://connect.composio.dev/mcp"
http_headers = { "x-consumer-api-key" = "ck_*******" }

What is the Avoma MCP server, and what's possible with it?

The Avoma MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Avoma account. It provides structured and secure access to your meetings, calls, transcripts, notes, recordings, and conversation intelligence, so your agent can find meetings, retrieve transcripts, review AI insights, analyze engagement, and inspect scorecard evaluations on your behalf.

  • Meeting and call discovery: Have your agent find meetings and externally recorded calls by date, attendee, direction, CRM details, call type, privacy context, or duration.
  • Transcripts, notes, and snippets: Let the agent retrieve full meeting transcripts, review notes in JSON, HTML, or Markdown, and find user-created or AI-generated snippets.
  • Conversation analysis: Direct your agent to review AI insights, topics, speaker segments, sentiment records, and recording access for processed meetings.
  • Engagement and coaching insights: Instruct your agent to summarize team engagement metrics and inspect scorecard evaluations by date, meeting, scorecard, or evaluated user.
  • Call ingestion and workspace review: Have your agent submit externally hosted call recordings for processing, check their status, list visible users and configuration catalogs, or audit active webhook subscriptions.

Conclusion

You've successfully integrated Avoma with Codex using Composio's MCP server. Now you can interact with Avoma directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Avoma operations
  • Managed authentication through Composio
  • Access to 20,000+ tools across 1000+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Avoma operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities
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.

FAQ

Frequently asked questions

With a standalone Avoma MCP server, the agents and LLMs can only access a fixed set of Avoma tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Avoma and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Codex fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Avoma tools.

Yes, absolutely. You can configure which Avoma scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Avoma data and credentials are handled as safely as possible.

Start with Avoma.It takes 30 seconds.

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

Start building