gemini-file-search-rag-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP server (default: 3000, only used with --http) | 3000 |
| GEMINI_API_KEY | Yes | Google Gemini API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gemini_create_storeA | Create a new Gemini File Search store for RAG documents. Returns the created store resource. Use this to create a knowledge base before uploading documents. |
| gemini_list_storesA | List all Gemini File Search stores. Returns store names, display names, and timestamps. Use to see available knowledge bases. |
| gemini_get_storeB | Get details of a specific Gemini File Search store by its resource name. |
| gemini_delete_storeA | Delete a Gemini File Search store. Use force=true to also delete all documents inside it. |
| gemini_upload_to_storeA | Upload content directly to a Gemini File Search store. Accepts text content or base64-encoded binary. For large files, use gemini_import_file_to_store instead. Returns an operation to track upload progress. |
| gemini_import_file_to_storeA | Import a file from the Gemini Files API into a File Search store. Use this for large files that were uploaded separately via the Files API. Returns an operation to track import progress. |
| gemini_get_operationA | Check the status of a store operation (create, delete, import). Returns whether the operation is done and any error details. |
| gemini_get_upload_operationA | Check the status of a file upload operation. Returns whether the upload is done and any error details. |
| gemini_list_documentsA | List documents in a Gemini File Search store. Returns document names, display names, state, size, and MIME types. |
| gemini_get_documentB | Get details of a specific document in a File Search store, including state, size, and metadata. |
| gemini_delete_documentA | Delete a document from a File Search store. Use force=true to also delete associated chunks. |
| gemini_rag_queryA | Query your documents using Gemini RAG. Sends a natural language query grounded in your File Search stores. Returns AI-generated answer with source citations from your documents. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| setup-rag | Guide for setting up RAG — create stores, upload documents, and index content |
| query-rag | Guide for querying your indexed documents using Gemini RAG |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Gemini RAG Server Info | Connection status and available tools for this Gemini RAG MCP server |
TDQS
Scored across 12 tools
Most tools target a distinct resource+action (store CRUD, document CRUD, query), but two pairs risk confusion: gemini_get_operation vs gemini_get_upload_operation both poll operation status, and gemini_upload_to_store vs gemini_import_file_to_store both ingest content. The descriptions do clarify the distinctions (store vs upload operations; direct content vs Files API), keeping it mostly clean.
Every tool follows the same gemini_<verb>_<noun> convention (gemini_list_stores, gemini_get_store, gemini_delete_document, gemini_rag_query). The pattern is predictable and uniform across all 12 tools.
12 tools is well-scoped for a RAG/file-search server, covering store lifecycle, document lifecycle, ingestion, operation polling, and query. Each tool earns its place without redundancy.
Store lifecycle (create/get/list/delete) and document read/delete plus ingestion and query are well covered. Minor gaps exist: no store/document update or rename operation, and document creation is only via upload/import, but core workflows are complete.