Voice Memo to Text
io.github.lian-yangPublished by GitHub account lian-yangv1.0.0Updated Oct 25, 2026
AI transcription API: turn voice memos, meetings and audio URLs into text and SRT subtitles.
Overview
A remote transcription service that lets an assistant turn voice memos, meetings and audio URLs into text and SRT subtitles.
- What you can do
- Submit voice memos, meeting recordings and audio URLs for AI transcription and receive the resulting text back through the assistant. Produce SRT subtitle files alongside plain transcripts. The manifest lists no individual tools, so the exact operations are not documented here; the service is reached over a remote HTTP endpoint with OAuth sign-in.
- When to use it
- Worth adding when you regularly need spoken audio converted into written transcripts or subtitles and want to trigger that from an assistant rather than a separate app. Less useful if you only handle text or already have a transcription pipeline.
- Requirements
- A remote endpoint at the provider's site; no local package or runtime is needed. OAuth authentication is required, so you need an account with the provider and must complete its sign-in flow. Network access to the provider is required.
Installation
In SourceWeft
- Open Voice Memo to Text in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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/io.github.lian-yang%2Fvoicememotext/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. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"voice-memo-to-text": {
"type": "http",
"url": "https://www.voicememotext.com/api/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestOct 15, 2026
Score
67% 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
- Auth declaredRequired10 pts
- 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.