gemini_searchLABSCO SUMMARY
A second model, with its own web access, on call.
The split is by job, not by model name: search when the answer has to be current, reason when it has to be worked through, code for a repository, fileops for whatever arrives as a file. Because the file goes to Gemini directly, a large PDF or CSV never has to pass through your main model's context to be summarised.
What it is
A bridge between Google's Gemini models and MCP clients. Four tools split the work by what you are asking for rather than by which Gemini variant answers it, and the server picks the model for each call.
What you get
- gemini_search — web-connected retrieval, for questions whose answer has to be current
- gemini_reason — complex problems worked through in steps, with the steps shown
- gemini_code — full repository analysis, solution generation and debugging
- gemini_fileops — 60+ file formats including PDFs and images, several files in one call
- A model chosen per task, overridable per call or through DEFAULT_MODEL_ID
- Retries with exponential backoff and a fallback model when a call is rate-limited
Requirements
A Gemini API key as GEMINI_API_KEY, and Node. Set GEMINI_PAID_TIER when your key is on the paid tier so the higher rate limits apply. A Dockerfile is included if you would rather build and run it in a container.
Setup effort
Build from source — git clone https://github.com/PV-Bhat/GemForge-MCP.git
USE CASES
Getting an answer that has to be current
Ask through the search tool and the answer comes back grounded in live results rather than in training data.
Working through a problem that needs steps
Hand over the problem and get the reasoning shown rather than only the conclusion.
Understanding a repository you did not write
Point it at the directory and ask what it does, where a behaviour lives, or why a change breaks something.
Reading a PDF or an image without transcribing it
Send the file itself. 60+ formats are handled, so most of what lands in a ticket can be read directly.
Comparing two versions of a document
Pass both files in one call and ask for the significant changes between them.
Getting a second opinion when your main model is stuck
Run the same code question through Gemini and compare. Where two models disagree is usually where the real problem is.
4 tools
Listed in project docs. Your client may show a different list.
gemini_reasongemini_codegemini_fileopsBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
GEMINI_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
git clone https://github.com/PV-Bhat/GemForge-MCP.git
cd GemForge-MCP
npm install
npm run buildMCP Clients
Claude Desktop
{
"mcpServers": {
"GemForge": {
"command": "node",
"args": [
"<YOUR_PATH_TO_GEM_FORGE_MCP>/dist/src/index.js"
],
"env": {
"GEMINI_API_KEY": "<YOUR_GEMINI_API_KEY>"
}
}
}
}