Your IDE already has one AI. MegaLens makes it sharper.
MegaLens MCP plugs into Claude Code, Codex, Cursor, and other MCP editors to add planning, research, code intelligence, security audit, architecture review, blind spot detection, gap-finding, and final closure review without replacing your existing workflow.
MegaLens is the specialist layer. Your IDE stays the final judge.
Can save you thousands in review costs
MegaLens can catch code, security, and architecture issues early, before they turn into expensive fixes or outside audit bills.
Cuts wasted output and token spend
MegaLens trims bulky MCP output so your IDE gets the useful findings without paying for extra noise.
Try it with just $0.50
Verify your card for $0.50 and get $5.50 total credit, enough to properly test planning, audits, and MCP workflows.
How it works
Three steps to sharper IDE workflows.
Connect MegaLens to your IDE
Add one MCP config block. Claude Code, Codex, Cursor, and similar MCP clients can connect in seconds.
Send targeted specialist work
Use MegaLens for planning, audits, architecture review, research, blind spot detection, and gap-finding instead of stuffing all of that into your main IDE thread.
Your IDE makes the final call
MegaLens returns tighter specialist findings. Your IDE decides what to accept, change, reject, or act on next.
Workflow fit
MegaLens complements your IDE.
The point is not another heavy interface. The point is to move specialist work into a separate MCP layer so your IDE has less context pressure and fewer wasted cycles.
Claude Code
Already in flow
Claude is already in the driver seat
MegaLens adds
Specialist work from outside the main model family
Result
MegaLens adds planning, audit, and blind spot checks while Claude Code stays the final judge.
Codex (OpenAI)
Already in flow
Codex is already driving the session
MegaLens adds
Targeted specialist review without replacing Codex
Result
MegaLens handles parallel specialist work so Codex can keep more reasoning room for final action and closure.
Cursor / Other MCP
Already in flow
Your editor already has a primary assistant
MegaLens adds
A specialist layer for planning, audit, research, and gap-finding
Result
MegaLens complements your primary assistant instead of becoming another IDE. Your editor remains the final decision-maker.
Setup
Two lanes, one setup
Local MCP for users who bring their own API keys (Free or Pro) and want the most reliable IDE workflow. Hosted HTTP for Managed Credits users who want the quickest setup without provider keys.
Local MCP
Your own keys · Free or Pro
Your key, your machine
Hosted HTTP
Managed Credits
Managed billing, no key
Pick your lane
Your own keys (Free or Pro). Bring your own OpenRouter key, run local MCP on your machine. Best for daily reliability and deeper IDE workflows. Pro unlocks full multi-AI depth.
Managed Credits. Prepay from $20, no provider key required, connect via hosted HTTP. Billed at $9 per 1M blended tokens.
Local MCP
Runs on your machine via stdio transport with your own OpenRouter key. No dependency on hosted round-trip latency or client timeout behavior.
Add to ~/.claude.json or your project's .mcp.json:
{
"mcpServers": {
"megalens": {
"type": "stdio",
"command": "npx",
"args": ["-y", "megalens-mcp@latest"],
"env": {
"MEGALENS_OPENROUTER_KEY": "sk-or-v1-your-key"
}
}
}
}Add to your project's codex.json or workspace config:
{
"mcp": {
"servers": {
"megalens": {
"type": "stdio",
"command": "npx",
"args": ["-y", "megalens-mcp@latest"],
"env": {
"MEGALENS_OPENROUTER_KEY": "sk-or-v1-your-key"
}
}
}
}
}Hosted HTTP MCP
Managed CreditsQuickest setup, managed billing via prepaid MegaLens credits. Connect to the hosted endpoint with your token and start immediately. Billed at $9 per 1M blended tokens.
Grab your MegaLens token from Settings → MCP setup:
Or use the CLI helper to auto-detect your editor and write the hosted config:
npm install -g megalens-mcp megalens-mcp setup
Add to ~/.claude.json or your project's .mcp.json:
{
"mcpServers": {
"megalens": {
"url": "https://megalens.ai/api/mcp",
"headers": {
"Authorization": "Bearer ml_tok_your_token_here"
}
}
}
}Add to your project's codex.json or workspace config:
{
"mcp": {
"servers": {
"megalens": {
"url": "https://megalens.ai/api/mcp",
"headers": {
"Authorization": "Bearer ml_tok_your_token_here"
}
}
}
}
}Start asking for targeted work
MegaLens tools appear in your IDE automatically. Ask for specific specialist work:
Core scopes
Fast to scan. Clear in seconds.
Planning, research, code intelligence, security audit, architecture review, blind spot detection, gap-finding, and closure review.
Planning
Use MegaLens for serious planning passes before commits, migrations, infra changes, or product decisions.
Research
Targeted research can happen in a separate MCP layer instead of bloating your IDE thread.
Code intelligence
Repo-aware specialist review sees real files, imports, dependencies, and structure instead of a pasted summary.
Security audit
Useful for catching issues earlier, when they are cheaper to fix than after release or after a late-stage audit.
Architecture review
Good for tradeoff checking, blind spot coverage, and gap-finding when one model feels too certain too early.
Final closure review
Use MegaLens at the end to check what still feels unresolved before your IDE makes the final call.
Sharper workflow. Less waste.
A few dollars for meaningful planning or audit work is negligible next to shipping mistakes. External audits can cost $2,000+.