Speak AI vs Whisper
A side-by-side look at the Speak AI and Whisper MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Speak AI for speech-to-text work as a local process; choose Whisper for speech-to-text as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Speak AI when
- You need dedicated capabilities in the Speech-to-Text domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SPEAKAI_KEY, SPEAK_API_KEY. - You want tools like
get_signed_upload_url, upload_media, list_media.
Choose Whisper when
- You need dedicated capabilities in the Speech-to-Text domain.
- You prefer a local stdio subprocess transport.
- You want tools like
whisper_verify, whisper_rdap, whisper_identify.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Speech-to-Text | Speech-to-Text |
| Quality signal | 63/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | SPEAKAI_KEYSPEAK_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 3 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 189 | 5 |
| Full listing | View Speak AI | View Whisper |
Tools & capabilities
Speak AI tools 189
get_signed_upload_urlGet a pre-signed S3 URL for direct file upload to Speak AI storage. After getting the URL, PUT your file to it, then call upload_media with the S3 URL. For a simpler workflow, use upload_local_file instead which handles all steps automatically.upload_mediaImport an audio or video file into Speak AI from a URL and start transcription. Accepts a direct public file URL, a URL returned by get_signed_upload_url, or a page link from a supported platform, which the server resolves to the underlying media. Supported page links: YouTube, TikTok, Instagram, X/Twitter, Facebook, Reddit, SoundCloud, Twitch, Dailymotion, Streamable, Snapchat, Pinterest, Tumblr, Bilibili, VK, OK.ru and Rutube. Vimeo and Loom page links are not supported. Requires an active subscription. Creates a media item, bills its duration against the workspace's minutes or credits, and sends the media.created event to the workspace's webhooks and Slack channels if any are configured. The request fails if the file exceeds the plan's size limit or its duration cannot be read, and no mediaId is returned if the balance is insufficient. Returns mediaId and state right away while processing continues in the background. Use get_media_status until state is 'processed', then get_transcript and get_media_insights.list_mediaList and search media files in the workspace with filtering, pagination, and sorting. Use filterName for text search, mediaType to filter by audio/video/text, folderId for folder-specific results, and from/to for date ranges. Use the include param to embed additional data (transcripts, speakers, keywords) inline with each result, avoiding N+1 API calls. Returns mediaIds you can pass to get_transcript, get_media_insights, or ask_ai_chat. For deep full-text search across transcripts, use search_media instead.get_media_insightsRetrieve AI-generated insights for a processed media file — topics, sentiment, keywords, action items, summaries, and more. The media must be in 'processed' state (check with get_media_status first). For asking custom questions about a media file, use ask_ai_chat instead. For a video, data.thumbnail has the thumbnail: url, source (auto or custom), pending while a requested frame is being made, and error if that frame failed.get_transcriptRetrieve the full transcript for a media file with speaker labels and timestamps. Works on processed media and also returns the partial, in-progress transcript while a meeting bot is still recording (LIVE_TRANSCRIPT state). To fetch only the new sentences added since your previous call during a live meeting, use get_live_meeting_transcript instead. Use update_transcript_speakers to rename speaker labels after reviewing. For subtitle-formatted output, use get_captions instead.update_transcript_speakersUpdate or rename speaker labels in a single media transcript. Call get_transcript first to read the speaker list — a speaker's label is whatever it was last renamed to, not a fixed value, so ids from an earlier turn may be stale. Renaming a speaker to a name another speaker already has is refused as a collision. Re-sending a rename that has already been applied is a safe no-op, so do not retry a call that reported success.update_transcriptionEdit the official transcript text of a single media file by finding and replacing text. Replaces every occurrence of the original text with the replacement (leave replacement empty to delete the text) and reports how many occurrences were replaced. Use update_transcript_speakers to rename speaker labels instead.get_media_statusCheck the processing status of a media file. States: pending → transcribing → analyzing → processed (or failed). Poll this after upload_media until state is 'processed', then use get_transcript and get_media_insights to retrieve results. For a video, data.thumbnail has the thumbnail: url, source (auto or custom), pending while a requested frame is being made, and error if that frame failed.update_media_metadataUpdate metadata fields (name, description, tags, status) for an existing media file. Sends the media.updated event to the workspace's webhooks and Slack channels if any are configured.delete_mediaPermanently delete a media file and all associated transcripts and insights. Sends the media.deleted event to the workspace's webhooks and Slack channels if any are configured.get_captionsGet captions for a media file. Captions are separate from full transcripts and are formatted for display/subtitles.list_supported_languagesList all languages supported for transcription. Use the language codes when uploading media with a specific sourceLanguage.- +177 more on the listing page
Whisper tools 5
whisper_verifyVerify whether an address or FQDN is a real Whisper agent and, if so, whose - running the full keyless trust chain (reverse-DNS + DANE-EE TLSA pin + DNSSEC + JWS identity doc). Returns the verdict as JSON. Use it to check any peer's claimed identity before trusting it. No API key needed.whisper_rdapFetch the RDAP record for a Whisper IPv6 /128 (the IP-anchored registration object: who operates the agent identity, since when, under which tenant). Returns RDAP JSON. Use it to look up ownership/registration facts about an address. No API key needed.whisper_identifyName the vendor and operator role behind a host or IP in one call. Resolves a host/IP to its canonical vendor, category and operator roles (DNS_OPERATOR / CDN / ORIGIN_AS / MAIL_RECEIVER) with a confidence band. No API key needed. Docs: https://www.whisper.security/docs/whisper-graph/procedures/identifywhisper_assessGet a labelled threat posture for a host or IP - malicious, benign, or unknown. Returns a posture label + severity band + sub-labels + coverage + evidence for an indicator; benign-allowlisted vs malicious-evidenced, never a bare score. No API key needed. Docs: https://www.whisper.security/docs/whisper-graph/procedureswhisper_explainScore an indicator against the threat feeds and explain exactly why. Threat-intel scorer: score + level + human explanation + the feeds it is listed in (feedId, weight, firstSeen/lastSeen). Two live forms: bare CALL explain($v) (full columns) and CALL whisper.explain($v) (restricted YIELD). No API key needed. Docs: https://www.whisper.security/docs/whisper-graph/procedures/explain
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Speak AI
{
"mcpServers": {
"speak-ai": {
"command": "npx",
"args": [
"-y",
"@speakai/mcp-server"
],
"env": {
"SPEAKAI_KEY": "YOUR_SPEAKAI_KEY_HERE",
"SPEAK_API_KEY": "YOUR_SPEAK_API_KEY_HERE"
}
}
}
}
Whisper
{
"mcpServers": {
"whisper": {
"command": "npx",
"args": [
"-y",
"@whisper-security/whisper-mcp"
]
}
}
}
Frequently asked questions
Speak AI is categorized under Speech-to-Text and uses a local stdio subprocess. Whisper belongs to Speech-to-Text and uses a local stdio subprocess. Pick Speak AI for speech-to-text work and Whisper for speech-to-text.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Speak AI has no declared pricing — check the project's own site. Whisper has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add speak-ai and whisper as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Speak AI has a quality signal of 63/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Whisper has 61/100 (Good) with 1 views, 0 installs and 3 GitHub stars.