Vibe2Text — AI audio & video transcription with speaker diarization
ru.vibe2textPublished by vibe2text.ruOfficial publisherv1.0.1Updated Oct 27, 2026
Audio & video to text, Russian-first: diarization, timestamps, summary, action items, subtitles.
Overview
Remote MCP endpoint that turns audio and video into Russian-first transcripts with speaker diarization, timestamps, summaries, action items and subtitles.
- What you can do
- Transcribe audio and video files into text, with Russian as the primary language.
- Label speakers and attach timestamps to the transcript.
- Produce summaries, action items and subtitles from the transcription output.
- No individual tools are listed in the manifest, so the exact operations are not documented.
- When to use it
- Useful when you want an assistant to convert Russian-language recordings, meetings or videos into structured text, speaker-labelled transcripts, summaries or subtitle files without running transcription software locally.
- Requirements
- A remote MCP endpoint at the provider's API host, reachable over streamable HTTP; no local package or runtime is needed. The manifest declares no authentication, environment variables or headers, so any account or key requirement is undocumented.
Installation
In SourceWeft
- Open Vibe2Text — AI audio & video transcription with speaker diarization in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ru.vibe2text%2Fvibe2text/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"vibe2text-ai-audio-video-transcription-w": {
"type": "http",
"url": "https://api.vibe2text.ru/mcp/"
}
}
}Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
28% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.