Belindoc Translator
com.belindocPublished by belindoc.comOfficial publisherv0.1.7Updated Oct 24, 2026
Translate PDF, Word, Excel, Markdown, image and video files with Belindoc, and rewrite subtitles.
Overview
Belindoc Translator lets an assistant translate PDF, Word, Excel, Markdown, image and video files and rewrite subtitles through Belindoc.
- What you can do
- Translate documents and media files: PDF, Word, Excel, Markdown, images and video, using the Belindoc service through the assistant's tool calls. Rewrite subtitles for video content. Report task status, progress and errors in the language chosen by MCP_LOCALE. No individual tools are listed in the manifest, so the exact operations are not documented here.
- When to use it
- Useful when you need to translate or localize documents, spreadsheets, images, videos or subtitles and want an assistant to drive the Belindoc service rather than doing it by hand.
- Requirements
- A Belindoc account and API key (ft_ prefix, 40 characters), created at belindoc.com under Open Platform → API Keys. The key is passed as the BELINDOC_API_KEY environment variable for the local uvx package or as an Authorization Bearer token for the remote endpoint. Network access to the Belindoc service. MCP_LOCALE optionally sets the language of status and error messages.
Installation
In SourceWeft
- Open Belindoc Translator in the dashboard and add it to a workspace.
- Connect Authorization token 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/com.belindoc%2Fbelindoc-mcp/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": {
"belindoc-translator": {
"type": "http",
"url": "https://mcp.belindoc.com/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Tools
0Version history
1- v0.1.7LatestSep 21, 2026
Score
50% 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
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.