CleoLM vs BibiGPT
A side-by-side look at the CleoLM and BibiGPT MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
CleoLMSpeech-to-TextSearch and cite timestamped YouTube and podcast transcripts; transcribe any video or episode.37FairAuth: not declaredB
BibiGPTSpeech-to-Text · Remote HTTP/SSESummarize, transcribe and search YouTube, Bilibili, TikTok, podcasts and other videos with AI.57GoodAuth: not declaredVerdict: choose CleoLM for speech-to-text work; choose BibiGPT for speech-to-text over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
BChoose BibiGPT when
- You need dedicated capabilities in the Speech-to-Text domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
summarize_video, summarize_video_with_config, summarize_by_chapter.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C CleoLM | B BibiGPT |
|---|---|---|
| Category | Speech-to-Text | Speech-to-Text |
| Quality signal | 37/100 · Fair | 57/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 128 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 6 |
| Full listing | View CleoLM | View BibiGPT |
Tools & capabilities
CleoLM tools
No tool names declared yet. Check the project README from the listing page.
BibiGPT tools 6
summarize_videoSummarize a video or podcast URLsummarize_video_with_configSummarize with custom prompt, model, languagesummarize_by_chapterChapter-by-chapter summaryget_subtitleGet transcript/subtitles with timestampscreate_summary_taskCreate async task for long videosget_task_statusCheck async task status
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.
CleoLM
No confirmed install command for CleoLM yet — follow the setup steps linked from its listing page rather than a guessed package name.
BibiGPT
{
"mcpServers": {
"bibigpt": {
"url": "https://bibigpt.co/api/mcp"
}
}
}
Frequently asked questions
CleoLM is categorized under Speech-to-Text and uses an install path we have not confirmed yet. BibiGPT belongs to Speech-to-Text and uses a remote HTTP/SSE transport. Pick CleoLM for speech-to-text work and BibiGPT 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. CleoLM has no confirmed install command yet — follow its own setup instructions.
CleoLM has no declared pricing — check the project's own site. BibiGPT 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 cleolm and bibigpt as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, CleoLM has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. BibiGPT has 57/100 (Good) with 0 views, 0 installs and 128 GitHub stars.