Otter.ai MCP
for LuumenAI

Search your Otter.ai meetings and pull full transcripts, in the terminal

Incident calls, change reviews, and vendor syncs often hold the detail that never made it into a ticket. Connect Otter.ai and Luumen can find the right meeting with OTTER_AI_MCP_OTTER_SEARCH, then pull the speaker-attributed transcript, summary, and action items with OTTER_AI_MCP_OTTER_FETCH. Read-only, over OAuth with dynamic client registration.

The Otter.ai MCP toolbox

3 tools, all read-only. They answer instantly, and every call is logged.

  • ReadOtter fetchFetch one meeting's complete verbatim transcript by ID - full speaker-attributed, timestamped content, plus its AI summary, action items, outline, and attendees.
  • ReadOtter get user infoGet current Otter.ai user's name, email, and current date/time (PST) - READ-ONLY.
  • ReadOtter searchSearch meetings across platforms by date, attendee, topic, keyword, or title.

Questions

How does LuumenAI connect to Otter.ai MCP?

Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Otter.ai MCP on its own?

No. Every one of the 3 tools LuumenAI has for Otter.ai MCP is read-only, so it can answer questions from Otter.ai MCP but cannot change anything in it. Reads are not gated — they answer immediately, and each one is recorded on the audit trail with the actor and the result.

Who gets access to the integration?

You decide. Access is granted per agent, skill, and team, and per environment — production is not staging.

Is there an audit trail?

Every call to Otter.ai MCP is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

Put Otter.ai MCP to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.