About Google Docs MCP Server
Google Docs MCP Server connects MCP-compatible assistants to Google Docs for document management. It covers creation, search, sharing, updates, and export through a set of dedicated tools.
Key features
- 01Create and delete documents
- 02Read and update document content
- 03List and search documents
- 04Export documents to other formats
- 05Share documents with users
- 06Verify API connection
Use cases
- 01Create documents from assistant workflows
- 02Find documents by title or content
- 03Update and share existing documents
- 04Export a document as PDF or plain text
MCP support
Exposes Google Docs operations as MCP tools for compatible assistants, including document creation, retrieval, editing, search, sharing, and export.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEGoogle Docs MCP Server
A powerful Model Context Protocol (MCP) server implementation for seamless Google Docs API integration, enabling AI assistants to create, read, update, and manage Google Docs.
Features
- Create new Google Docs with custom titles and content
- Retrieve document content and metadata
- Update existing documents with new content
- List all accessible documents
- Delete documents
- Export documents to different formats (PDF, plain text, etc.)
- Share documents with specific users
- Search for documents by title or content
- Verify connection and credentials
Prerequisites
- Node.js 18 or higher
- A Google Cloud project with the Google Docs API enabled
- Authentication credentials (API key, service account, or OAuth2)
Installation
-
Clone this repository:
git clone https://github.com/lkm1developer/google-docs-mcp-server.git cd google-docs-mcp-server -
Install dependencies:
npm install -
Create a
.envfile with your Google Cloud credentials:# Required GOOGLE_CLOUD_PROJECT_ID=your-project-id # Choose one authentication method: # Option 1A: Service Account with file path (recommended for production) GOOGLE_APPLICATION_CREDENTIALS=path/to/your-service-account-key.json # Option 1B: Service Account with JSON content directly # Useful for environments where you can't create files GOOGLE_APPLICATION_CREDENTIALS_JSON={"type":"service_account","project_id":"...","private_key":"...","client_email":"..."} # Option 2: API Key (simpler for development) GOOGLE_API_KEY=your-api-key # Option 3: OAuth2 (required for user-specific operations) client_id=your-oauth-client-id client_secret=your-oauth-client-secret refresh_token=your-oauth-refresh-token
Authentication Setup
Service Account Authentication
- Go to the Google Cloud Console
- Create a new project or select an existing one
- Enable the Google Docs API and Google Drive API
- Go to "IAM & Admin" > "Service Accounts"
- Create a new service account
- Grant it the necessary roles (e.g., "Docs API User", "Drive API User")
- Create and download a JSON key for the service account
- Set the path to this JSON file in your
.envfile
OAuth2 Authentication
For operations that require user consent (like creating/editing documents):
- Go to the Google Cloud Console
- Create a new project or select an existing one
- Enable the Google Docs API and Google Drive API
- Go to "APIs & Services" > "Credentials"
- Create OAuth client ID credentials (Web application type)
- Add authorized redirect URIs (e.g., http://localhost:3000/oauth2callback)
- Note your Client ID and Client Secret
- Use the following script to get a refresh token:
// get-refresh-token.js
const { google } = require('googleapis');
const http = require('http');
const url = require('url');
const open = require('open');
const destroyer = require('server-destroy');
async function getRefreshToken() {
const oauth2Client = new google.auth.OAuth2(
'YOUR_CLIENT_ID',
'YOUR_CLIENT_SECRET',
'http://localhost:3000/oauth2callback'
);
const scopes = [
'https://www.googleapis.com/auth/documents',
'https://www.googleapis.com/auth/drive'
];
const authorizeUrl = oauth2Client.generateAuthUrl({
access_type: 'offline',
scope: scopes,
prompt: 'consent'
});
console.log('Opening browser for authorization...');
open(authorizeUrl);
return new Promise((resolve, reject) => {
const server = http.createServer(async (req, res) => {
try {
const queryParams = url.parse(req.url, true).query;
if (queryParams.code) {
res.end('Authentication successful! You can close this window.');
server.destroy();
const { tokens } = await oauth2Client.getToken(queryParams.code);
console.log('\nRefresh Token:', tokens.refresh_token);
console.log('\nAdd this refresh token to your .env file as refresh_token');
resolve(tokens.refresh_token);
}
} catch (e) {
reject(e);
}
}).listen(3000);
destroyer(server);
});
}
getRefreshToken().catch(console.error);
Run this script with:
npm install googleapis open server-destroy
node get-refresh-token.js
Building and Running
-
Build the project:
npm run build -
Test your connection:
npx tsx src/test-connection.ts -
Run the server:
npm startOr with specific credentials:
npm start -- --GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account.json --GOOGLE_CLOUD_PROJECT_ID=your-project-id # Or with JSON content directly: npm start -- --GOOGLE_APPLICATION_CREDENTIALS_JSON='{"type":"service_account","project_id":"..."}' --GOOGLE_CLOUD_PROJECT_ID=your-project-id -
Run the SSE server with authentication:
npx mcp-proxy-auth node dist/index.js
Implementing Authentication in SSE Server
The SSE server uses the mcp-proxy-auth package for authentication. To implement authentication:
-
Install the package:
npm install mcp-proxy-auth -
Set the
AUTH_SERVER_URLenvironment variable to point to your API key verification endpoint:export AUTH_SERVER_URL=https://your-auth-server.com/verify -
Run the SSE server with authentication:
npx mcp-proxy-auth node dist/index.js -
The SSE URL will be available at:
localhost:8080/sse?apiKey=apikeyReplace
apikeywith your actual API key for authentication.
The mcp-proxy-auth package acts as a proxy that:
- Intercepts requests to your SSE server
- Verifies API keys against your authentication server
- Only allows authenticated requests to reach your SSE endpoint
Docker Support
You can also run the server using Docker:
-
Build the Docker image:
docker build -t google-docs-mcp-server . -
Run the container:
docker run -p 8080:8080 \ -e GOOGLE_CLOUD_PROJECT_ID=your-project-id \ -e GOOGLE_APPLICATION_CREDENTIALS_JSON='{"type":"service_account","project_id":"..."}' \ -e client_id=your-client-id \ -e client_secret=your-client-secret \ -e refresh_token=your-refresh-token \ -e AUTH_SERVER_URL=https://your-auth-server.com/verify \ google-docs-mcp-server
MCP Integration
To use this server with Claude or other MCP-compatible assistants, add it to your MCP settings:
{
"mcpServers": {
"google-docs": {
"command": "node",
"args": ["/path/to/google-docs-mcp-server/dist/index.js"],
"env": {
"GOOGLE_CLOUD_PROJECT_ID": "your-project-id",
"GOOGLE_APPLICATION_CREDENTIALS": "/path/to/your-service-account-key.json",
"GOOGLE_APPLICATION_CREDENTIALS_JSON": "{\"type\":\"service_account\",\"project_id\":\"...\"}",
"GOOGLE_API_KEY": "your-api-key",
"client_id": "your-oauth-client-id",
"client_secret": "your-oauth-client-secret",
"refresh_token": "your-oauth-refresh-token"
},
"disabled": false,
"autoApprove": []
}
}
}
Available Tools
| Tool Name | Description | Required Parameters |
|---|---|---|
google_docs_create | Create a new Google Doc | title, content (optional) |
google_docs_get | Get a Google Doc by ID | documentId |
google_docs_update | Update a Google Doc with new content | documentId, content, replaceAll (optional) |
google_docs_list | List Google Docs accessible to the authenticated user | pageSize (optional), pageToken (optional) |
google_docs_delete | Delete a Google Doc | documentId |
google_docs_export | Export a Google Doc to different formats | documentId, mimeType (optional) |
google_docs_share | Share a Google Doc with specific users | documentId, emailAddress, role (optional) |
google_docs_search | Search for Google Docs by title or content | query, pageSize (optional), pageToken (optional) |
google_docs_verify_connection | Verify connection with Google Docs API | None |
Example Usage
Here are some examples of how to use the tools:
Create a new document
{
"name": "google_docs_create",
"arguments": {
"title": "My New Document",
"content": "This is the content of my new document."
}
}
Get a document
{
"name": "google_docs_get",
"arguments": {
"documentId": "1Ax7vsdg3_YhKjkl2P0TZ5XYZ123456"
}
}
Update a document
{
"name": "google_docs_update",
"arguments": {
"documentId": "1Ax7vsdg3_YhKjkl2P0TZ5XYZ123456",
"content": "This is the new content.",
"replaceAll": true
}
}
Search for documents
{
"name": "google_docs_search",
"arguments": {
"query": "meeting notes",
"pageSize": 5
}
}
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.