The Speak AI MCP server connects Claude, ChatGPT, Cursor, VS Code, and other Model Context Protocol clients to a Speak AI workspace. It runs at https://api.speakai.co/v1/mcp and exposes 112 tools, 5 resources, and 3 prompts covering media, transcripts, AI insights, folders, recorders, automations, dashboards, webhooks, and exports.
The same package that implements the server, @speakai/mcp-server, is also a Node library. If you want to call Speak AI from your own code instead of through a connected AI client, see the Node SDK.
What can an agent do once it’s connected?
Once connected, an agent can search recordings, read transcripts and AI insights, create folders and clips, run automations, and schedule a meeting assistant, all without you leaving the chat. You describe what you want, and the agent picks the right tools.
Examples of what people ask once the server is connected:
- “Find the last 10 customer interviews that mention pricing, group the feedback by theme, and cite the source recordings.”
- “Summarize this week’s team meetings into decisions, action items, owners, and unresolved risks.”
- “Join my 2pm Zoom call, then send me a summary with action items.”
- “Find a strong 30-second highlight from the latest webinar, create a clip, and export captions.”
Your recordings stay in your Speak AI workspace. Claude and ChatGPT only see the specific data a request asks for, and neither copies or stores your media.
Which client are you setting up?
Connecting takes one URL paste and one permission click for most AI tools. Paste the address above into your client’s connector settings, then approve the popup that opens.
Pick yours for the steps.
Claude.ai (web)
Browser-based, works on any computer.
Claude Desktop
Native macOS / Windows app.
ChatGPT
Web + desktop. Requires Developer Mode.
Cursor
One-click install via deeplink.
VS Code
One-click install via deeplink.
Windsurf
HTTP transport, config file.
ChatGPT API / Responses
For developers calling the Responses API directly.
Claude Code
Recommended, install via the official Claude Code plugin marketplace.
OpenClaw
Use Speak AI as a skill in OpenClaw-compatible agents.
How does authentication work?
The MCP server accepts two authentication methods: OAuth 2.1 with Dynamic Client Registration for the one-click connect flow, or a Speak AI API key passed as a Bearer token for manual setups, stdio mode, and the CLI.
See Authentication for how to get a key, what the REST token flow looks like, rate limits, and the tool error format.
Where’s the full tool reference?
Every tool, resource, and prompt the server exposes is documented in the tool reference, grouped by area: media, AI chat, folders and views, recorders, automations, clips, custom fields, webhooks, users and teams, dashboards, the meeting assistant, media embeds, text notes, exports, and search.
You don’t need to memorize tool names. Claude and ChatGPT pick the right ones based on what you ask.
Is there a Node SDK too?
The same package that runs the MCP server, @speakai/mcp-server, is also a library you can import directly into Node code. Use it when you’re embedding Speak AI’s tools inside your own service instead of connecting through an AI client.
See Node SDK for the exported functions and when to reach for them.
What does connecting actually grant access to?
Both methods, the permission popup and a pasted API key, grant the AI assistant read and write access to your whole Speak AI workspace. That includes viewing, modifying, and deleting recordings, folders, and clips.
Access is not continuous. Claude or ChatGPT reads specific data only when it calls a tool to answer something you asked, and your recordings stay in your Speak AI workspace.
To disconnect, remove the connector inside Claude or ChatGPT, or revoke a one-click connection at api.speakai.co/v1/oauth/connections.
How is this different from AI chat inside Speak AI?
Speak AI’s built-in AI Chat answers questions inside Speak. The MCP server lets you ask the same questions from Claude or ChatGPT, where you may already be drafting an email, planning content, or writing code. Use whichever fits the task.
What if the connection keeps failing?
A single failure mid-conversation is usually transient, so try the same prompt again. If it persists, reinstall the connector: revoke the one-click connection at api.speakai.co/v1/oauth/connections, then connect again.
If your company blocks custom connectors, that is an admin policy rather than a fault. Some Claude Team and Enterprise workspaces restrict them, and your workspace admin needs to allow https://api.speakai.co/v1/mcp.