How to add Google Drive MCP
Prepare Google Drive access, add the connection in Durin, and connect an agent with your personal connection URL.
Prepare Google Drive access
Confirm Workspace Developer Preview eligibility. Enable the Drive API and Drive MCP service, configure consent and permitted users, and use your own web OAuth client with the Durin callback. Check Google’s file eligibility rules.
Save, review and enable
Choose Custom MCP, give it a name such as Google Drive — Engineering, and enter https://drivemcp.googleapis.com/mcp/v1 as the endpoint.
- Open Admin → Connections → All providers. Choose Custom MCP.
- Choose User signs in, OAuth and Sign in now. Supply registered client details when required; for Custom MCP keep Advanced → Transport → Streamable HTTP.
- Save the draft, Sign in to provider, then Discover available tools.
- Save permission review for an allowed read, including resources and scopes, and obtain the matching deployed validator release.
- Run read test with approved JSON arguments. Resolve blockers, choose Review billing and Confirm and enable, then Enable reviewed tool.
Connect your agent
In the personal workspace, complete your own provider access. Choose Set up connection URL, then Copy connection URL. Follow MCP client setup, authenticate for that exact URL, and verify a reviewed read in activity.
Troubleshooting
Sign-in works but the tool is unavailable
Check the deployed validator, permitted resource, current team access and personal consent. A saved draft or discovered tool alone does not grant access.
Frequently asked questions
Which provider OAuth callback should I register?
Use your exact Durin app origin followed by /connections/callback. Client sign-in to Durin is separate.