[ MCP SERVER SUMMARY ]
Google Drive MCP server summary
Google Drive MCP (Developer Preview) lets AI agents search files, read content, and manage Drive resources under user OAuth permissions. Bifrost governs which Drive tools each team can use and logs file access for compliance.
| Property | Details |
|---|---|
| Company | |
| Connection type | HTTP |
| Authentication | OAuth 2.0 (Google Cloud client) |
| Package or endpoint | https://drivemcp.googleapis.com/mcp/v1 |
| Capabilities | Search and list files, Read file content and metadata, Copy and create files |
| Official documentation | Google Drive MCP documentation |
Before you start
- Google Cloud project with Drive API and Drive MCP API enabled
- OAuth client credentials
What you can do with Google Drive
- Give research agents governed Drive search without sharing service accounts broadly
- Block write tools for read-only knowledge assistants
- Retain an audit trail of AI file access
[ HOW TO CONNECT ]
Connect Google Drive to Bifrost in three steps
Install Bifrost
Start the gateway locally or deploy in your VPC.
npx -y @maximhq/bifrost
Add Google Drive in MCP Gateway
Open MCP Gateway in the Bifrost dashboard, click New MCP Server, and choose HTTP. Or register via the API below.
• Endpoint: https://drivemcp.googleapis.com/mcp/v1.
• Enable drive.googleapis.com and drivemcp.googleapis.com.
Point clients at Bifrost /mcp
Configure Claude Desktop, Cursor, or Claude Code to use your Bifrost endpoint with a virtual key instead of connecting directly to Google Drive.
{
"mcpServers": {
"bifrost": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer vk_your_virtual_key"
}
}
}
}[ EXAMPLE CONFIG ]
Register Google Drive via API
Add this MCP client with a POST to /api/mcp/client. See Connecting to MCP Servers for full options.
curl -X POST http://localhost:8080/api/mcp/client \
-H "Content-Type: application/json" \
-d '{
"name": "google-drive",
"connection_type": "http",
"connection_string": "https://drivemcp.googleapis.com/mcp/v1",
"auth_type": "oauth",
"tools_to_execute": [
"*"
]
}'[ WHY BIFROST ]
Run Google Drive through one governed gateway
Access control
Virtual keys, RBAC, and tool allowlists per team or agent.
Cost governance
Attribute MCP tool spend alongside LLM usage in one view.
Observability
Log every tool call with latency, server, and virtual key metadata.
Credential isolation
Upstream secrets stay in the gateway — not on every laptop.
[ FAQ ]
Common questions
What does the Google Drive MCP server do?
Google Drive exposes search and list files, read file content and metadata, copy and create files to MCP-compatible AI clients. Bifrost connects to it as an upstream MCP client and exposes approved tools through one governed /mcp endpoint.
How does Google Drive authenticate when used with Bifrost?
Google Drive uses OAuth 2.0 (Google Cloud client). Store credentials in Bifrost's environment or credential configuration so they stay at the gateway instead of being copied into every AI client.
Can Claude Desktop, Cursor, or Claude Code use Google Drive through Bifrost?
Yes. After registering Google Drive in Bifrost, point any HTTP MCP-compatible client at the Bifrost /mcp endpoint and authenticate with a virtual key. The client sees only the tools allowed for that key.
[ RELATED SERVERS ]
More MCP integrations
Gmail
Connect AI assistants to Gmail to search messages, draft and send email, and automate inbox workflows through Google Workspace MCP.
Google Calendar
Let AI assistants access Google Calendar events and automate scheduling workflows through Google Workspace MCP.
Google Chat
Enable AI assistants to work with Google Chat spaces, messages, and collaboration workflows through Google Workspace MCP.