Yes, globalize.now works with Lovable. You install one skill, connect the globalize MCP, then ask Lovable to do the rest. Every push after that stays translated.
What you need first
- A Lovable project connected to GitHub.
- A globalize.now account. Free signup includes €5 of starting credit, no card.
- Workspace owner or admin in Lovable, needed to add a skill once for the whole workspace.
Setup
1. Connect your Lovable project to GitHub. In the Lovable editor, open the + menu in the chat, then GitHub, then Connect project. Skip if it is already connected.
2. Add the lovable-i18n skill from GitHub. In Lovable open Skills, click Add, choose Import from GitHub, and point it at:
https://github.com/globalize-now/lovable-i18n
Use the repository root, no subdirectory. You do this once per workspace; it is free and does not use credits.
3. Add the globalize MCP. In Lovable open Connectors, select +, and choose MCP server. Paste the server URL:
https://api.globalize.now/mcp
Leave authentication on OAuth, Lovable's default, and choose Add & authorize. Sign in with your globalize.now account. No API key needed. Lovable then works in the organisation you last opened in globalize.now, with your role there.
4. Ask Lovable to run it. Paste into the Lovable chat:
Use the lovable-i18n skill and the globalize MCP to set up i18n and translate my app.
Lovable installs Lingui, scaffolds a PO catalog per locale, wraps your hardcoded strings, and adds a language switcher. The MCP connects your repo and translates. Review the diff and merge.
5. Keep building. Every push opens a translation PR with updated catalogs. Merge it and your app ships translated. There is no separate dashboard step and nothing to do between releases.
Building in Cursor or Claude Code instead?
Same skills, different install. In the connected repo, run:
npx skills add globalize-now/globalize-skills --all
Then add the same MCP and ask your agent to set up i18n and translate.
Troubleshooting
- No Skills page in Lovable? You need workspace owner or admin access. Ask your workspace owner to add the skill once; it then applies to every project.
- Import from GitHub fails? Point the import at the repository root (
https://github.com/globalize-now/lovable-i18n), not a subdirectory — Lovable only reads a skill from the root. As a fallback, download the repo and upload itsSKILL.mddirectly. - Lovable asks for an API key or bearer token? You don't need one. Set authentication to OAuth instead of "Bearer token or API key", then choose Add & authorize again.