How to Connect Google Photos to Claude (and What It Can't Do)
There is no official Claude connector for Google Photos, and no Google-published MCP server — the only route is a community MCP, and even that is boxed in by Google’s own API restrictions. In March 2025 Google deprecated the core Google Photos Library API scopes, so any tool can now touch only the media it uploaded itself, or media a user hand-picks through the new Picker API each session. That single change is why “connect Google Photos to Claude” is far thinner than it sounds.
Below: what the API actually still allows, how a community MCP server bridges Claude to it, why the connection is chat-only and manual, and how to run the photo-adjacent workflow — filing, attaching, reporting — on real triggers instead.
Why Google’s API limits shape everything first
Before Claude enters the picture, Google decided what any assistant can do. As of March 31, 2025, the photoslibrary.readonly, photoslibrary.sharing, and broad photoslibrary scopes were removed. API calls that relied on them return 403 PERMISSION_DENIED. Two paths survive:
- App-created data only. The Library API still works, but an app can list, search, and retrieve only the albums and media items it created. It cannot browse your 40,000-photo lifetime library.
- The Picker API. To reach anything else, the user opens a picker and manually selects the photos or album to share for that session. Nothing is ambient; every batch is a deliberate hand-off.
So no integration — Claude, Gemini, or otherwise — gets standing access to your full Google Photos library anymore. That’s a Google policy ceiling, not a Claude limitation.
The only bridge is a community MCP server
Google Photos is not in Claude’s connector directory, and Google has not shipped an official MCP server for it (unlike its Drive and Workspace MCP servers). What exists is community work — for example the open-source google-photos-mcp project, built on the surviving Picker API — plus general connectors through platforms like Composio.
A community MCP means you self-host: clone the repo, run it on Node locally next to Claude Desktop, register your own Google Cloud OAuth credentials, and add it as a custom connector. Practically, once wired up you can ask Claude to:
- “List the albums this tool created and show what’s in the July client shoot.”
- “From the photos I just picked, which were taken on the same day?”
- “Pull these three selected images into a doc I’m drafting.”
Useful, but notice the shape: every request works against media you already handed it through the picker, or media the app itself uploaded. There’s no “find every photo of the whiteboard from last quarter” across your real library — the API won’t answer that anymore.
Why the connection stays chat-only and manual
You’re the trigger, every time. A community MCP server, like every Claude connector, only acts inside a chat you open. Claude has no event triggers and no schedules. A new album shared to you on Saturday, a batch of event photos uploaded Friday night — Claude notices none of it until you start a conversation and re-pick the files.
The picker resets the work. Because standing library access is gone, most useful requests start with you manually selecting photos through Google’s picker. That’s fine for a one-off (“summarize what’s in these”), but it makes a repeating, hands-off workflow impossible by design.
Self-hosting is on you. No directory listing means no OAuth screen Google maintains for you. You run the server, rotate the credentials, and keep it patched. And custom connectors in Claude require a paid Claude plan.
The net: Claude is a capable desk-side helper for “help me sort through the photos I just handed you,” and structurally unable to be the thing that reacts when new media shows up.
Where the real automation lives: Carly
Because Google locked the raw library down for everyone, the durable automation isn’t inside Google Photos at all — it’s the workflow around the images: filing them, attaching them to a report, emailing them to a client, logging them. Carly — an AI executive assistant that runs on triggers, in the cloud — handles that half:
- A photographer at Airbnb drops a new listing shoot into a shared Google Drive folder → Carly attaches the images to the weekly listings doc in Google Docs and emails the host the proof set. Overnight, laptop shut.
- A field team at Toast uploads install photos → Carly files them into the right client folder, updates the project record, and posts a summary in Slack.
- You describe it once in plain English — “when new photos land in this Drive folder, attach them to the report and send it” — and Carly interviews you, then builds the workflow. Nothing to self-host, no OAuth credentials to babysit.
Carly is bound by the same Google API ceiling as everyone else, so it works through Drive, Docs, and email where those give reliable, trigger-friendly access — rather than pretending it has library access Google no longer grants. AI agents start at $35/month, and workflow steps that don’t use AI run free and unlimited. See the Google Photos integration page and the full integrations list.
Side by side
| Claude + Google Photos MCP | Carly | |
|---|---|---|
| Official one-click connector | No (community MCP only) | Managed setup |
| Full library access | No (Google API restricts to app-created / picked media) | No (same Google ceiling) |
| Search/organize photos you hand it | Yes | Yes |
| Reacts when new photos are uploaded or shared | No | Yes, on triggers |
| File photos into a doc / email them automatically | No | Yes |
| Runs overnight with your laptop shut | No | Yes (cloud) |
| Setup | Self-host MCP + paid Claude plan | Plain-English interview |
Frequently Asked Questions
Does Claude integrate with Google Photos?
Not officially. Google Photos is not in Claude’s connector directory and Google has not published an MCP server for it. The only route as of mid-2026 is a community-built MCP server you self-host (for example google-photos-mcp) or a connector through a platform like Composio — both bound by Google’s API limits.
Can Claude see my entire Google Photos library?
No, and neither can any tool. Since March 31, 2025 Google restricts apps to media they created themselves or media you manually select through the Picker API each session. The broad read scopes were removed and return 403 PERMISSION_DENIED.
Why does connecting Google Photos to Claude feel so limited?
Because the limit is Google’s, not Claude’s. The Library API deprecation ended deep third-party access, so every request either works against app-created albums or starts with you hand-picking photos through the picker. There’s no ambient, whole-library search anymore.
Will Claude organize new photos as they come in?
Only if you open a chat and re-select them. Claude connectors have no event triggers or schedules, so a fresh upload or shared album sits untouched until your next conversation. For upload-triggered filing and reporting, use a trigger-based agent like Carly.
What does an automated photo workflow cost with Carly?
AI agents start at $35/month, and steps in a workflow that don’t use AI — moving files, attaching them, sending a report — run free and unlimited.
More: Claude connectors · Can Claude send emails · Claude vs Carly · Claude Cowork alternatives · Best AI email tools · Claude + Adobe · Claude + Missive · Claude + Mem
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
