Add the Google Drive (Workspace MCP) MCP server to Cursor
Config last verified Jun 1, 2026
The exact config to run Google Drive (Workspace MCP) in Cursor — paste it in, restart, and the tools load.
Prerequisites
- Cursor installed.
- GOOGLE_OAUTH_CLIENT_ID — OAuth client ID from your Google Cloud project.
- GOOGLE_OAUTH_CLIENT_SECRET — OAuth client secret for the Google Cloud OAuth client.
Setup
1. Open ~/.cursor/mcp.json
2. Add this configuration
Add to ~/.cursor/mcp.json
~/.cursor/mcp.json
json
{
"mcpServers": {
"google-drive": {
"command": "uvx",
"args": [
"workspace-mcp",
"--tools",
"drive"
],
"env": {
"GOOGLE_OAUTH_CLIENT_ID": "<GOOGLE_OAUTH_CLIENT_ID>",
"GOOGLE_OAUTH_CLIENT_SECRET": "<GOOGLE_OAUTH_CLIENT_SECRET>"
}
}
}
}3. Restart Cursor and confirm the Google Drive (Workspace MCP) tools load.
Gotchas
Cursor keeps MCP servers under an "mcpServers" object in ~/.cursor/mcp.json for global use, and also reads a project-scoped .cursor/mcp.json so a repository can ship its own servers. Remote servers are configured with a bare "url" field and connect natively, with OAuth handled in-app when a server requires it.