Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Search recordings, summarize meetings, create clips, and automate workflows from your AI assistant.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
SPEAK_API_KEY, SPEAK_BASE_URLValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://api.speakai.co/v1/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"speakai": {
"command": "npx",
"args": [
"-y",
"@speakai/mcp-server"
],
"env": {
"SPEAK_API_KEY": "your-value",
"SPEAK_BASE_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add --transport http speakai https://api.speakai.co/v1/mcpclaude mcp add speakai --env SPEAK_API_KEY=your-value --env SPEAK_BASE_URL=your-value -- npx -y @speakai/mcp-serverFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"speakai": {
"url": "https://api.speakai.co/v1/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"speakai": {
"command": "npx",
"args": [
"-y",
"@speakai/mcp-server"
],
"env": {
"SPEAK_API_KEY": "your-value",
"SPEAK_BASE_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"speakai": {
"type": "http",
"url": "https://api.speakai.co/v1/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"speakai": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@speakai/mcp-server"
],
"env": {
"SPEAK_API_KEY": "your-value",
"SPEAK_BASE_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://api.speakai.co/v1/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
SPEAK_BASE_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account speakai, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 128 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: SPEAK_API_KEY
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (1.41.1) reached the registry 7 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Connect Speak AI to Claude, ChatGPT and other AI assistants in 60 seconds
For researchers, revenue teams, meeting-heavy teams, and media workflows.
No Terminal. No npm. No JSON config files.
Works with Claude, ChatGPT, Cursor, VS Code, Windsurf, Muse, OpenClaw and any MCP client.
Installation guide at docs.speakai.co/mcp →
Speak AI transcribes your interviews, sales calls, research sessions, webinars, podcasts, and team meetings, then extracts AI insights like summaries, action items, sentiment, and themes.
This connector is built on MCP, the open standard AI assistants use to connect to apps, so it brings all of that into Claude, ChatGPT, Cursor, Muse or any other MCP-compatible assistant. Once installed, you can ask:
The AI does the searching, summarizing, and citing. Your recordings stay in your Speak AI workspace; the assistant only queries them through this connector.
Two paths to install: pick whichever feels easier. The one-click connect path approves access via a permission popup; the manual path pastes an API key into a header.
Don't know which one to pick? Install it in the AI assistant you already use. Every option below connects to the same Speak AI workspace.
Speak AI's connector address (paste this into your AI tool's connector settings; it's the same idea as pasting a Zoom link into your calendar):
https://api.speakai.co/v1/mcp
https://api.speakai.co/v1/mcp, then click AddWhat each step looks like (screenshots)
3. Add custom connector dialog: name and URL filled in.
5. Connected: Speak AI tools appear in your connector list.
Developer alternative: manual setup with an API key
Get a key at app.speakai.co/developers/apikeys, then in step 3 expand Advanced settings and add Authorization = Bearer before clicking Add.
https://api.speakai.co/v1/mcpDeveloper alternative: manual setup with an API key
Get a key at app.speakai.co/developers/apikeys, then in step 2 also expand Custom headers and add:
AuthorizationBearer Then click Add.
https://api.speakai.co/v1/mcpWhat each step looks like (screenshots)
1. Connect screen in ChatGPT: paste the connector URL and pick OAuth.
2. Confirm and continue: ChatGPT asks you to continue to Speak AI.
3. Authorize on Speak AI: sign in or click Confirm if you're already signed in.
4. Connected: Speak AI now shows in your ChatGPT connector list.
Trouble connecting?
A few things we've seen during early access:
Still stuck? Email success@speakai.co.
Recommended: install from the official Claude Code plugin marketplace:
/plugin marketplace add claude-plugins-official/plugin install speakai@claude-plugins-official/reload-pluginsgetting-started skill and paste your Speak AI API key. Generate one at app.speakai.co/developers/apikeys.If /plugin install doesn't find Speak AI, refresh the local catalog with /plugin marketplace update claude-plugins-official and retry.
Developer alternative: manual HTTP transport
Skip the plugin and add the connector directly:
claude mcp add speakai --transport http --url https://api.speakai.co/v1/mcp
Claude Code will open an OAuth window for sign-in. To bypass OAuth and pass a Bearer token instead:
claude mcp add speakai --transport http --url https://api.speakai.co/v1/mcp \
--header "Authorization: Bearer $SPEAKAI_KEY"
Set SPEAKAI_KEY in your shell first, or paste your key inline. Generate a key at app.speakai.co/developers/apikeys.
Click the button. Cursor registers itself automatically and opens the permission popup. Sign in to Speak AI and click Allow.
Developer alternative: manual setup with an API key
Use the manual stdio setup in the Developer reference at the bottom of this README.
Click the button. VS Code registers itself automatically and opens the permission popup. Sign in to Speak AI and click Allow.
Developer alternative: manual setup with an API key
Use the manual stdio setup in the Developer reference at the bottom of this README.
Windsurf connects to the remote server over HTTP through its MCP config file. Follow the steps at docs.speakai.co/mcp/setup/windsurf.
Muse, Meta's personal AI assistant, connects with one-click OAuth and no API key. Follow the steps at docs.speakai.co/mcp/setup/muse.
Speak AI is published as a skill on ClawHub for OpenClaw-compatible agents.
clawhub install speakai from the ClawHub CLISPEAK_API_KEY environment variable. Generate one at app.speakai.co/developers/apikeys.For developers calling the Responses API directly. Pass the bearer token in the tool config:
{
"tools": [ { "type": "mcp", "server_url": "https://api.speakai.co/v1/mcp", "authorization": "Bearer YOUR_SPEAK_API_KEY" } ] }
Get a key at app.speakai.co/developers/apikeys.
Any assistant that supports remote MCP servers can connect. Add https://api.speakai.co/v1/mcp as a remote (Streamable HTTP) server, then either approve the Speak AI permission popup (OAuth 2.1 with Dynamic Client Registration) or send a Speak AI API key as Authorization: Bearer . All setup guides: docs.speakai.co/mcp.
When you click Allow on the permission popup (or paste your Speak AI API key into your AI assistant), you're authorizing that AI assistant to read and modify your Speak AI workspace on your behalf: including media files, transcripts, and AI insights.
For questions about data handling, see speakai.co/privacy or email success@speakai.co.
You shouldn't need to be technical to install this. If anything is confusing or doesn't work:
Speak AI ships 189 tools your AI assistant can call. You don't need to memorize them; your AI assistant picks the right ones based on what you ask. Examples by category:
| A
Only the beginning is shown; read the rest in the repo