Back to reviews
Gemini API Docs MCP

Gemini API Docs MCP

Give your coding agent live Gemini API docs so it stops hallucinating old code

Google launched the Gemini API Docs MCP on April 1, 2026 — a public Model Context Protocol server at gemini-api-docs-mcp.dev that connects coding agents to live Gemini API documentation, SDK references, and model information. Agents using it alongside Gemini API Developer Skills achieve a 96.3% pass rate on Google's eval set with 63% fewer tokens per correct answer versus vanilla prompting. The server adds a search_documentation function that retrieves real-time API definitions and integration patterns. Solves the core problem of agents trained at a knowledge cutoff generating outdated API calls.

Panel Reviews

Ship

Any project using the Gemini API gets immediate value from this — the models keep generating code against deprecated endpoints and wrong model names. Plugging in the MCP server and Skills package took 10 minutes and my Cursor agent stopped suggesting gemini-pro when it should be gemini-2.0-flash. The 63% token reduction on correct answers is real money saved per month for high-volume usage.

Skip

Google designed, ran, and scored their own 96.3% eval — no independent validation. The MCP server only helps if you're building on the Gemini API specifically; useless for anyone on Claude, OpenAI, or Mistral. This is Google solving a problem their own API versioning policy created, and framing it as a developer win. Useful if you're already in the Google ecosystem, irrelevant if you're not.

Skip

First-party MCP servers from major AI providers are the new developer relations strategy. Google shipping gemini-api-docs-mcp.dev means every future API change can be instantly reflected in what coding agents generate — no retraining lag. This is the prototype for how all API providers will maintain accuracy in AI-generated code within 18 months.

Ship

The number of times I've had to tell an agent 'that model name doesn't exist anymore' is embarrassing. Pointing my agent at a live docs MCP server that Google keeps current is the obvious fix I didn't know existed. Setup is three lines of config in Cursor. Shipping-quality Gemini API calls on the first try now instead of the third.

Community Sentiment

OverallNaN mentions
NaN% positiveNaN% neutralNaN% negative
HN mentions

The 63% token reduction matters more than the accuracy bump for anyone paying API bills

Reddit mentions

First-party MCP from Google is the right move — agents hallucinating old API signatures is a real pain

Twitter/X mentions

96.3% pass rate is a lot of nines for an eval Google designed themselves