gdrive-knowledgelisted

# Google Drive knowledge Answer questions about your team's Google Drive using the **gdrive-knowledge** MCP server — a permission-filtered knowledge graph over your documents. Every result is masked *before* retrieval to exactly the documents you can read; forbidden documents are invisible, not "locked" — they never appear in results, neighborhoods, or counts. ## When to use Questions about documents, files, folders, specs, contracts, meeting notes, proposals, call transcripts, or entities mentioned in documents. Examples: "what does the consulting contract say about termination?", "find the design doc about embeddings", "which docs mention Northwind?". ## Tools (gdrive-knowledge server) | Tool | Purpose | |------|---------| | `search` | Search the knowledge graph. Returns node **pointers** plus a small neighborhood for top hits — never document content. Args: `query`, `top_k`, `type_filter`, `relation_filter`. | | `get_node` | Read a node. `detail="full"` returns the document's chunk text — **this is the only tool that returns content.** | | `related_work` | Explore neighbors (folders, sibling docs, entities) of a node you found. Args: `node_id`, `hops` (1–2), `type_filter`, `relation_filter`. | | `describe_schema` | Discover valid `type_filter` / `relation_filter` values for *your* allowed subgraph. | | `read_document` | Legacy alias for `get_node(doc_id, detail="full")`. | > Claude surfaces these prefixed by the server, e.g. `…gdrive-knowledge__search`. ## Workflow