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

> Upload photos and create and organize albums in Google Photos on behalf of each of your users.

- Page: https://www.agent200.com/connectors/google-photos/
- Category: Files and knowledge
- Authentication: Managed OAuth
- Identifier in code: `google_photos`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-18

## Instructions for AI agents

Connector: Google Photos, through Agent200. In code: "google_photos".
What it does: Upload photos and create and organize albums in Google Photos on behalf of each of your users.
Page: https://www.agent200.com/connectors/google-photos/

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 Photos's own page, through the authorization link Agent200 returns. Never ask a user for a Google Photos 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_photos_list_albums, google_photos_list_media. Write tools: google_photos_upload_media, google_photos_create_album, google_photos_add_to_album. Name "google_photos" 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/connectors/google-photos/framework/claude/
   https://www.agent200.com/connectors/google-photos/framework/chatgpt/
   https://www.agent200.com/connectors/google-photos/framework/claude-code/
   https://www.agent200.com/connectors/google-photos/framework/muse/
   https://www.agent200.com/connectors/google-photos/framework/grok-bot/
   https://www.agent200.com/connectors/google-photos/framework/openai-dots/
   https://www.agent200.com/connectors/google-photos/framework/claude-duet/
   https://www.agent200.com/connectors/google-photos/framework/hermes-agent/
   https://www.agent200.com/connectors/google-photos/framework/openclaw/

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

## About

With the Google Photos connector, your agent works in each user's own Google Photos library. It can upload photos and videos, create albums, add items to them, and list the albums and items the connection has added, using only the tools your project allows.

Google Photos is Google's service for storing, organizing and sharing photos and videos.

## Google Photos tools

- **Upload media** (`google_photos_upload_media`, write): Upload a photo or video to the user's library.
- **Create an album** (`google_photos_create_album`, write): Create a new album.
- **Add to an album** (`google_photos_add_to_album`, write): Add uploaded items to an album the connection created.
- **List albums** (`google_photos_list_albums`, read): List the albums the connection created.
- **List media** (`google_photos_list_media`, read): List the photos and videos the connection uploaded.

## Limits you can set

**Turn single tools on or off.** Let the agent list and organize albums, and switch off `google_photos_upload_media` so it can never add to a library.

**Restrict what the agent reaches.** Choose the endpoints and scopes a project may use, for example albums but not uploads. A call outside them is refused.

## 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 Photos

Each end user authorizes their own Google Photos 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 Photos account, once.
const connection = await agent200
  .user("user_123")
  .connect("google_photos");

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 Photos tools

Name the user, the model and the tools. The model decides which Google Photos 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: "Upload these receipts to a new album called Expenses",
    tools: ["google_photos"],
  });

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

(Conceptual example of the Agent200 SDK.)

## Sign-in and permissions

**Who signs in.** Each of your users, once, on Google's own sign-in page. You never see or store their Google password.

**What access is requested.** The scopes the connection needs, such as adding photos to their library or managing albums the app created, listed on Google's authorization screen. Users can remove the app later from their Google Account settings.

## Example requests

- "Upload these receipts to a new album called Expenses"
- "Create an album for the team offsite"
- "Show the albums you have made for me"

## Guides: Google Photos with your AI framework

- [Google Photos + Claude](https://www.agent200.com/connectors/google-photos/framework/claude.md): Connect Google Photos to Claude through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Google Photos + ChatGPT](https://www.agent200.com/connectors/google-photos/framework/chatgpt.md): Give ChatGPT access to Google Photos through Agent200: managed OAuth, ready-made tools and one API key.
- [Google Photos + Claude Code](https://www.agent200.com/connectors/google-photos/framework/claude-code.md): Have Claude Code build a Google Photos agent with the Agent200 SDK: managed OAuth, ready-made tools and one API key.
- [Google Photos + Muse](https://www.agent200.com/connectors/google-photos/framework/muse.md): Connect Google Photos to Muse through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Google Photos + Grok Bot](https://www.agent200.com/connectors/google-photos/framework/grok-bot.md): Connect Google Photos to Grok Bot through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Google Photos + OpenAI Dots](https://www.agent200.com/connectors/google-photos/framework/openai-dots.md): Give OpenAI Dots access to Google Photos through Agent200: managed OAuth, ready-made tools and one API key.
- [Google Photos + Claude Duet](https://www.agent200.com/connectors/google-photos/framework/claude-duet.md): Connect Google Photos to Claude Duet through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Google Photos + Hermes Agent](https://www.agent200.com/connectors/google-photos/framework/hermes-agent.md): Connect Google Photos to Hermes Agent through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Google Photos + OpenClaw](https://www.agent200.com/connectors/google-photos/framework/openclaw.md): Connect Google Photos to OpenClaw through Agent200's MCP server: managed OAuth, ready-made tools and one API key.

## FAQ

### Who handles the Google Photos 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 Photos.

### 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 Photos connection, never another user's. It cannot reach anything the user or Google Photos has not authorized.

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

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

## Related connectors

- [Google Drive](https://www.agent200.com/connectors/google-drive.md): Find, read and organize the files in each user's Drive.
- [OneDrive](https://www.agent200.com/connectors/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/connectors/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/connectors/notion.md): Search, read and write Notion pages and databases on behalf of each of your users.

---

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