Avoma MCP server
Avoma in any MCP client, through Memtro: Avoma does not publish this server. Memtro's Avoma connector reads Avoma through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Avoma meeting assistant: recorded meetings and calls with attendees, purpose and outcome, Avoma's AI notes per meeting, full transcripts by speaker, the organisation's users, scorecard evaluations and smart categories. When you ask it can add a dialer call recording for Avoma to process, make the bot leave a live meeting, and create or change smart categories.
Reads
avoma_list_meetingsMeetings and calls recorded by Avoma, newest first: subject, start and end (UTC), length, organiser and attendees, purpose and outcome…avoma_get_meetingOne Avoma meeting by uuid: subject, time, attendees, purpose, outcome and readiness of notes and transcript.avoma_get_meeting_notesAvoma's AI notes for a meeting — action items, decisions, questions and the rest, each with its type — and the keywords that came up.avoma_get_transcriptThe full transcript of an Avoma meeting, speaker by speaker.avoma_list_usersPeople in the Avoma organisation: name, email, role and whether active.avoma_list_scorecardsScorecard evaluations of meetings in Avoma, newest first: the scorecard, overall score, who scored and who was scored, the company and deals.avoma_list_smart_categoriesAvoma's smart categories (the keyword and prompt trackers that tag meeting notes across the organisation): uuid, name, keywords, prompts and settings.
Acts, when you ask
These change something in Avoma. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
avoma_create_callRecords a phone call from a dialer in Avoma for one of the organisation's users, so Avoma downloads the recording from its public link…avoma_drop_meetingMakes Avoma's bot leave a meeting that is in progress, so the rest of it is not recorded; it cannot be undone or rejoined from here…avoma_create_smart_categoryCreates a smart category in Avoma: keywords and prompts Avoma then looks for in every meeting across the organisation…avoma_update_smart_categoryAdds or removes keywords and prompts on an Avoma smart category, or changes its settings.
Connect it
First connect Avoma on Dashboard → Connections, then add Memtro to your client once. The Avoma tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Avoma connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › What did we agree with Acme on Tuesday?
- › What did Brightwave Ltd raise across our calls this month?
- › How did Dan Fletcher score on discovery calls this month?
- › Which action items came out of yesterday's internal meetings?
- › Add 'competitor pricing' with the keywords Globex and BigCo as a smart category
Questions
- Is this an official Avoma MCP server?
- No. It is Memtro's MCP server with Memtro's Avoma connector behind it: the connector reads Avoma through its API with the credentials you connect on Dashboard → Connections, and Avoma publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Avoma?
- Only when you ask, and only what it has been granted: add a dialer call for Avoma to record and process (uses the user's recording minutes); make Avoma's bot leave a live meeting; create a smart category; add or remove a smart category's keywords and prompts. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.