Google Docs

This Google Docs MCP Server lets you connect Claude to your Google Docs workspace, giving you the ability to list, read, create, update, search, and delete documents via natural interactions. It provides a practical bridge between your documents and conversational prompts, handling authorization and data presentation for you.

How to use

You connect your MCP client to the Google Docs MCP Server to perform document operations through natural language prompts. Typical actions include listing all documents, reading the content of a specific document, creating new documents, updating existing ones, searching for documents by text, and deleting documents. The server handles authentication and token refreshing automatically, and it formats results in a user-friendly way.

How to install

Clone the project and install dependencies

git clone https://github.com/yourusername/MCP-Google-Doc.git
cd MCP-Google-Doc
npm install

# Create Google OAuth 2.0 credentials in your Google Cloud project
# Enable Google Docs API and Google Drive API
# Download credentials.json and place it in the project root

# Build the project
npm run build

# Run the server
npm start

The first run prompts you to authenticate with Google. Complete the authorization flow to generate a token.json file that stores your access tokens for future sessions.

## Connecting to Claude for Desktop

On macOS ~/Library/Application Support/Claude/claude_desktop_config.json On Windows %APPDATA%\Claude\claude_desktop_config.json

Add this MCP server configuration to the Claude Desktop config:

{ "mcpServers": { "googledocs": { "command": "node", "args": ["/absolute/path/to/build/server.js"] } } }

Replace `/absolute/path/to/build/server.js` with the actual path to your built server.js file. Restart Claude for Desktop to apply the changes.

Security considerations

Credential safety is important. The server uses sensitive credentials that should never be shared or committed to version control. Token files are refreshed automatically, and you can revoke access by removing the token file and revoking the app from your Google Account Security settings.

Development notes

The server is structured to compile TypeScript sources into JavaScript under build/ and run from build/server.js when started in production-like environments. If you modify functionality, rebuild and restart to apply changes. The project exposes endpoints and prompts for document operations in a conversational style.

Troubleshooting

If authentication fails, delete token.json and start the server again to trigger a new OAuth flow. If the Google Docs or Drive APIs are not functioning, confirm that both APIs are enabled in your Google Cloud project and that the OAuth credentials include the correct scopes for Docs and Drive access.

Notes

Environment-based startup options are available via the standard Node.js runtime. If you choose to run in a non-default environment, ensure that the runtime can access credentials.json or use environment variables as described in the setup steps.

Available tools

list-docs

Lists all Google Docs in your Drive and presents them in a readable format.

read-doc

Reads and returns the content of a specific Google Doc by its ID.

create-doc

Creates a new Google Doc with a given title and optional initial content.

update-doc

Updates an existing Google Doc with new content (append or replace).

insert-text

Inserts text into a document at the current cursor or specified location.

search-docs

Searches for Google Docs containing specific text.

delete-doc

Deletes a Google Doc by its ID.

create-doc-template

Helps create a new document based on a topic and writing style.

analyze-doc

Analyzes the content of a document and provides a summary.