# Google Drive for AI agents. Managed auth, ready-made tools.

> Find, read and organize the files in each user's Drive.

- Page: https://www.agent200.com/tools/google-drive/
- Category: Files and knowledge
- Authentication: Managed OAuth
- Identifier in code: `google_drive`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-15

## Instructions for AI agents

Connector: Google Drive, through Agent200. In code: "google_drive".
What it does: Find, read and organize the files in each user's Drive.
Page: https://www.agent200.com/tools/google-drive/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Google Drive's own page, through the authorization link Agent200 returns. Never ask a user for a Google Drive password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: google_drive_search, google_drive_get_file. Write tools: google_drive_upload, google_drive_share. Name "google_drive" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/tools/google-drive/framework/claude/
   https://www.agent200.com/tools/google-drive/framework/chatgpt/
   https://www.agent200.com/tools/google-drive/framework/claude-code/
   https://www.agent200.com/tools/google-drive/framework/muse/
   https://www.agent200.com/tools/google-drive/framework/grok-bot/
   https://www.agent200.com/tools/google-drive/framework/openai-dots/
   https://www.agent200.com/tools/google-drive/framework/claude-duet/
   https://www.agent200.com/tools/google-drive/framework/hermes-agent/
   https://www.agent200.com/tools/google-drive/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

## Google Drive tools

- **Search files** (`google_drive_search`, read): Find files by name, type or content.
- **Read a file** (`google_drive_get_file`, read): Read a file's content and metadata.
- **Upload a file** (`google_drive_upload`, write): Create a file in a folder.
- **Share a file** (`google_drive_share`, write): Give a person access to a file.

## Get started

### Step 1: Set up the SDK

Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 2: Let your user connect Google Drive

Each end user authorizes their own Google Drive account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

File `connect.js`:

```js
// Each end user authorizes their own Google Drive account, once.
const connection = await agent200
  .user("user_123")
  .connect("google_drive");

if (connection.authorizationUrl) {
  // Show this link to your user; Agent200 handles the rest.
  console.log(connection.authorizationUrl);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 3: Run with the Google Drive tools

Name the user, the model and the tools. The model decides which Google Drive tools to call, and Agent200 executes them with that user's connection.

File `run.js`:

```js
const result = await agent200
  .user("user_123")
  .run({
    model: "openai/gpt-5.6-sol",
    input: "Find the Q3 board deck",
    tools: ["google_drive"],
  });

console.log(result.output);
```

(Conceptual example of the Agent200 SDK.)

## Example requests

- "Find the Q3 board deck"
- "Share the roadmap with the design team"

## Guides: Google Drive with your AI framework

- [Google Drive + Claude](https://www.agent200.com/tools/google-drive/framework/claude.md): Connect Google Drive to Claude through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Google Drive + ChatGPT](https://www.agent200.com/tools/google-drive/framework/chatgpt.md): ChatGPT cannot send an API key to a custom MCP server, so this guide builds Google Drive into your own agent with OpenAI's models and the Agent200 SDK.
- [Google Drive + Claude Code](https://www.agent200.com/tools/google-drive/framework/claude-code.md): Have Claude Code build a Google Drive agent with the Agent200 SDK: managed OAuth, ready-made tools and one API key.
- [Google Drive + Muse](https://www.agent200.com/tools/google-drive/framework/muse.md): Connect Google Drive to Muse through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Google Drive + Grok Bot](https://www.agent200.com/tools/google-drive/framework/grok-bot.md): Connect Google Drive to Grok Bot through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Google Drive + OpenAI Dots](https://www.agent200.com/tools/google-drive/framework/openai-dots.md): Dots cannot send an API key to a custom MCP server, so this guide builds an always-on Google Drive agent with OpenAI's models and the Agent200 SDK.
- [Google Drive + Claude Duet](https://www.agent200.com/tools/google-drive/framework/claude-duet.md): Connect Google Drive to Claude Duet through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Google Drive + Hermes Agent](https://www.agent200.com/tools/google-drive/framework/hermes-agent.md): Connect Google Drive to Hermes Agent through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Google Drive + OpenClaw](https://www.agent200.com/tools/google-drive/framework/openclaw.md): Connect Google Drive to OpenClaw through Agent200's MCP server: managed OAuth, ready-made tools and one API key.

## FAQ

### Who handles the Google Drive OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Google Drive.

### Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Google Drive connection, never another user's. It cannot reach anything the user or Google Drive has not authorized.

### Can I limit what my agent can do in Google Drive?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

## Related connectors

- [OneDrive](https://www.agent200.com/tools/onedrive.md): Search, read, upload and share OneDrive files, including Word, Excel and PowerPoint documents, on behalf of each of your users.
- [Dropbox](https://www.agent200.com/tools/dropbox.md): Search, read, upload and organize Dropbox files, and create shared links, on behalf of each of your users.
- [Notion](https://www.agent200.com/tools/notion.md): Search, read and write Notion pages and databases on behalf of each of your users.
- [Confluence](https://www.agent200.com/tools/confluence.md): Search, read and write Confluence pages and comments on behalf of each of your users, within the spaces they can access.

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
