MegaLens + GitHub Copilot
Copilot writes and reviews. MegaLens brings a second set of eyes.
What Copilot lacks today
Copilot is a strong coding assistant, but its review workflow has structural gaps that a second tool can fill.
One opaque model for review
Copilot uses a single model behind the scenes. You don't choose it, you don't know its blind spots, and you can't cross-check its findings against a different model family.
Same agent generates and reviews code
The model that wrote the code is the same one reviewing it. That's a conflict of interest. It is unlikely to flag problems in its own output with the same rigor an independent reviewer would.
Cannot "Request Changes" on PRs
Copilot can comment on pull requests, but it cannot submit formal "Request Changes" reviews. Comments are easy to skip. Structured review findings are harder to ignore.
How MegaLens will fill it
MegaLens runs as an MCP server alongside Copilot in VS Code. Same editor, different job.
MCP server alongside Copilot in VS Code
MegaLens registers as an MCP server in your VS Code workspace. Copilot handles generation. MegaLens handles independent review. No conflicts, no overlap.
Multiple specialist engines review independently
Instead of one model checking its own work, 2 to 8 models from different AI families review your code in parallel. Different training, different blind spots, broader coverage.
GPT 5.4 judges the debate
After specialists submit their findings, GPT 5.4 adjudicates disagreements, fills gaps, and filters noise. Only findings that survive scrutiny reach your editor.
Consolidated findings with line-level detail
Every finding includes the file path, line number, severity, and a concrete next step. Structured output your IDE can act on, not a wall of text.
Setup
Quickest way: run the setup wizard. It detects VS Code and writes the config for you.
npx megalens-mcp setup
Detects VS Code, asks for your token, and writes .vscode/mcp.json automatically. Or paste it yourself:
.vscode/mcp.json
{
"servers": {
"megalens": {
"type": "http",
"url": "https://megalens.ai/api/mcp",
"headers": {
"Authorization": "Bearer ml_tok_your_token_here"
}
}
}
}Get your token at megalens.ai/app/settings/mcp. Source: github.com/megalens/mcp.
Cost preview
MegaLens adds multi-engine review without doubling your bill.
Starter Stack
Full Stack
Honest limitations
We'd rather you know this upfront than find out after setup.
Advisory only, no model switch
MegaLens surfaces findings and recommendations. It does not override Copilot's model selection or intercept its completions. You decide what to act on.
Reviews surface as suggestions in chat, not inline diff comments
Copilot's MCP integration exposes tools through the chat panel. Review findings will appear there as structured suggestions, not as inline annotations in the editor diff view.
Copilot MCP is tools-only
GitHub's current MCP implementation supports tools but not resources or prompts. This means MegaLens can respond to review requests but cannot proactively inject context into Copilot's workflow.
Multi-engine review alongside Copilot.
One config file. Multiple AI perspectives. Copilot generates, MegaLens reviews.