Google's Workspace CLI returns raw JSON. `gdocs-to-md-mcp` returns markdown. Here's why that matters.

with MCP support — so technically, your AI assistant can read a Google Doc now. But what it gets back is raw API JSON: a 500-line nested tree of StructuralElement objects, ParagraphElement arrays, and TextRun objects with style metadata buried three levels deep.

Your LLM can parse it. But it shouldn't have to.

Why Markdown Matters for LLMs

Think about what markdown gives an LLM that raw JSON doesn't:

• 
  # Heading tells it "this is a new section" — no need to infer structure from nested objects


• 
  `bold*`* signals emphasis — in JSON, that's a textStyle.bold: true property buried inside a TextRun object


• 
  | tables | stay readable inline — in JSON, that's a matrix of TableCell arrays inside TableRow arrays inside a Table object


• 
  - lists just work — in JSON, you're parsing bullet.nestingLevel and listProperties.nestingLevels[n].glyphType
  

An LLM can read markdown the way a human reads a document. JSON forces it to reconstruct the document from parts.

And the research backs this up. An showed Markdown-KV hitting 60.7% accuracy — 16 points ahead of CSV and JSON alternatives. Markdown is also recommends XML tags with markdown/plain text for document input. recommends markdown headings for structuring prompts.

The Solution

"

Claude calls read_google_doc, gets clean structured markdown, and actually understands the document — sections, emphasis, tables, all of it. Compare that to the raw \n\n-delimited text blob from the default Google Drive integration. Night and day.

Three tools, nothing more:

• 
  read_google_doc — URL or doc ID in, markdown out


• 
  search_google_docs — find docs by keyword


• 
  list_recent_docs — see what's been updated recently

No 80-tool mega-server. No Gmail. No Calendar. Just Google Docs to markdown, done right.

"But doesn't Google have a Workspace CLI?"

Yes — Google recently released an official

npm: — Up to 40% performance variance across formats