How to integrate Avoma MCP with Hermes

Connect Hermes to Avoma MCP. Summarize yesterday's customer call notes, find meetings needing follow-up emails, and more using natural language, with authentication handled for you.

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

Hermes is a 24/7 autonomous agent that lives on your computer or server — it remembers what it learns and evolves as your usage grows.

This guide explains the easiest and most robust way to connect your Avoma account to Hermes. You can do this through either Composio Connect CLI or Composio Connect MCP. For personal use we recommend the CLI, but you won't go wrong with MCP either.

Also integrate Avoma with

What is Composio Connect?

Composio Connect is a consumer offering that lets anyone plug 1,000+ applications directly into their agent harness — including Hermes. It can:

  • Search and load tools from relevant toolkits on-demand, reducing context usage.
  • Chain multiple tools to accomplish complex workflows via a remote workbench, without excessive back-and-forth with the LLM.
  • Manage app authentication end-to-end with zero manual overhead.

Integrating Avoma with Hermes

Using Composio Connect CLI

1. Install the Composio CLI

Run the install script directly, or paste https://composio.dev/hermes into your Hermes chat box to have it installed for you.

bash
curl -fsSL https://composio.dev/install | bash
Hermes authenticating with Composio

2. Authenticate

Once the CLI is installed, ask Hermes to authenticate with Composio.

3. Connect to Avoma

Ask your agent to connect to Avoma, or simply request any Avoma-related task. Hermes will prompt you to authenticate and authorize access.

4. Done. You're all set with a new Avoma connection.


Using Composio Connect MCP

1. Get your MCP URL and API Key

Go to dashboard.composio.dev and copy your Connect MCP URL and API key.

Copy MCP URL and API key from Composio dashboard

2. Open the Hermes config file

bash
nano ~/.hermes/config.yaml

3. Add the Composio Connect MCP server

bash
mcp_servers:
  composio:
    url: "https://connect.composio.dev/mcp"
    headers:
      x-consumer-api-key: "YOUR_COMPOSIO_API_KEY"
    connect_timeout: 60
    timeout: 180

Save with Ctrl + O, Enter, then exit with Ctrl + X.

4. Restart your Hermes agent

Once restarted, ask your agent to connect to Avoma or request any Avoma-related task. It will prompt you to authenticate and authorize access.

5. Done!

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 so your agent can perform Avoma operations on your behalf.

Way Forward

With Avoma connected, Hermes can now act on your behalf whenever it detects a relevant task or you ask it to.

From here, you can extend Hermes further:

  • Connect more apps: Calendar, Slack, Notion, Linear, and hundreds of others are available through the same Composio Connect setup. Each new integration compounds what Hermes can do for you.
  • Build workflows across tools: Once multiple apps are connected, Hermes can chain actions together — turn an email into a calendar invite, a Slack message into a Linear ticket, or a meeting note into a follow-up draft.
  • Let it learn your patterns: The more you use Hermes, the better it gets at anticipating how you'd handle recurring tasks. Give it feedback on drafts and decisions, and it will adapt.

If you run into trouble or want to share what you've built, join the community or check out the Docs for deeper configuration options.

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.

FRAMEWORKS

How to build Avoma MCP Agent with another framework

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. Hermes 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