Sitecore MCP: LLM Page Translation in a Few Prompts!

Sitecore is all about the content. It has many other features and components, but content is still at the center of the Sitecore ecosystem. And Sitecore is often used for multilingual websites. We have built 60+ Sitecore projects over the years. And more than half of them were multilingual. There are different approaches to the translations. But all of them could be divided into big groups. Translation could be done in-house or outsourced. And translation could be done by a human or a machine. There are a lot of vendors who provide translations for Sitecore: Lionbridge, LanguageWire, Translate Plus, XTM, WordBee BeeBox, iLang, Crowdin, Memsource, GlobalLink, GPI, and many others. We worked with LanguageWire and Lionbridge machine translations, and they provide decent translation results.

We always mean AI when we talk about machine translations in 2025. It can be neural machine translation(NMT) or large language models(LLM). I will not stop at differences in this article, both approaches give decent translation results.

Usually, all translation providers have their UI interfaces, APIs. You need to connect Sitecore to them, configure, set up, time to time write some additional code. But AI evolves. LLM agents can split big tasks into small ones. It can perform small tasks one by one and implement the results using the model context protocol.

Model Context Protocol

Model Context Protocol is an open protocol that enables seamless integration between LLM applications and external data sources and tools. It is like giving LLM “hands” to do the work. LLM already has a “brain”. It can tell you what to do. It can answer your questions. It can talk to you. MCP allows your LLM not only to talk. It allows making actions. For example: reading, creation, updating, and deletion of items in databases, files, and CMSs.

We implemented the model context protocol for Sitecore. It covers the basic Sitecore API for working with items. It is only the beginning. But the results exceeded our expectations. LLM Agents can do a lot of your routine Sitecore work just in a few messages! Isn’t it the magic?

Translation of Sitecore content. Sample.

I will describe a new possible way of content translation. It is a simplified approach to show the power of LLM Agents together with Sitecore MCP. Production usage will include security configuration, content workflows, and additional MCP tools to improve your process.

We need something to translate. We will take the Sitecore Verticals Demo website. BTW, we reimplemented it on Astro from Next.js and achieved almost twice faster speed on mobile.

Step 1: Available languages

Before translation, let's check if LLM has proper access to Sitecore and can get information from it.

I will use Cursor together with Claude 3.7 Sonnet. It is possible to do the same everywhere where MCP is supported(VS Code, Claude desktop, Cline, etc.). The Claude 3.7 model is not the best. Gemini-2.5-pro can give you better results. But Claude 3.7 is included in the Cursor subscription, and I will show that you can get decent results without any extra payments for additional API calls.

What languages are available in Sitecore?

Correct. Claude was able to find the right MCP tool item_service_get_languages, run it, and explain the results. Yes, indeed, we have 3 languages:

Step 2: Adding the new language

Let’s ask Claude to add a new language to Sitecore. Let it be Spanish.

Can you add Spanish please?

Agent successfully added a new language and verified that it was added. Are you impressed? Hold on. It is only the beginning!

Step 3: Page Translation

We need a page to translate. We have ~140 pages in our demo. I tried a few, and the results are pretty consistent. Let it be Services page /sitecore/content/Verticals/Services/Home/services.

It contains local datasources, global datasources, page design, and partial designs. It is a typical Sitecore SXA Headless page, nothing unusual.

Can you translate /sitecore/content/Verticals/Services/Home/services page into Spanish?

The Agent did 14 actions, I wasn’t even able to put it into one screenshot!

The summary looks quite promising. But before the check, we need to update the languages list on our website. It is hardcoded, as it is a demo site.

Step 4: Add language to the code

Adding language to .js file is an easy task. I would never use LLM Agent for it, only if it is some subtask of a bigger task. It is quicker to open languages.js and add one line of code. But let’s use an agent for this task as well. Do proper vibe coding, without touching the code with our hands! Only for curiosity and demo purposes, of course.

Can you add Spanish language to sxastarter Astro website?

The action is correct, and we accept the proposed changes.

Step 4: Check our results

We can check Sitecore items one by one, or we can open the page and check the results.

Not bad. We can see that Agent translated the page itself, the local datasources, but skipped the header, footer, and one component with a global datasource. Let’s remind them about about missed translation.

Step 5: Global datasource translation

We want to translate the missed parts. But we don’t want to be very specific. The agent should work for us. Not we for agent! We will not tell which component, which datasource, or what is missing.

You missed global datasource used on the page. Can you translate all datasources for /sitecore/content/Verticals/Services/Home/services page, please?

Agent overperformed and deserved a bonus! It found rendering ID 3a7dc4f0-472c-4c73-b428-a3155c8853f2 with a datasource that is not translated. But, it didn’t stop there. It decided to check the Footer! I didn’t expect this proactivity from LLM Agent! Was it the magic “please” at the end?

And the webpage is now almost translated!

Step 6: Final touch: Header

We see only four words that are not translated.

• “Contact” button — it is the link to another Sitecore page.
• “About”, “Portfolio”, and “Insights” links translation are missing in the header. “Services” is translated because it is our page.

These are separate pages. That is another task to translate other pages, but we can remind the Agent about texts that are not translated and ask them to translate them.

You missed “About”, “Portfolio”, and “Insights” translation in the header menu. Can you translate them?

You missed “Contact” translation in the header menu. Can you translate it?

Everything is translated now! Did you expect that it would be so easy?

Conclusion

LLM Agents, together with MCP servers, are the future! We wrote MCP servers to cover the basic Sitecore API, and we can translate the full Sitecore page. And it requires only six prompts:

• Can you add Spanish to Sitecore, please?
• Can you translate /sitecore/content/Verticals/Services/Home/services page into Spanish?
• Can you add Spanish language to sxastarter Astro website?
• You missed global datasource used on the page. Can you translate all datasources for /sitecore/content/Verticals/Services/Home/services page, please?
• You missed “About”, “Portfolio”, and “Insights” translations in the header menu. Can you translate them?
• You missed “Contact” translation in the header menu. Can you translate it?

I didn't optimize the prompts. I think combining them into one or two prompts is possible. I wanted to show you the process step by step. The way a regular content manager will ask LLM to do it. And the way LLM Agent responds to requests and performs the actions!

That is a simplified example. The production use case will include batch translation, the configuration of access rights for the MCP server user, an approval workflow to check that everything looks good by a human, the browser MCP server to allow the LLM Agent to see its changes, and probably another MCP server for translation if you have any translation preferences, etc. But it will be done beforehand the translation process. The translation will be the same few sentences, and the LLM Agent will do everything for you!

Are you excited? Scared? Interested? Drop me a line! I will gladly make a demo for you, discuss your use cases, and help you apply it to your project.

Now, the cost of translation starts from 10 USD per month with Pro Cursor subscriptions! None of the translation companies can compete with this price. Save costs on translation and spend on something else! Also, speed is the key. I don’t know any Sitecore translation connectors that can find all datasources automatically, you need to configure them. With the LLM Agent approach, your content manager will be able to concentrate on producing the content, as they don’t need to look for items for translation in the Sitecore tree anymore.

And stay tuned. It is only the beginning of Sitecore MCP server adventures. We will translate the whole website. We will teach Sitecore PowerShell to speak English. We will generate Sitecore content. The Sitecore MCP server will be used for multiple tasks and to automate almost any routine Sitecore work. Wanna be on the edge of AI technologies? We have capacity and are looking for projects. You will get seasoned Sitecore developers superpowered with AI. And the 10x engineer myth is not a myth anymore.