AssemblyAI MCP server
AssemblyAI in any MCP client, through Memtro: AssemblyAI does not publish this server. Memtro's AssemblyAI connector reads AssemblyAI 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
AssemblyAI speech to text: the account's transcripts from the last 30 days with status, then any transcript's text or speaker-by-speaker utterances, summary, chapters, key phrases and topics, its paragraphs, and where given words were said; when you ask, can transcribe an audio file at a URL (billed per audio second) or delete a transcript's data permanently.
Reads
assemblyai_list_transcriptsTranscripts this AssemblyAI key made in the last 30 days, newest first: id, status (queued, processing, completed, error)…assemblyai_get_transcriptOne AssemblyAI transcript: status, duration, language, summary, chapters, key phrases and topics where they were requested, the speakers…assemblyai_get_paragraphsA completed transcript split into paragraphs with start times (m:ss), for reading or quoting a long recording in order.assemblyai_search_wordsWhere words or short phrases (up to five words each) were said in a completed transcript: how many times each was matched and at which moments (m:ss).
Acts, when you ask
These change something in AssemblyAI. 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.
assemblyai_transcribeSends the audio or video at audio_url to AssemblyAI to be transcribed, which spends money: billed per second of audio, with speaker labels…assemblyai_delete_transcriptDeletes an AssemblyAI transcript's data permanently: its text, words and results are removed and it is marked deleted (the id remains)…
Connect it
First connect AssemblyAI on Dashboard → Connections, then add Memtro to your client once. The AssemblyAI 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 AssemblyAI 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 was said about pricing on the last recorded sales call?
- › Which transcripts failed this week, and why?
- › Summarise the chapters of yesterday's board meeting recording.
- › Where in the onboarding call did anyone mention SSO?
- › Transcribe the recording at this link.
Questions
- Is this an official AssemblyAI MCP server?
- No. It is Memtro's MCP server with Memtro's AssemblyAI connector behind it: the connector reads AssemblyAI through its API with the credentials you connect on Dashboard → Connections, and AssemblyAI 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 AssemblyAI?
- Only when you ask, and only what it has been granted: transcribe an audio or video file at a URL (billed per audio second); delete a transcript's text and data permanently. 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.