Lovable builds it. MegaLens checks it.
Ask Lovable to send its code to MegaLens, and several AI engines read it and report what they find. Your first review is free and you do not need a card.
What this does, and what it does not
MegaLens reviews what Lovable sends it. When you ask for a review, Lovable picks the files and passes them across. Several engines read that code, argue about it, and the disagreements come back as findings.
MegaLens cannot open your project. It has no access to your files, your repository or your database. It only ever sees the code Lovable chooses to send in that one message. If Lovable sends nothing, there is nothing to review — which is why the prompt below asks for the file contents on purpose.
It does not change your code. MegaLens reports. Any fixing is still Lovable's job, and yours.
Connect it. Three steps.
1. Get your token
Sign in and open your setup page. Tick Other and continue. Under that section you will see a box headed Using a web builder like Lovable? Press Copy token only.
That button copies the token on its own, which is what Lovable's form wants. Do not type the word Bearer in front of it here — Lovable adds that itself. The token is shown once, when it is made, so keep it somewhere safe.
2. Add MegaLens in Lovable
In your Lovable project, open the MCP connector settings and add a custom server. Paste this as the server URL:
https://megalens.ai/api/mcp?ide=lovable
Choose the Bearer token authentication option, and paste your token into the token field. Save it.
Keep the whole URL exactly as it is, including the ?ide=lovable on the end. That part only tells us the review came from Lovable. It does not change the review.
3. Ask for a review
Type this to Lovable in the normal chat box:
“Use the megalens_debate tool to review this project's authentication code. Send the actual file contents.”
The last sentence matters. It tells Lovable to send the code itself rather than a list of file names, and a list of names gives the engines nothing to read.
Swap “authentication code” for whatever you want looked at. A review takes a few minutes, because several engines read the code and then a final one checks their work.
Your first review is free
It works on this surface, with no card. The free review runs two engines rather than the full panel, which is enough to see what the findings look like on your own code.
After that you can either pay as you go, or connect your own model key and pay the provider directly instead of us. Both options live on your billing page.
If something does not work
Lovable says it is not authorised
The token is usually the cause. Copy it again with Copy token only and paste it on its own, with no spaces before or after.
The review comes back with nothing much in it
Lovable probably sent file names instead of the code. Ask again and include the sentence “Send the actual file contents.”
It is still not working
Email [email protected] and say what you typed and what came back. A broken review is more useful to us right now than a working one.