{"id":105,"date":"2026-09-23T11:24:44","date_gmt":"2026-09-23T11:24:44","guid":{"rendered":"https:\/\/docs.latw.ai\/uncategorized\/mcp-server-2\/"},"modified":"2026-09-23T11:24:44","modified_gmt":"2026-09-23T11:24:44","slug":"mcp-server-2","status":"publish","type":"post","link":"https:\/\/docs.latw.ai\/pl\/latw-for-polylang\/mcp-server-2\/","title":{"rendered":"Translating from Claude and ChatGPT (MCP)"},"content":{"rendered":"

Available in LATW AI Translation for Polylang PRO<\/strong>.<\/em><\/p>\n

Everywhere else in this plugin, translating means sending your text to an AI engine and paying that
\nengine for the answer. The MCP server turns that around. You connect your site to the AI assistant
\nyou already use \u2014 Claude or ChatGPT \u2014 and translate from inside the conversation. The assistant
\nwrites the translation; the plugin puts it into Polylang.<\/p>\n

There is no API bill.<\/strong> No key is used, no engine is called, and every translation made this way
\nshows a cost of $0.00 on the History screen. You are using the subscription you already pay for.<\/p>\n

MCP \u2014 Model Context Protocol \u2014 is the standard those assistants use to talk to outside systems.
\nSwitching the server on gives the assistant a set of tools: find untranslated pages, take one for
\ntranslation, send the translation back, look something up in your glossary.<\/p>\n

In practice a session looks like this:<\/p>\n

\n

You:<\/strong> What still needs translating into German?<\/p>\n

Claude:<\/strong> Eleven pages have no German version. The most recently edited are About<\/em>, Shipping &
\nReturns<\/em> and Our Suppliers<\/em>.<\/p>\n

You:<\/strong> Do the three of them.<\/p>\n

Claude:<\/strong> (takes each page, translates it, sends it back)<\/em> All three are translated and live.
\nAbout<\/em> is at \/de\/uber-uns\/.<\/p>\n<\/blockquote>\n

What you need before you start<\/h2>\n
    \n
  • An active PRO licence<\/strong>.<\/li>\n
  • Polylang<\/strong>, with at least two languages set up, as for any other translation this plugin makes.<\/li>\n
  • HTTPS.<\/strong> Assistants run on someone else’s servers and will not connect to an unencrypted site.<\/li>\n
  • A Claude<\/strong> or ChatGPT<\/strong> plan that allows custom connectors. On ChatGPT that means Plus, Pro,
    \nBusiness, Enterprise or Edu \u2014 the free tier cannot add one.<\/li>\n<\/ul>\n

    Switching it on<\/h2>\n
      \n
    1. Go to AI Translation \u2192 Settings \u2192 MCP<\/strong>.<\/li>\n
    2. Turn on MCP server<\/strong>.<\/li>\n
    3. Press Generate token<\/strong>. The token is the password to this door \u2014 anyone holding it can read and
      \ntranslate your site’s content.<\/li>\n
    4. Decide what the assistant may reach, under What the assistant may do<\/strong>. Posts and pages are
      \nalways available. Status and costs, and the glossary, are on by default; interface strings and
      \ncategories are off until you want them.<\/li>\n
    5. Press Save Changes<\/strong>, then Test connection<\/strong>. That check calls the server the same way an
      \nassistant would and tells you plainly if something between the internet and WordPress is in the
      \nway.<\/li>\n<\/ol>\n

      The screen then shows two addresses. Which one you use depends on the application.<\/p>\n

      Connecting Claude<\/h2>\n

      Claude Desktop and claude.ai.<\/strong> Open Settings \u2192 Connectors \u2192 Add custom connector<\/strong>, give it a
      \nname, and paste the Address (token in URL)<\/strong> from the MCP tab. Press Show<\/strong> next to the field
      \nfirst \u2014 the screen masks it until you do. There is nothing else to fill in: the token is part of the
      \naddress.<\/p>\n

      Claude Code.<\/strong> The MCP tab shows the exact command, ready to copy:<\/p>\n

      claude mcp add my-site https:\/\/example.com\/wp-json\/latw-mcp\/v1\/http --transport http --header \"Authorization: Bearer YOUR_TOKEN\"<\/code><\/pre>\n
      Run it in a terminal, then \/mcp<\/code> inside Claude Code to confirm the site is listed.<\/p>\n
      Connecting ChatGPT<\/h2>\n
      Custom connectors are hidden until you switch developer mode on, so this is two trips into Settings.<\/p>\n
      First, switch developer mode on.<\/strong> Open Settings \u2192 Security and login<\/strong>, find Developer mode<\/strong>
      \nand turn it on.<\/p>\n
      Then add the connector.<\/strong> Open Settings \u2192 Plugins \u2192 Browse plugins<\/strong> and press the +<\/strong> in the
      \ntop right corner. Fill the form in:<\/p>\n
        \n
      • Name<\/strong> \u2014 whatever you want to see in the conversation, for example your site’s name.<\/li>\n
      • Address<\/strong> \u2014 the Address (token in URL)<\/strong> from the MCP tab.<\/li>\n
      • Authentication<\/strong> \u2014 No Auth<\/strong>. The token is already part of the address, so there is nothing
        \nelse to fill in.<\/li>\n
      • Tick I understand and want to continue<\/strong>, then press Create<\/strong>.<\/li>\n<\/ul>\n
        ChatGPT loads the connector, which takes a moment, and then shows Connect<\/strong>. Press it, and the
        \nsite’s tools are available in the conversation.<\/p>\n
        Asking for a translation<\/h2>\n
        Once connected, ask in plain language. The assistant has the tools; you do not need to name them.<\/p>\n
          \n
        • “What pages have no French translation yet?”<\/em><\/li>\n
        • “Translate the About page into German and French.”<\/em><\/li>\n
        • “The pricing page changed \u2014 update the Polish version.”<\/em><\/li>\n
        • “How much have translations cost this month?”<\/em><\/li>\n
        • “Show me the German version of the pricing page \u2014 does it read naturally?”<\/em><\/li>\n
        • “The Polish About page says ‘Zacznij zakupy’ on the button. Change it to ‘Przejd\u017a do zakup\u00f3w’.”<\/em><\/li>\n
        • “What was the last thing translated?”<\/em><\/li>\n
        • “Change the Polish address of the About page to o-nas-firmy.”<\/em><\/li>\n
        • “Translate only the SEO title and description of the About page into Polish.”<\/em><\/li>\n<\/ul>\n
          The translation is written into Polylang exactly where the plugin would have written it. It appears
          \nin AI Translation \u2192 History<\/strong>, in Polylang’s own language switcher, and on the front end, and you
          \ncan edit it afterwards in the block editor like any other translation.<\/p>\n
          Which parts of a page the assistant is handed \u2014 the content, the custom fields, the SEO title and
          \ndescription \u2014 is decided by this plugin’s own settings, under Settings \u2192 Translation<\/strong>, and the
          \nrules are the same however you translate.<\/p>\n
          Reviewing and correcting a translation<\/h2>\n
          You do not have to accept a translation as it came out, and you do not have to redo the whole page
          \nto change one line.<\/p>\n
          Ask to see it, and the assistant reads the current translation field by field beside the source it
          \ncame from:<\/p>\n
          \n
          You:<\/strong> Show me the Polish About page next to the original.<\/p>\n
          Claude:<\/strong> (lists each piece)<\/em> The heading is “O nas”, the intro is \u2026, the button says “Zacznij
          \nzakupy”.<\/p>\n
          You:<\/strong> The button should say “Przejd\u017a do zakup\u00f3w”.<\/p>\n
          Claude:<\/strong> Changed. The rest of the page is untouched.<\/p>\n<\/blockquote>\n
          Only the line you asked about is rewritten. Everything else keeps the wording it already had,
          \nincluding any corrections you made by hand in the editor.<\/p>\n
          Two things are worth knowing:<\/p>\n
            \n
          • A page translated by hand from scratch cannot be listed this way.<\/strong> This plugin keeps no record
            \nof which text produced which translation unless it made the translation itself, so there is
            \nnothing to line up, and the assistant will say so rather than guess.<\/li>\n
          • A first translation is all-or-nothing.<\/strong> Until a page has a translation, every field has to be
            \nfilled in one go \u2014 there is nothing to keep for the ones left out, so they would be published
            \nempty. The assistant is told this and will not half-translate a page by accident.<\/li>\n<\/ul>\n
            Addresses of translated pages<\/h2>\n
            When Polylang creates a translation it builds its address from the translated title, so About<\/em>
            \nbecomes \/pl\/o-nas\/<\/code> on its own. That is usually what you want, and occasionally not \u2014 a title that
            \ntranslates to the same words, or a page whose heading and URL should read differently.<\/p>\n
            You can ask for a different one, either while translating or long afterwards:<\/p>\n
            \n
            You:<\/strong> Translate the About page into Polish, and make the address \/pl\/o-nas-firmy\/.<\/p>\n<\/blockquote>\n
            \n
            You:<\/strong> Change the Polish address of the About page to poznaj-nasza-firme.<\/p>\n<\/blockquote>\n
            Only the translation moves. The original page keeps its own address, and so does every other
            \nlanguage. If the address you ask for is already used by another page in that language, WordPress
            \nappends a number and the assistant tells you which address it actually got.<\/p>\n
            For posts<\/strong>, changing the address of something already published is safe: WordPress remembers the
            \nold address and sends anyone using it to the new one, exactly as it does when you rename a post in
            \nthe editor.<\/p>\n
            Pages are the exception.<\/strong> WordPress only keeps old addresses for non-hierarchical content, and
            \npages are hierarchical \u2014 so the old address of a page simply stops working, and any link pointing at
            \nit lands on a 404. If the page was already published and linked to, add a redirect yourself.<\/p>\n
            What it will not do<\/h2>\n
            Be clear about this before you promise it to anyone:<\/p>\n
              \n
            • It is not bulk translation.<\/strong> The assistant works page by page, in a conversation, and long
              \npages use up a lot of it. For dozens of posts, use Automatic Translation<\/strong> and pay the API bill \u2014
              \nthat is what it is for. This is for the pages you care about individually.<\/li>\n
            • The quality is the assistant’s, not the plugin’s.<\/strong> Your Translation Prompt<\/strong> and Website
              \nDescription<\/strong> are handed over as guidance, but nothing enforces them. An assistant that decides to
              \nparaphrase will paraphrase.<\/li>\n
            • The glossary is advice here, not a rule.<\/strong> Your terms are sent with every job and assistants
              \nfollow them well, but the plugin cannot check the result the way it does on its own pipeline.<\/li>\n
            • There is no “outdated” list.<\/strong> Find content to translate<\/em> can tell you what has no translation
              \nyet, but not what changed since the last one \u2014 ask the assistant to read a specific page with
              \nlatw_get_translation<\/em> instead.<\/li>\n
            • A conversation can stop halfway.<\/strong> If it does, the page is left with an open job. Ask the
              \nassistant to “list open translation jobs”<\/em> and either finish or cancel them; open jobs also show
              \nas awaiting_mcp<\/code> on the History screen.<\/li>\n
            • One token for the whole site.<\/strong> There is no per-person access and no list of connected
              \napplications. Generating a new token disconnects everything using the old one.<\/li>\n<\/ul>\n
              About the token<\/h2>\n
              The token is shown masked, and Show<\/strong> reveals it \u2014 you will need to read it back when you connect
              \na second application.<\/p>\n
              The two addresses differ in more than convenience. The one with the token in the URL is the easy
              \none, and it is what Claude Desktop and ChatGPT need, but a secret in an address ends up in your
              \nserver’s access logs and in the browser history of whoever pasted it. The address using the
              \nAuthorization<\/code> header keeps the token out of both, and is worth using wherever the application
              \nsupports it.<\/p>\n
              Either way: treat the token like an administrator password, and press Generate a new token<\/strong> the
              \nmoment you think someone else has seen it.<\/p>\n
              The connected assistant acts as the WordPress user who generated the token, with that user’s
              \npermissions. If that account is deleted or loses its administrator role, the token stops working.<\/p>\n
              When something goes wrong<\/h2>\n
              Test connection<\/strong> on the MCP tab is the first thing to try \u2014 it separates “the plugin is fine and
              \nyour assistant is misconfigured” from “nothing can reach this site at all”.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
              What you see<\/th>\nWhat it usually means<\/th>\n<\/tr>\n<\/thead>\n
              The assistant says it cannot reach the server<\/td>\nThe address is wrong, the server is switched off, or the site is not on HTTPS.<\/td>\n<\/tr>\n
              Test connection says the token did not arrive<\/td>\nYour host strips the Authorization<\/code> header before PHP sees it. Use the address with the token in the URL instead.<\/td>\n<\/tr>\n
              Test connection cannot reach the site at all<\/td>\nA firewall or a security plugin is blocking \/wp-json\/<\/code>. Allow \/wp-json\/latw-mcp\/<\/code> through.<\/td>\n<\/tr>\n
              A 404 from the address<\/td>\nThe server is switched off, or the licence is not active.<\/td>\n<\/tr>\n
              A 401<\/td>\nThe token is wrong \u2014 copy it again from the MCP tab.<\/td>\n<\/tr>\n
              The assistant lists no tools<\/td>\nThe licence expired, or every tool group was switched off.<\/td>\n<\/tr>\n
              Rows stuck at awaiting_mcp<\/code><\/td>\nA conversation ended mid-job. Ask the assistant to list and cancel open jobs.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
              The AI Translation \u2192 Logs<\/strong> page records what happened on this site’s side, and
              \nSettings \u2192 Advanced \u2192 Debug Mode<\/strong> adds the detail.<\/p>\n","protected":false},"excerpt":{"rendered":"
              Available in LATW AI Translation for Polylang PRO. Everywhere else in this plugin, translating means sending your text to an AI engine and paying that engine\u2026<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_latwm_translated_slug":"","footnotes":""},"categories":[17],"tags":[],"class_list":["post-105","post","type-post","status-publish","format-standard","hentry","category-latw-for-polylang"],"_links":{"self":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/105","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/comments?post=105"}],"version-history":[{"count":0,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/105\/revisions"}],"wp:attachment":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/media?parent=105"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/categories?post=105"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/tags?post=105"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}