Gemini API DocsSAFE
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
A remote HTTP MCP server that provides tools to search and retrieve Google Gemini API documentation. The server exposes the MCP protocol at the /mcp endpoint and can be deployed to Cloud Run or other containerized platforms. It also supports local stdio mode for development.
- Search Documentation: Full-text search across all Gemini documentation pages.
- Get Capabilities: List available documentation pages or retrieve content for a specific page.
- Get Current Model: Quickly access documentation for current Gemini models.
- Automatic Updates: Scrapes and updates documentation on server startup.
sequenceDiagram
participant Client as MCP Client / IDE
participant Server as FastMCP Server
participant DB as SQLite Database
Client->>Server: call_tool("search_documentation", queries=["embeddings"])
Server->>DB: Full-Text Search for "embeddings"
DB-->>Server: Return matching documentation
Server-->>Client: Return formatted resultsHow it Works
- Ingestion: On startup, the server fetches
https://ai.google.dev/gemini-api/docs/llms.txtto get a list of all available documentation pages. - Processing: It then concurrently fetches and processes each page, extracting the text content.
- Indexing: The processed content is stored in a local SQLite database with a Full-Text Search (FTS5) index for efficient querying.
- Searching: When you use the
search_documentationtool, the server queries this SQLite database to find the most relevant documentation pages.
Installation
Option 1: Use uvx (Recommended)
You can use uvx to run the server directly without explicit installation. This is the easiest way to get started.
b240e12d5e22OBSERVED · 2026-10-07Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add gemini-docs-mcp -- uvx gemini-docs-mcp
{
"mcpServers": {
"gemini-docs-mcp": {
"command": "uvx",
"args": [
"gemini-docs-mcp"
]
}
}
}Exposed tools (1)
1 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
get_capability_page | read |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- declared (5 observation(s))
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (1)
streamable-http
Gates applied: no_behavioural_pass.
b240e12d5e22full audit observations/trust-audit/mcp-server/philschmid__gemini-api-docs.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-07 | b240e12d5e22 | SAFE | B | 89 | first audit |
Questions
What tools does Gemini API Docs expose?
1 in total: 1 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Gemini API Docs safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Gemini API Docs need?
No credential environment variables were found in its source, so it appears to need none.
How does Gemini API Docs run?
It speaks streamable-http, so it runs as a service you connect to over the network. It is published on PyPI as gemini-docs-mcp.
How current is this page?
The grade is for one exact copy of the source (b240e12d5e22), read on 2026-10-07. The repository is watched and re-audited when it changes.