Labsco
MCP SERVER

Deep Code Reasoning MCP Server

by haasonsaas

Hand a stuck investigation to Gemini's 1M-token context and get the analysis back where Claude can act on it.

Model Routing, Multi-Model Consultation & Cost Control
Summary
Routing between models, not replacing one with another.

The premise is that these are heterogeneous services rather than competitors: one is good at tight terminal loops and multi-file edits, the other at a single enormous sweep over logs, traces and code at once. The tools are shaped around that handoff — you tell it what you already tried and where you got stuck, which is the context a fresh model normally lacks.

What it is

An escalation route between two models. Claude Code keeps the local, incremental work; when a problem outgrows that — gigabytes of traces, failures spanning ten services, twenty hypotheses to test — this server packages the context and hands it to Gemini 2.5 Pro, then returns the result for implementation.

What you get
  • `escalate_analysis` — the main handoff: what was attempted, what was found, where it stuck, and the files in scope, with an analysis type of `execution_trace`, `cross_system`, `performance` or `hypothesis_test`, a depth level from 1 to 5 and an optional time budget
  • `start_conversation`, `continue_conversation`, `finalize_conversation`, `get_conversation_status` — a multi-turn dialogue between the two models, closing with a summary formatted `detailed`, `concise` or `actionable`
  • `trace_execution_path` — follow execution from a file and line with data flow included, to a configurable depth
  • `cross_system_impact` — model breaking, performance and behavioural effects of a change across service boundaries
  • `performance_bottleneck` — N+1 query patterns, memory leaks and algorithmic hot spots, at a profile depth you choose
  • `hypothesis_test` — state a theory about the code and a way to test it, and get evidence-based validation back
Requirements

Node.js 18 or later and a Gemini API key from Google AI Studio in `GEMINI_API_KEY`. Cloned and built with `npm install` and `npm run build`, then launched as `node dist/index.js`. Two practical rules the troubleshooting section spells out: file paths passed to tools must be absolute, and every parameter name is snake_case (`claude_context`, not `claudeContext`). Your code is sent to Google's Gemini API, so read their data policies before pointing it at a private repository.