MegaLens gives Claude Code a second opinion before you ship.
Other AI models review your code. You call them from your terminal over MCP. Setup is one config line, and you do not need to switch tabs.
How it works
Opus writes code. You invoke megalens_debate with a skill tag.
MegaLens selects up to four AI models from different companies to review your code. They review it independently.
A final check reviews their findings.
It returns structured findings that point to the file and line when you send the code. Each result names the models that actually took part.
Claude Code receives the verdict.
It decides what to apply, reject, or investigate. Your IDE keeps the final say.
Setup
The quickest way is the setup wizard. It detects Claude Code and writes the config for you.
npx megalens-mcp setup
Detects Claude Code, asks for your token, and writes the config below automatically. Or paste it yourself:
Run this once. The --scope user flag makes MegaLens available in every project:
claude mcp add --transport http --scope user megalens \ "https://megalens.ai/api/mcp?ide=claude-code" \ --header "Authorization: Bearer ml_tok_your_token_here"
Or edit ~/.claude.json yourself:
{
"mcpServers": {
"megalens": {
"type": "http",
"url": "https://megalens.ai/api/mcp?ide=claude-code",
"headers": {
"Authorization": "Bearer ml_tok_your_token_here"
}
}
}
}Get your token at megalens.ai/app/settings/mcp. Restart Claude Code, then run megalens_status to confirm. Setup wizard source: github.com/megalens/mcp.
Using Claude.ai in the browser instead of Claude Code? Add MegaLens there as a custom connector. There is no token to copy: see the steps.
What MegaLens can catch in code from Claude Code
Security assumptions
Auth logic, token handling and CORS rules are where one model can be too trusting. A model from a different company can spot what the first one assumed was safe.
Framework-specific anti-patterns
Next.js, Rails, Django, Laravel. Each framework has conventions that a generalist model may not flag.
Contradictions across files
A type defined one way in the schema and used differently in the handler. If you send both files, the reviewers can catch a mismatch between them.
Overconfident rewrites
A model reviewing its own rewrite is not an independent check. A review from a different model family can catch regressions the author missed.
Honest limitations
Advisory only. MegaLens does not merge, push, or run tests.
Review quality depends on how specific your request is. Name a skill when you can.
A review takes a few minutes. It is not for autocomplete.
Pricing
Free
$0
Your first review is free, with no card. MegaLens selects two reviewing models for it. After that, pay as you go: $9 per 1M blended tokens, never more than $3 for one review.
Plus and Pro
From $19 a month
A monthly allowance of reviews with model usage included: up to 100 reviews on Plus, 300 on Pro. MegaLens selects up to four reviewing models. Cancel any time.
How model costs are paid
On a plan, model usage is part of your monthly allowance. Otherwise, pay-as-you-go credits: $9 per 1M blended tokens, capped at $3 per review, prepaid from $20. See all plans
Get a second opinion on your code.
Run your first MegaLens review inside Claude Code. It is free and needs no card.