# Google Docs MCP servers — and when you want Sheets instead People searching for a Google Docs MCP server often actually have tabular data. This is an honest map of what exists for Docs, what exists for Sheets, and how to tell which one you need. *Last updated: 2026-07-13 · Source: * ## Key facts - **PasteSheet does not do Google Docs.** It is built for spreadsheets — if your content is genuinely prose, use a Docs or Drive MCP server instead. - Google's **hosted** Workspace MCP servers cover Gmail, Drive, Calendar, Chat and the People API — **not Sheets**. Its managed Google Cloud MCP servers do not cover Sheets either. ([source](https://developers.google.com/workspace/guides/configure-mcp-servers)) - Google does publish an **open-source** Workspace MCP server (a Gemini CLI extension) that includes Sheets — but you run it yourself, and it still needs a Google Cloud project and OAuth credentials. There is **no hosted, zero-setup** Google Sheets MCP server from Google. ([source](https://github.com/google/mcp)) - The difference that matters to an agent is **structure**: a Doc is read as text, while a Sheet can be filtered and aggregated — so a Sheets server answers questions on tables far larger than a context window. ([source](https://modelcontextprotocol.io/specification/2025-06-18)) - PasteSheet's MCP server exposes three tools — `list_tabs`, `get_schema` and `query_rows` — and is **read-only by design**: an agent can query your sheet but can never modify it. ## Is there a Google Docs MCP server? Yes — community open-source servers exist, and Google's own **Workspace MCP server covers Drive**, which reaches Docs files. What Google does *not* ship is a Sheets MCP server. So the coverage is close to the opposite of what most people assume. To be straightforward: **PasteSheet does not do Google Docs.** It is built for spreadsheets. If your content genuinely lives in a Doc, use a Docs or Drive MCP server. This page exists because a lot of people searching for one are actually holding tabular data. ## Docs or Sheets — which do you actually need? The distinction that matters to an AI agent is **structure**. A Doc is prose: the agent reads it as text and reasons over the whole thing. A Sheet is records: the agent can ask for *only* the rows matching a condition, aggregate them, and never load the rest. That difference decides which tool wins. If you ask "what were Q3 sales in the west region?", a Docs server hands the model a wall of text and hopes. A Sheets server filters to the matching rows and returns them — faster, cheaper, and correct on tables far larger than a context window. ## Side by side | | Google Docs MCP | Google Sheets MCP | | --- | --- | --- | | Data shape | Prose / unstructured text | Rows and typed columns | | Agent can filter? | Not really — reads the document | Yes — `query_rows` with filters | | Aggregate (sum, count)? | No | Yes | | Scales past the context window? | Poorly | Yes — it only fetches matching rows | | Best for | Policies, notes, specs, long-form writing | Catalogs, listings, config, reporting data | | Official Google server? | Via Workspace/Drive | **None** — see [the comparison](https://pastesheet.com/guides/google-sheets-mcp-vs-google-official) | ## The common case: your data is a table in a Doc If the thing you want the AI to read is a table you happened to paste into a Doc, move it to a Sheet. You get filtering, typing, and aggregation for free, and the agent stops guessing. That is a five-minute change that makes every subsequent question more reliable. ## What it costs **MCP is included on the Free plan.** Connect any **public** endpoint over MCP with no Google Cloud project and no credit card. Private endpoints and the account-wide workspace server need a paid plan (from **Starter ($9/mo)**) for the keys and OAuth they authenticate with. Pro adds full-text search and aggregation (`count`, `sum`, `avg`, `group_by`) that your AI agent can call through `query_rows`. **Free — $0/month.** For side projects and trying things out. - Endpoints: 3 - Requests: 2,000 / month - Rows per endpoint: 500 - Tabs per endpoint: 1 - Rate limit: 60 / minute ## Frequently asked questions ### Does PasteSheet support Google Docs? No. PasteSheet works with Google Sheets only. If your content is genuinely prose in a Google Doc, you want a Docs or Drive MCP server instead — this page is here to help you tell the difference. ### Does Google have an official Docs MCP server? Google ships a Workspace MCP server covering Gmail, Drive, Calendar, Chat, and the People API. Drive access reaches Docs files. Notably, that same Workspace server does not cover Google Sheets. ### Why is a spreadsheet better for AI than a document? Because it is structured. An agent can read a sheet's schema, filter to only the rows it needs, and aggregate them. With a document it has to read the whole thing as text, which is slower, costlier, and less reliable. ### Can one MCP server handle both? Some community servers bundle multiple Workspace apps. In practice, a server specialised for structured rows gives an agent much better tools for tabular data than a general document reader can. ## Sources - [Model Context Protocol specification](https://modelcontextprotocol.io/specification/2025-06-18) — Model Context Protocol - [Configure the Google Workspace MCP servers](https://developers.google.com/workspace/guides/configure-mcp-servers) — Google - [google/mcp — Google's open-source MCP servers](https://github.com/google/mcp) — Google ## Related guides - [Google Sheets MCP Server for Claude & ChatGPT](https://pastesheet.com/guides/google-sheets-mcp) — Turn any public or private Google Sheet into an MCP server so Claude, Cursor, and ChatGPT can read and query it in plain English. No code, no backend. - [Does Google Have an Official Sheets MCP Server?](https://pastesheet.com/guides/google-sheets-mcp-vs-google-official) — Google's official and Workspace MCP servers both skip spreadsheets. Here is what it shipped, what it left out, and the no-setup way to fill the gap. - [Read-Only Google Sheets MCP for Agents](https://pastesheet.com/guides/read-only-google-sheets-mcp) — A read-only Google Sheets MCP server is safe to hand an AI agent: it can query, filter, and analyze your data but can never modify the spreadsheet. - [Google Sheets MCP Server in Python](https://pastesheet.com/guides/google-sheets-mcp-python) — Build or connect a Google Sheets MCP server from Python. Compare the DIY route against a hosted endpoint, with working client code for both paths. --- [PasteSheet](https://pastesheet.com) turns any Google Sheet into a live REST API and MCP server for AI agents — no backend, no code. Canonical HTML version of this page: