Denne integrationsguide er kun tilgængelig på engelsk.

Translate a Lovable app with BeMyWords

Make a Lovable app multilingual without leaving Lovable's chat. You connect BeMyWords once, ask for languages in a sentence, and Lovable's assistant hands every string it writes to BeMyWords, which translates it.

Tested on 2026-10-03 against a real Lovable project: from one sentence, the assistant turned on French, Spanish and German, registered the app's strings, fetched the translations into the project, added a language picker, and the app rendered in German.

---

What you need

• A Lovable project.
• A BeMyWords account (the free tier is enough to try this) and a project for the app.
• A personal access token for that project: in BeMyWords, your avatar → Personal access tokens, choose the project, create. The token is shown once; copy it.

Step 1 · Add the connector in Lovable

In Lovable, open Connectors (left sidebar) and add a custom MCP connector:

Field	Value
Name	BeMyWords
URL	https://app.bemywords.org/api/<project-id>/mcp
Authentication	Bearer token
Token	the personal access token from above

Your project's Connect page in BeMyWords shows these fields with the URL already filled in, each with a copy button. Lovable's assistant cannot add a connector from the chat, so this step is yours.

Lovable keeps the connector for your other projects too, and it points at one BeMyWords project. For a second app, create a second BeMyWords project and add a connector for it, so the two apps' text stays apart.

Step 2 · Ask in the chat

Type:

Make this app multilingual with BeMyWords.

The assistant asks which languages you want. Then it turns them on in BeMyWords, registers every piece of text it has written, and wires the translations into the app. You do not paste a long prompt: the connector tells the assistant how to work with BeMyWords when it connects.

What ends up in your app

The assistant picks one of two ways to ship the translations, and you can choose for it by adding a few words to the sentence:

• Translation files ("…as translation files in src/locales"): one JSON file per language inside the project, loaded by an i18n setup and switched with a language picker. Nothing in the published app calls BeMyWords. This is what the assistant chose in the tested run.
• The Embed script ("…and use the Embed script"): one <script> tag in the app's HTML. Pages translate in the visitor's browser, with a language switcher, and text added later is picked up without another step.

When you add text later

The connector asks the assistant to register every piece of text it writes. To be sure, say so when you ask for a change: "…and register the new text with BeMyWords." BeMyWords translates registered text into every language you have turned on. With the Embed script that is the end of it. With files, ask the assistant to update the translation files once the new text is translated.

Your rules still apply

• Glossary and do-not-translate terms you set in BeMyWords are used when BeMyWords translates, and the connector tells the assistant to follow them in the text it writes.
• Review in BeMyWords. New translations arrive as AI drafts. Open the project's editor to read, correct or approve them. If the assistant edits a translation itself, the edit lands as needs review and is labelled as an assistant edit.

Search engines

A Lovable app is a single-page app: the language lives in the visitor's browser, not in the address. Visitors read your app in their language either way, but search engines see one language. If you need a page per language that Google indexes, that is not something this setup gives you.

More

• The MCP guide covers the same server for Claude Code and Cursor, read-only connections, and every tool the assistant can use.
• Revoke the token under Personal access tokens and the connector stops at once.