SUPPORT

Keep the document moving.

Short answers for installation, URL fetches, file formats, and a batch that will not validate.

Applies to: iPlugin TranslateMCP: https://iplugin.dev/translate/mcp

Install and open

Add iPlugin Translate from its review or installation link in a ChatGPT client that supports custom MCP servers. After installation, open the workbench from the plugin list or ask ChatGPT to open Translate. No account, OAuth connection, or API key is required.

If the plugin does not appear, fully quit and reopen the ChatGPT client, then confirm the plugin is installed and enabled. If the server shows as unavailable, retry after a minute and check the health endpoint.

Which files can I translate?

Text-based files: .md, .markdown, .json, .txt, and similar UTF-8 text. JSON must parse as valid JSON. PDF, DOCX, XLSX, images, and other binary formats are not accepted; export them to text first.

Why was my URL refused?

The fetcher only accepts public http / https pages on standard ports. Private, localhost, link-local, credential-bearing, and non-standard-port URLs are blocked on purpose. If a public article fails, it may be behind a login, paywall, bot challenge, or JavaScript-only rendering. Open the article and paste the text instead.

A batch was rejected

Ask ChatGPT to resubmit only the rejected segment ids and to keep every ⟦n⟧ placeholder exactly once. Placeholders stand for code, links, URLs, or template variables and must not be translated or removed. If the document expired, start a new translation from the original source.

Copy or download is disabled

The actions unlock when every segment has been translated and validated. Ask ChatGPT to finish the remaining batches, then use Copy or Download in the workbench. If the session expired, start again; documents live in memory for at most two hours.

Privacy and deletion

Documents are processed in memory for the session and are not written to a database. See the privacy policy and data deletion page. Do not send sensitive content in a support request.

Contact

Email micromvp@gmail.com. Include the plugin name, the client and version, the approximate time, the document type, and any error text shown in the conversation or workbench. Do not include the document itself, passwords, API keys, or personal data. We aim to reply within a few business days.