Code Lens
Add a Gemini MCP layer so your agent can lens into code structure and behavior while you integrate features across the stack.
Overview
Code Lens is a MCP server for the Build phase that connects coding agents to Gemini-powered code analysis over a stdio MCP package.
What is this MCP server?
- Gemini-powered code analysis via MCP over stdio
- npm package @j0hanz/code-lens-mcp at registry version 0.9.5
- Designed as a focused code-lens style analysis bridge for agents
- GitHub-hosted j0hanz/code-lens with MCP 2025-12-11 server schema
- Complements other j0hanz analysis servers with a lens-oriented analysis angle
- Registry package version 0.9.5
- One npm identifier @j0hanz/code-lens-mcp
- stdio transport type in server.schema.json metadata
What problem does it solve?
Agents lose precision when you ask for structural code insight without a dedicated analysis integration wired to your workspace.
Who is it for?
Developers who already use MCP in Build and want a npm stdio server specialized for code-lens style analysis with Gemini.
Skip if: Builders who only need one-off chat explanations, or who cannot run Node/npm MCP servers or supply Gemini credentials.
What do I get? / Deliverables
Once configured, your agent can invoke Code Lens MCP tools for Gemini-backed analysis while you build and wire integrations.
- Working stdio MCP connection to Code Lens from your agent
- Gemini-mediated analysis calls during build and integration tasks
- Documented local MCP config snippet for team reuse
Recommended MCP Servers
Journey fit
Build is the canonical phase because Code Lens supports hands-on implementation and integration work rather than launch or ops monitoring. Integrations reflects an MCP server that plugs external model capability into your existing editor and repo workflow.
How it compares
Sibling-style Gemini analysis MCP (lens-oriented), not the Ship-phase Code Review Analyst server.
Common Questions / FAQ
Who is Code Lens for?
It is for solo builders and small teams who use AI agents daily and want Gemini analysis exposed as MCP tools during development.
When should I use Code Lens?
Use it while integrating features or exploring unfamiliar code paths when you need repeatable, tool-based analysis from the agent.
How do I add Code Lens to my agent?
Add @j0hanz/code-lens-mcp via npm, configure the stdio command in your MCP settings, provide Gemini API configuration, and reload the agent.