Skip to content
Back to search

google-drive-mcp

SkillWorks with Claude CodeGitHub

A Model Context Protocol (MCP) server that provides secure integration with Google Drive, Docs, Sheets, Slides and Calendar. It allows Claude Desktop and other MCP clients to manage files in Google Drive through a standardized interface.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/piotr-agier--google-drive-mcp/badge.svg)](/listings/piotr-agier--google-drive-mcp)

HTML

<a href="/listings/piotr-agier--google-drive-mcp"><img src="/api/listings/piotr-agier--google-drive-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

1. Create Google OAuth credentials

In a Google Cloud project:

1. Enable the Drive, Docs, Sheets, Slides, and Calendar APIs. 2. Configure the OAuth consent screen and add your Google account as a test user when the app is in testing. 3. Create an OAuth client with application type **Desktop app**. 4. Download the JSON file and save it as:

~/.config/google-drive-mcp/gcp-oauth.keys.json

The [setup guide](docs/setup.md) has the complete Google Cloud walkthrough and alternative credential locations.

2. Authenticate

npx -y @piotr-agier/google-drive-mcp auth

Complete the Google consent flow in the browser. Tokens are stored by default at `~/.config/google-drive-mcp/tokens.json`.

3. Add the server to your MCP client

For clients that use the common `mcpServers` configuration shape:

{
  "mcpServers": {
    "google-drive": {
      "command": "npx",
      "args": ["-y", "@piotr-agier/google-drive-mcp"]
    }
  }
}

Restart the client after saving its configuration. Claude Desktop paths and HTTP examples are documented in [Client configuration](docs/clients.md#client-configuration).

4. Make a first tool call

Ask your client:

Run authGetStatus and tell me which Google account is active.

Then try a read-only Drive request:

Search my Google Drive for files modified in the last seven days.

If the identity is wrong or search returns no files, use the [troubleshooting guide](docs/troubleshooting.md).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 172 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Google Drive MCP Server
  2. [![MCP Toplist](https://mcptoplist.com/badge/io.github.piotr-agier%2Fgoogle-drive-mcp.svg)](https://mcptoplist.com/server/io.github.piotr-agier%2Fgoogle-drive-mcp)
  3. Connect an MCP client to Google Drive, Docs, Sheets, Slides, and Calendar through one self-hosted server. Search and organize files, create and edit Workspace content, manage sharing, and automate multi-step workflows while keeping control of the Google identity and credentials used for every call.
  4. ## Why this server
  5. - **Drive-first workflows:** 130 tools cover file management, Shared Drives, permissions, revisions, rich Docs editing, Sheets formatting, Slides authoring, and Calendar events.
  6. - **Local or hosted:** use stdio for a personal desktop client, Streamable HTTP for a hosted integration, or OAuth-protected team mode for a shared service.
  7. - **Identity control:** local OAuth supports multiple Google accounts and per-tool account selection; service accounts and externally managed OAuth tokens are also supported.
  8. - **Agent-friendly access:** tools expose targeted operations, while the optional `gdrive:///` resource interface supports direct reading and discovery.
  9. - **Open and self-hosted:** credentials and tokens stay in the environment you operate.
  10. This project remains focused on deep Drive and editor workflows rather than attempting to expose every Google Workspace API.
  11. ## Client compatibility
  12. Compatibility is determined by the transport and authentication flow a client supports.
  13. | Client type | Transport | Recommended mode |
  14. |---|---|---|
  15. | Claude Desktop | stdio | Local OAuth |
  16. | Other local MCP clients, including Gemini CLI | stdio | Local OAuth |
  17. | claude.ai custom connectors | Streamable HTTP | Team mode |
  18. | Other remote MCP clients | Streamable HTTP | Single identity behind access control, or team mode with OAuth 2.1 |
  19. See [Client configuration](docs/clients.md#client-configuration) for configuration examples and transport requirements.
  20. ## Quick start
  21. ### 1. Create Google OAuth credentials
  22. In a Google Cloud project:
  23. 1. Enable the Drive, Docs, Sheets, Slides, and Calendar APIs.
  24. 2. Configure the OAuth consent screen and add your Google account as a test user when the app is in testing.
  25. 3. Create an OAuth client with application type **Desktop app**.
  26. 4. Download the JSON file and save it as:
  27. ```text
  28. ~/.config/google-drive-mcp/gcp-oauth.keys.json
  29. ```
  30. The [setup guide](docs/setup.md) has the complete Google Cloud walkthrough and alternative credential locations.
  31. ### 2. Authenticate
  32. ```bash
  33. npx -y @piotr-agier/google-drive-mcp auth
  34. ```
  35. Complete the Google consent flow in the browser. Tokens are stored by default at `~/.config/google-drive-mcp/tokens.json`.
  36. ### 3. Add the server to your MCP client
  37. For clients that use the common `mcpServers` configuration shape:
  38. ```json
  39. {
  40. "mcpServers": {
  41. "google-drive": {
  42. "command": "npx",
  43. "args": ["-y", "@piotr-agier/google-drive-mcp"]
  44. }
  45. }
  46. }
  47. ```
  48. Restart the client after saving its configuration. Claude Desktop paths and HTTP examples are documented in [Client configuration](docs/clients.md#client-configuration).
  49. ### 4. Make a first tool call
  50. Ask your client:
  51. ```text
  52. Run authGetStatus and tell me which Google account is active.
  53. ```
  54. Then try a read-only Drive request:
  55. ```text
  56. Search my Google Drive for files modified in the last seven days.
  57. ```
  58. If the identity is wrong or search returns no files, use the [troubleshooting guide](docs/troubleshooting.md).
  59. ## What you can do
  60. ### Organize Drive
  61. ```text
  62. Find PDF files in /Reports, create an Archive folder there, and move files older
  63. than one year into it.
  64. ```
  65. ### Build a report
  66. ```text
  67. Create a Google Sheet for monthly results, summarize it in a Google Doc, and
  68. create a short Google Slides presentation from the summary.
  69. ```
  70. ### Edit a document
  71. ```text
  72. Find the "Project Plan" document, replace the old launch date, format the new
  73. date in bold, and add a comment describing the change.
  74. ```
  75. ### Prepare a meeting
  76. ```text
  77. Create a Calendar event with a Google Meet link and attach the project brief
  78. from Drive.
  79. ```
  80. <!--
  81. Anchors for sections that lived in this README before the guides moved to docs/.
  82. External deep links (directory listings, issue replies, blog posts) land on the
  83. table below, which names the guide each section moved to. Do not remove.
  84. -->
  85. <a id="features"></a><a id="example-usage"></a><a id="requirements"></a>
  86. <a id="google-cloud-setup"></a><a id="installation"></a><a id="docker-usage"></a>
  87. <a id="configuration"></a><a id="runtime-configuration-cli-args-or-env-vars"></a>
  88. <a id="usage-with-claude-desktop"></a><a id="streamable-http-transport"></a>
  89. <a id="team-mode-multi-user-http-deployments"></a><a id="available-tools"></a>
  90. <a id="external-authentication"></a><a id="multi-account-support"></a>
  91. <a id="authentication-flow"></a><a id="troubleshooting"></a><a id="development"></a>
  92. <a id="advanced-configuration"></a><a id="contributing"></a><a id="support"></a>
  93. ## Documentation
  94. Every section that used to live in this README is now in one of these guides.
  95. | Guide | Contents |
  96. |---|---|
  97. | [Setup](docs/setup.md) | Requirements, Google Cloud APIs, OAuth credentials, and installation |
  98. | [Client configuration](docs/clients.md) | Supported transports and client configuration |
  99. | [Authentication](docs/authentication.md) | Local OAuth, multi-account, service accounts, external tokens, and scopes |
  100. | [Configuration](docs/configuration.md) | CLI flags, environment variables, defaults, and precedence |
  101. | [Deployment](docs/deployment.md) | Docker, Streamable HTTP, team mode, and reverse-proxy security |
  102. | [Tool reference](docs/tools.md) | All Drive, Docs, Sheets, Slides, Calendar, and account tools |
  103. | [Troubleshooting](docs/troubleshooting.md) | Authentication, API, identity, Docker, and rate-limit problems |
  104. | [Development](docs/development.md) | Repository structure, build commands, tests, and contributions |
  105. ## Security
  106. - Never commit OAuth credentials, service-account keys, access tokens, refresh tokens, or `tokens.json`.
  107. - Use the narrowest OAuth scopes that support the tools you need.
  108. - Keep the default HTTP bind address on `127.0.0.1` unless the server is protected by TLS and access control.
  109. - Use [team mode](docs/deployment.md#team-mode-multi-user-http-deployments) for shared deployments so every request is authenticated as its caller.
  110. - Treat `team-store.json` as a secret because it contains members' Google refresh tokens.
  111. See [Authentication](docs/authentication.md) and [Deployment](docs/deployment.md) for the complete security and identity model.
  112. ## Development and support
  113. See the [development guide](docs/development.md) to build and test the project.
  114. - Report defects and request features in [GitHub Issues](https://github.com/piotr-agier/google-drive-mcp/issues).
  115. - Review released changes in the [changelog](CHANGELOG.md).
  116. - Contributions are welcome through pull requests.
  117. ## License
  118. [MIT](LICENSE)
  119. ## Acknowledgments
  120. - Built on the [Model Context Protocol](https://modelcontextprotocol.io).
  121. - Uses the [Google APIs Node.js Client](https://github.com/googleapis/google-api-nodejs-client).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.