22. Connecting Your IDE & Lovable
Alex wants their AI coding assistant — and Lovable — to understand the LexVault schema.
The Connect page generates ready-to-use configuration for popular AI coding tools and app builders. It gives your AI assistant context about your project's schema, API endpoints and connection details, and connects it to the Eurobase MCP server.
Supported tools
One tab per tool
Claude Code — a CLAUDE.md with your schema and API reference, plus the MCP server command
Lovable — a step-by-step setup with the Eurobase skill, the MCP connector and your app's allowed URLs (see below)
Codex — an AGENTS.md, plus the MCP server entry for ~/.codex/config.toml
Cursor — a .cursorrules file, plus the MCP server entry for .cursor/mcp.json
Windsurf — a .windsurfrules file, plus the MCP server entry
Generic — SDK install, a .env template, the MCP server URL and cURL examples
Each tab shows a preview of the generated files with copy and download buttons. For the IDE tabs, drop the file into your project root and your AI assistant has full context about your Eurobase project. Every tab except Generic has a button that creates a project token for that tool and, in the IDE tabs, fills it into the config; in Lovable you paste it into the connector yourself.
Building a Lovable app on Eurobase
Alex's colleague prototypes the LexVault client portal in Lovable. By default Lovable puts the backend on Lovable Cloud (Supabase); with the Eurobase integration the app talks to Eurobase directly from the browser with @eurobase/sdk, so the data stays in the EU. Open Connect → Lovable and follow the six steps — the values are already filled in for your project:
1. Stop Lovable from creating its own backend
In Lovable: Connectors → Cloud → Manage my agent's permissions → set Enable Cloud to Ask each time, and decline if it asks. Otherwise the first "add a login" prompt puts your users on Lovable Cloud.
2. Environment
Copy the .env lines into the Lovable project:
VITE_EUROBASE_URL=https://lexvault.eurobase.app VITE_EUROBASE_PROJECT_ID=<project id> VITE_EUROBASE_PUBLIC_KEY=eb_pk_...
3. Add the Eurobase skill
The skill teaches Lovable the Eurobase SDK (it's not supabase-js), row-level security, file privacy and where secrets belong. Copy SKILL.md into Project settings → Knowledge, or add it to your workspace's skills (workspace owner or admin) so every project can use it. sdk-reference.md is the full SDK reference that goes with it.
4. Connect the Eurobase MCP server
In Lovable: Connectors → + → MCP server, server URL https://mcp.eurobase.app/mcp, authentication Bearer token. Use a project token with Developer access, so Lovable can see and create tables in this project and nothing else. Lovable can't edit a connection — to change the token, delete the connector and add it again.
5. Allow your app's URLs
Paste the Lovable editor URL (lovable.dev/projects/…), the published URL and any custom domain, then click Add to allowed URLs. The console adds every origin — both preview addresses (<id>.lovableproject.com and id-preview--<id>.lovable.app), the published app and its preview-- address, and your custom domain — to Allowed CORS origins, and each origin plus its sign-in pages (/verify, /reset-password, /magic, /auth/callback) to Allowed redirect URLs. Wildcards like *.lovable.app aren't accepted, since anyone can publish there. Needs the admin role.
6. Start building
Copy the first prompt, which tells Lovable to use the skill and Eurobase instead of Lovable Cloud, add your public key if it isn't filled in, and add what to build.
Remove old entries in Auth after renaming or unpublishing a Lovable app — someone else could later take the old address.
The generated configs include your API URL and public key but never your secret key. Never paste a secret key (eb_sk_…) into Lovable or any other app builder — anything that needs it belongs in an edge function. For local projects, add secret keys to your .env file manually and make sure it's in your .gitignore.