Skip to main content Announcing Tool Policies: AI agent permissions down to the field Read the announcement
Live 8 Actions

Otter.ai MCP Server
for AI Agents

Connect your AI agent to StackOne's Otter.ai MCP server and give it ready-to-use MCP tools out of the box. Auth, tool execution, and security all managed.

Otter.ai logo
Otter.ai MCP Server
Built by StackOne StackOne
DrataGPLocalyzeFlipMindtoolsScreenloop

Coverage

8 Agent Actions

Agents can read and write in Otter.ai. Extend your agent's capabilities with custom actions.

Authentication

Agent Tool Authentication

Per-user OAuth in one call. Your Otter.ai MCP server gets session-scoped tokens with zero credentials stored on your infra.

Agent Auth →

Security

Agent Protection

Every Otter.ai tool response scanned for prompt injection in milliseconds, with 88.7% accuracy, all running on CPU.

Prompt Injection Defense →

Performance

Max Agent Context. Min Cost.

Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every Otter.ai call.

Tools Discovery →

What is the Otter.ai MCP Server?

A Otter.ai MCP server lets AI agents read and write Otter.ai data through the Model Context Protocol, Anthropic's open standard for connecting LLMs to external tools. StackOne's Otter.ai MCP server ships with pre-built actions, fully extensible via the Connector Builder, plus managed authentication, prompt injection defense, observability, and agent execution runtime. Connect it from MCP clients like Claude Desktop, Claude Code, Cursor, Goose, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.

All Otter.ai MCP Tools

Every StackOne action for Otter.ai, ready for your agent. Read and write, scoped to exactly what you need.

Channels

  • List Channels

    Retrieve the Otter channels accessible to the authenticated user. Returns the channel id needed by list_channel_members and by the channel_id filter on list_conversations.

Channel Members

  • List Channel Members

    Retrieve the members of an Otter channel by channel id (from list_channels), returning each member's id, name and email.

Conversations

  • Create Conversation

    Import an externally recorded audio or video file into Otter from a URL, creating a conversation that Otter transcribes and summarises.

  • List Conversations

    Retrieve a cursor-paginated list of Otter conversations (meetings) for the authenticated user. Returns the conversation id needed by get_conversation and get_conversation_audio.

  • Get Conversation

    Retrieve a single Otter conversation by its id (from list_conversations), together with the transcript, action items, insights or outline selected by the include parameter.

Conversation Audios

  • Get Conversation Audio

    Retrieve the MP3 download link for an Otter conversation's recording, by conversation id from list_conversations.

Workspaces

  • Get Workspace

    Retrieve the Otter workspace the authenticated API key belongs to, including its id, name, owner, member count, handle and type.

Workspace Conversations

  • List Workspace Conversations

    Retrieve every conversation in an Otter workspace, not just those owned by or shared with the authenticated user. Requires Super Admin.

Set Up Your Otter.ai MCP Server in Minutes

One endpoint. Any framework. Your agent is talking to Otter.ai in under 10 lines of code.

Agent Frameworks

Claude Desktop
{
  "mcpServers": {
    "stackone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id=<account_id>",
        "--header",
        "Authorization: Basic <YOUR_BASE64_TOKEN>"
      ]
    }
  }
}

Check More AI & ML MCP Servers

ElevenLabs

182+ actions

Cursor

164+ actions

Hugging Face

126+ actions

OpenAI

121+ actions

E2B

62+ actions

Dialpad

57+ actions

Pinecone

42+ actions

Otter.ai MCP Server FAQ

Does StackOne have a Otter.ai MCP server?
Yes. StackOne offers a hosted Otter.ai MCP server, and every action is tested and QA'd by StackOne. Connect it to Claude, Cursor, and any other MCP client, or to any agent framework through the AI Action SDK. It ships with managed agent authentication, prompt injection defense, and tool discovery with server-side execution that preserve your agent's context window and keep reasoning performance.
Otter.ai MCP server vs direct API integration: what's the difference?
A Otter.ai MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software work, where backend code calls Otter.ai. A Otter.ai MCP server is for AI agents that discover and call Otter.ai at runtime, such as MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI. StackOne provides both.
How does Otter.ai authentication work for AI agents?
Otter.ai authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK to get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own Otter.ai account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via origin_owner_id.
Are Otter.ai MCP tools vulnerable to prompt injection?
Yes. Otter.ai MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content, such as documents, messages, tickets, records, or free-text fields, is a potential vector. StackOne Defender scans every tool response before it enters the agent's context. It runs regex patterns in ~1ms, then a MiniLM classifier in ~4ms. Accuracy is 88.7%, and it runs entirely on CPU.
What is the context bloat of a Otter.ai agent and how do I avoid it?
Context bloat happens when Otter.ai tool schemas and API responses eat your Otter.ai agent's memory, preventing it from reasoning effectively. A single Otter.ai query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery reduces it by loading only the tools relevant to each query.
Can I limit which actions my Otter.ai agent can access?
Yes. You can limit which actions your Otter.ai agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my Otter.ai MCP server?
Yes. You can create custom agent actions for your Otter.ai MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research Otter.ai's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a Otter.ai MCP server?
Skip a Otter.ai MCP server if your integration is purely software-to-software, because direct Otter.ai API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call Otter.ai actions at runtime.
What AI frameworks and AI clients does the StackOne Otter.ai MCP server support?
The StackOne Otter.ai MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.

Put your AI agents to work

All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.