MCP setupIncluded on every plan

Your IDE already has one AI. MegaLens adds a second opinion.

MegaLens adds planning, research, code review, security audit and diff review to your IDE, without replacing your existing workflow. Works with Claude Code, Codex CLI, Cursor, Gemini CLI and Lovable, and with any tool that supports OAuth MCP connectors, such as ChatGPT and Claude.ai. GitHub Copilot is coming soon.

MegaLens reviews. Your IDE decides what to change.

Catch issues before you ship

MegaLens can catch code and security issues before you ship.

Models from different companies

MegaLens selects up to four AI models from different companies to review your code. Each result names the models that actually took part.

Your first review is free

No card and no API key for the first one. After that, verify a card for $0.50 and get $5.50 total credit, enough to test planning, audits, and MCP workflows.

How it works

Three steps to use MegaLens in your IDE workflows.

01

Connect MegaLens to your IDE

Add one MCP config block. Claude Code, Codex, Cursor, and similar MCP clients can connect in seconds.

02

Send targeted work

Use MegaLens for planning, research, code review and security audits.

03

Your IDE makes the final call

MegaLens returns tighter findings. Your IDE decides what to accept, change, reject, or act on next.

Workflow fit

MegaLens complements your IDE.

MegaLens runs the review on separate models, away from your IDE's own model.

◈

Claude Code

Already in flow

Claude is already in the driver seat

MegaLens adds

Review from outside the main model family

Result

MegaLens adds planning and audits. Claude Code decides what to change.

G

Codex (OpenAI)

Already in flow

Codex is already driving the session

MegaLens adds

Targeted review without replacing Codex

Result

MegaLens runs the review in parallel. Codex decides what to do with it.

C

Cursor, Gemini CLI, Lovable

Already in flow

Your editor already has a primary assistant

MegaLens adds

Planning, audit and research.

Result

MegaLens complements your primary assistant instead of becoming another IDE. Your editor remains the final decision-maker.

Setup

One setup, for every plan

Every plan connects to the hosted endpoint with one token.

Using ChatGPT, Claude.ai or another tool with OAuth connectors? You need no token or config block: paste https://megalens.ai/api/mcp as a connector, then sign in and approve. See the steps.

1

Get your token

Connect to the hosted endpoint with your token. Your first review is free. After that, pick a plan with reviews included, or use credits ($9 per 1M blended tokens, capped at $3 per review).

Copy your MegaLens token from Settings → MCP setup:

ml_tok_••••••••••••••••
2

Add MegaLens to your IDE

The CLI helper detects your editor and writes the hosted config:

npm install -g megalens-mcp
megalens-mcp setup

Or add it yourself:

Claude Code

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"
      }
    }
  }
}
Codex CLI

Add to ~/.codex/config.toml. It is TOML, not JSON:

[mcp_servers.megalens]
url = "https://megalens.ai/api/mcp?ide=codex"
http_headers = { "Authorization" = "Bearer ml_tok_your_token_here" }

Cursor, Gemini CLI and Lovable each use a different format. Copy the exact block from Cursor, Gemini CLI or Lovable. GitHub Copilot is coming soon.

3

Choose how reviews are paid

a.

A plan. Plus and Pro include a monthly allowance of reviews, with model usage included, from $19 a month. See plans.

b.

Managed Credits. Prepay from $20. Billed at $9 per 1M blended tokens, capped at $3 per review.

Nothing to add to the config for either. On Free, MegaLens selects two reviewing models. On a plan, MegaLens selects up to four reviewing models.

4

Start asking for targeted work

MegaLens tools appear after you restart your IDE. Ask for specific work:

> Use megalens to audit the auth middleware for security issues
> Use megalens to review this diff before I merge

Core scopes

Five scopes in one tool.

Planning, research, code intelligence, security audit and diff audit.

Planning

Use MegaLens for serious planning passes before commits, migrations, infra changes, or product decisions.

Research

Ask MegaLens to research a question with models from different companies.

Code review

Code review works on the actual files your IDE sends, so ask it to send the code, not a summary. You can also ask it for architecture and tradeoff checks.

Security audit

Useful for catching security issues before release.

Diff audit

Run a last review of your diff before you merge.

A second opinion before you ship.

Your IDE reads the findings and decides what to fix.