Google Docs MCP Server

What is Google Docs MCP Server?

A Model Context Protocol (MCP) server for the Google Docs API, enabling language models to search, create, append to, and update Google Docs programmatically.

How to use Google Docs MCP Server?

Install dependencies with npm install, set up Google OAuth 2.0 credentials (save as credentials.json), run node get-refresh-token.js for authorization, build the server with npm run build, then start with npm start or node build/index.js. Optionally build the Extism plugin for direct testing.

Key features of Google Docs MCP Server

• Search Google Docs in Drive with custom queries
• Create new Google Docs with optional initial content
• Append content to the end of an existing Google Doc
• Replace content in an existing Google Doc with new content

Use cases of Google Docs MCP Server

• An AI assistant searches for relevant documents by query
• Automatically create a new document from a template or user input
• Append generated report data to an existing document
• Update a document with revised content without manual editing

FAQ from Google Docs MCP Server

What are the prerequisites?

Node.js v14+, npm, and a Google Cloud Platform account with the Drive API and Docs API enabled.

How do I obtain Google API credentials?

Create an OAuth 2.0 credential of type “Desktop application” in the Google Cloud Console, download the JSON, and save it as credentials.json in the project root.

How do I run the server after setup?

Run npm start or directly node build/index.js after building the project. The server starts as an MCP endpoint.

Can I test the Extism plugin independently?

Yes, build it first (cd extism-plugin && npm install && npm run build), then call it via the Extism CLI with the appropriate Wasm arguments and an access token.