Provides read-only retrieval over Google Docs, allowing agents to access and search document content.
Provides read-only retrieval over Google Drive, allowing agents to discover and search files within a Google Drive account.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Google Drive Agentic Retrieval MCP search Google Drive for the Q3 budget spreadsheet"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Read-only agentic retrieval over Google Drive and Google Docs/Sheets/Slides, served by a stateless MCP on Cloud Run, for any MCP-compatible reasoning agent.
This repository is developed with Spec-Kit
spec-driven development. Governing principles live in
.specify/memory/constitution.md and bind
every subsequent spec, plan, task list, and implementation.
Google Drive is the sole source of truth. The MCP is a secure, deterministic, ephemeral evidence-acquisition layer. The calling agent owns reasoning and the retrieval loop. v1 is read-only, single Google identity per deployment, and does not require an application-owned RAG index.
See the constitution for the full invariant set (Articles I–XV).
Related MCP server: mcp-server-drive
Cursor skills are installed under .cursor/skills/. Use them in this order:
/speckit-constitution — project principles (done: v1.0.0)
/speckit-specify — what to build (done: access control + retrieval core)
/speckit-clarify — optional; de-risk underspecified areas (done: session 2026-09-08)
/speckit-plan — how to build it (done: access control + retrieval core)
/speckit-tasks — actionable implementation tasks (done: both features)
/speckit-analyze — optional; cross-artifact consistency (done: 2026-09-08; remediations and plan sync applied)
/speckit-implement — execute the tasks
/speckit-converge — compare the codebase to spec/plan/tasks and append remaining work
Feature specs (ready for implementation):
Access Control Boundary — who may act, and on what authority
Retrieval Core — discover, read, exact-search once a call is cleared
Repeat implement and converge until converge reports Converged.
The Specify CLI (specify-cli 1.0.4) initialized this project with the
cursor-agent integration and bash scripts. Refresh managed files with
specify integration upgrade after upgrading the CLI.
Shared pickup state for the next Cloud Agent:
.specify/memory/project-status.md — current SDD phase
.cursor/rules/spec-kit-sdd.mdc — always-on constitution and next-step rules
.cursor/environment.json — installs uv and specify-cli on Cloud Agent boot
Multi-tenant access, write capability, persistent caches, and semantic/vector retrieval are MAJOR constitutional changes (Article XIV) and MUST be specified before any implementation work.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
No tool schema history has been recorded yet.
This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Agent-native MCP server over the public saagarpatel.dev corpus. Read-only, stateless.
Agentic search over your Dewey document collections from any MCP-compatible client.
Read-only MCP server for the OrchestKit docs: full-text search + Markdown fetch. No auth.
Team docs served to AI agents over MCP - search, Markdown reads, version pinning, read audit.
