- Home
- MCP servers
- Google Drive
Google Drive
- javascript
2
GitHub Stars
javascript
Language
4 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
This MCP server provides a bridge between your client and Google Drive, enabling you to list, search, upload, download, and manage files and folders through MCP requests. It acts as an OAuth proxy to Google, handling authentication and Drive API calls so you can build workflows that read and organize Drive content from your applications or AI assistants.
How to use
To use this server with an MCP client, connect via the HTTP endpoint exposed by the server and perform actions such as listing files, uploading new content, downloading items, or managing folders and permissions. Use a client that supports the MCP protocol and point it to the provided MCP URL. The server will handle Google OAuth and forward requests to Google Drive on your behalf.
How to install
Prerequisites you need before installation:
- Install Node.js from the official site or using your system package manager.
- npm is included with Node.js.
Install and run the server using the following steps.
# Step 1: Create Google OAuth credentials in Google Cloud Console (not shown here).
# Step 2: Install dependencies and start the server
GOOGLE_CLIENT_ID='your-client-id' \
GOOGLE_CLIENT_SECRET='your-client-secret' \
MCP_TRANSPORT=http \
npm start
Configuration and usage notes
The server requires Google OAuth credentials to authenticate against Drive. You will supply your client ID and client secret when starting the server. By default, the server runs at http://localhost:3000. You can change the port with the PORT environment variable.
To connect from an MCP client, add the HTTP MCP endpoint to your client configuration using the following example.
claude mcp add --transport http google-drive-mcp http://localhost:3000/mcp
Security and scopes
The server uses Google OAuth to obtain access tokens for Drive. It declares the drive scope to enable full access to Drive files. Keep client credentials secure and use restricted redirect URIs in production.
Available tools
files_list
List and search Drive files using Drive query syntax.
file_get
Retrieve metadata for a specific Drive file.
file_download
Download file content, with export support for Google Docs formats.
file_upload
Upload a new file to Drive.
file_update
Update file content or metadata.
file_copy
Copy a file within Drive.
file_move
Move a file to a different folder.
file_trash
Move a file to the trash.
file_untrash
Restore a file from the trash.
file_delete
Permanently delete a file.
folder_create
Create a new folder in Drive.
comments_list
List comments on a file.
comment_get
Get a comment and its replies.
comment_create
Add a new comment to a file.
comment_reply
Reply to a comment.
comment_resolve
Resolve or unresolve a comment.
replies_list
List replies to a comment.
reply_get
Get a specific reply.
reply_update
Update a reply.
reply_delete
Delete a reply.
permissions_list
List who has access to a file.
permission_get
Get a specific permission.
permission_create
Share a file with a user, group, domain, or anyone.
permission_update
Change a user's access level.
permission_delete
Revoke access to a file.