Integration: Lovable
Build with Lovable, keep the data in Europe
Lovable normally stores your app's data in Lovable Cloud or in Supabase. Both work well. But Lovable Cloud runs on Supabase, Supabase is a US company on AWS, and for a lot of European projects that is a problem.
You can use Eurobase as the backend instead. The setup is six steps and takes about 6-7 minutes. I recorded all of it:
Nothing is loaded from YouTube until you press play. When you do, the video comes from YouTube (Google) and they can see that you watched it.
Open the video on YouTube if you prefer that.
The six steps
You need a Eurobase project first. Sign up (free, no credit card), create a project and open Connect → Lovable. That page has all the values below filled in for your project, so keep it open in a second tab.
- 1
Tell Lovable not to create its own backend
In Lovable open Connectors → Cloud → Manage my agent's permissions and set "Enable Cloud" to "Ask each time". If it asks later, say no. If you skip this, the first time you ask for a login screen your users land in Lovable Cloud.
- 2
Copy the three .env lines
Connect → Lovable shows VITE_EUROBASE_URL, VITE_EUROBASE_PROJECT_ID and VITE_EUROBASE_PUBLIC_KEY for your project. Copy them into the Lovable project. The public key starts with eb_pk_ and it is the only key that goes in there.
- 3
Add the Eurobase skill
Lovable knows supabase-js very well and our SDK not at all, so it needs a short manual. Copy SKILL.md from the Connect page into Project settings → Knowledge. Workspace owners and admins can add it as a workspace skill instead, then all projects have it.
- 4
Connect the MCP server
Connectors → + → MCP server. The server URL is https://mcp.eurobase.app/mcp and the authentication is "Bearer token". The Connect page creates the token for you. It only works for this one project, with Developer access, so Lovable can read and create tables there and nothing else.
- 5
Allow your app's URLs
Paste your Lovable editor URL and your published URL into the Connect page and press "Add to allowed URLs". A Lovable app lives on four or five different addresses and the console adds all of them, so you don't have to hunt for them.
- 6
Send the first prompt
The Connect page has a first prompt ready to copy. It tells Lovable to use the skill and to use Eurobase instead of Lovable Cloud. Add what you want to build and go.
After that you work in Lovable like before. Login, database, file uploads, realtime and functions run on Eurobase, on Scaleway servers in France. The blog post goes through the same steps with a bit more background.
Things people ask
- Do I have to be a workspace admin in Lovable?
- No. Admin rights are only neccessary if you want the skill in every project of the workspace. For one project you paste SKILL.md into the project Knowledge and that is enough.
- Why can't I just allow *.lovable.app?
- Because anybody can publish an app on lovable.app. A wildcard would let every one of those apps talk to your backend, so we don't accept it. You need the exact addresses, and the Connect page works them out for you.
- I need to change the token.
- Lovable can't edit an MCP connection after it is created. Delete the connector and add it again with the new token.
- I renamed or unpublished my Lovable app.
- Then please remove the old addresses under Auth in the Eurobase console. Somebody else could take the old name later, and you definately don't want that address still on your allow list.
- Where do secret keys go?
- Not into Lovable. Keys that start with eb_sk_ belong in an edge function. The same goes for API keys of other services, like a payment provider.
Try it with your next project
The free tier is enough to build and test a Lovable app. It is for non-commercial use, so once the app earns money you need Pro, which is €25 a month. Every project also gets the GDPR tools: the one-click data export, the Article 30 report and the audit log. If something in the setup doesn't work, write to hello@eurobase.app and we will help.
Sign up free