MCP server for Google Docs, Sheets, Drive, Gmail, and Calendar
Google docs mcp mcp server connects Google Docs MCP to AI assistants that speak the Model Context Protocol. MCP server for Google Docs, Sheets, Drive, Gmail, and Calendar.
Connect Claude Desktop, Cursor, or any MCP client to your Google Docs, Google Sheets, Google Drive, Gmail, and Google Calendar.
Once connected, the assistant can call these 3 tools directly:
Comments — The Comments tool exposed by this serverGmail — The Gmail tool exposed by this serverSetup — 1. Create a GCP project and enable Docs, Sheets, and Drive APIs 2. Create an OAuth client (Web application type, not Desktop) 3. Set the authorizedThe server is distributed via npm as @a-bonus/google-docs-mcp, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
Before the server will start you need to supply 6 environment variables: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, SERVICE_ACCOUNT_PATH, GOOGLE_IMPERSONATE_USER, BASE_URL, JWT_SIGNING_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.
Communication servers earn their keep on volume — summarising channels and threads that would otherwise cost you an hour of scrollback. Google Docs MCP sits in that group, and the shape of its toolset — Comments, Gmail, Setup — tells you what it is really for. Worth comparing against the other communication servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| Comments | The Comments tool exposed by this server. |
| Gmail | The Gmail tool exposed by this server. |
| Setup | 1. Create a GCP project and enable Docs, Sheets, and Drive APIs 2. Create an OAuth client (**Web application** type, not Desktop) 3. Set the authorized redirect URI to {BASE_URL}/oauth/callback 4. Deploy to Cloud Run: |
{
"mcpServers": {
"google-docs": {
"command": "npx",
"args": ["-y", "@a-bonus/google-docs-mcp"],
"env": {
"SERVICE_ACCOUNT_PATH": "/path/to/service-account-key.json",
"GOOGLE_IMPERSONATE_USER": "user@yourdomain.com"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GOOGLE_CLIENT_ID | Configuration value read at startup. | Optional |
| GOOGLE_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| SERVICE_ACCOUNT_PATH | Filesystem location the server is allowed to use. | Optional |
| GOOGLE_IMPERSONATE_USER | Configuration value read at startup. | Optional |
| BASE_URL | Endpoint or connection string the server talks to. | Yes |
| JWT_SIGNING_KEY | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.