Sleekdocs Translate

com.sleekdocsPublished by sleekdocs.comOfficial publisherv1.0.0Updated Oct 29, 2026

Find missing translations in your app, propose texts and publish and deploy them to your CDN.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Remote Sleekdocs server that lets an assistant find missing app translations, propose texts, and publish and deploy them to your CDN.

What you can do
  • Detect missing translations in an app's localization files.
  • Propose translation texts for the gaps found.
  • Publish the translations and deploy them to the CDN.
  • Connect over a hosted remote endpoint with OAuth sign-in, or an API key header for clients that cannot use OAuth.
When to use it
Useful when you maintain a localized app with Sleekdocs and want an assistant to spot untranslated strings, draft the missing texts, and push them live without leaving the chat.
Requirements
A remote endpoint at translate.sleekdocs.com over streamable HTTP; OAuth sign-in is required. Clients that cannot use OAuth can send an Authorization header with a Sleekdocs API key. A Sleekdocs account and project with CDN deployment are implied.
Before you install
The server can publish and deploy translations to your CDN, so changes go live and may overwrite existing texts. The Authorization header carries a Sleekdocs API key secret; keep it out of logs and shared transcripts.

Installation

In SourceWeft

  1. Open Sleekdocs Translate in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.sleekdocs%2Ftranslate/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "sleekdocs-translate": {
      "type": "http",
      "url": "https://translate.sleekdocs.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

83% 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
  • 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.