The trade here is explicit: eight setup steps and a Google Cloud project in exchange for an integration where the client id, the secret and the token all live on your disk and the consent is granted to an app you registered. For anyone who would rather not hand Drive access to a hosted connector, that is the whole argument. It also means you own the upkeep — token refreshes and scope changes are yours to manage.
A local MCP server that bridges Claude Desktop to Google Drive. It uses OAuth credentials you create yourself in the Google Cloud Console, so the authorisation is between your Google account and an app you control — no third-party service sits in the middle.
Your Drive files and folders reachable from the assistant. Authorisation is a one-time browser flow: `npm run tokenGenerator` opens Google's consent screen and writes `token.json` into the project root, after which the built server reuses that token and the assistant works against your Drive without prompting again.
A Google account and an OAuth client you create: in the Google Cloud Console, enable the Google Drive API and create OAuth 2.0 Client ID credentials of type Desktop app, with the redirect URI set to `http://localhost:3000`. Put `CLIENT_ID`, `CLIENT_SECRET` and `REDIRECT_URI` in a `.env` file in the project root. Then `npm install`, `npm run tokenGenerator` to authorise, and `npm run build`. The Claude Desktop entry runs node against the build output with the same three values in its `env` block. The npm package name is `googledrivemcp` (1.0.0) with a `googleDrive` binary pointing at `./build/index.js`.
Build from source — clone the repository and build it, then point your client at the binary