Code Assistant
Wire Gemini-backed code analysis into Claude Code or Cursor so the agent can inspect and explain your repo without leaving the chat.
Overview
Code Assistant is a MCP server for the Build phase that gives coding agents Gemini-backed tools to analyze project code over stdio.
What is this MCP server?
- Gemini-powered analysis exposed as MCP tools over stdio transport
- Published on npm as @j0hanz/code-assistant (registry version 2.0.0)
- stdio MCP package for local agent hosts (Claude Desktop, Claude Code, Cursor)
- Focused on code analysis workflows tied to repository context
- Open-source server schema aligned with MCP 2025-12-11 server metadata
- Server version 2.0.0 in MCP registry metadata
- Single npm package @j0hanz/code-assistant with stdio transport
- Transport type stdio (local process, not remote HTTP in schema)
What problem does it solve?
Pasting files into chat burns context and produces shallow answers when you need consistent, tool-driven code analysis inside the agent.
Who is it for?
Solo builders using Claude Code or Cursor who want a local Gemini MCP bridge for repository-aware code analysis during implementation.
Skip if: Teams that need enterprise code review policies, CI gates, or analysis without configuring a Gemini API key and Node/npm MCP host.
What do I get? / Deliverables
After you register the stdio server in your agent, analysis requests run through dedicated MCP tools backed by Gemini instead of ad-hoc copy-paste.
- Registered stdio MCP server entry in your agent configuration
- Callable Gemini-backed code analysis tools from the agent session
- Local workflow for structured repo analysis without manual file dumps
Recommended MCP Servers
Journey fit
Canonical shelf is Build because the server is invoked while you are actively coding and need grounded analysis of local files. Agent-tooling fits an MCP stdio bridge that extends the coding agent’s toolkit rather than shipping a standalone app feature.
How it compares
MCP integration for code analysis, not a standalone IDE extension or a Ship-phase review checklist skill.
Common Questions / FAQ
Who is Code Assistant for?
It is for indie and solo developers who run AI coding agents locally and want Gemini-driven code analysis available as MCP tools.
When should I use Code Assistant?
Use it during Build when you are exploring, refactoring, or debugging code and want the agent to call analysis tools on your repo context.
How do I add Code Assistant to my agent?
Install @j0hanz/code-assistant from npm, configure stdio in your MCP client, set Gemini credentials per the GitHub README, and restart the agent host.