How to connect Google Photos to Grok Bot
Connect Google Photos to Grok Bot with ClawLink in one click — 10 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
Google PhotosOAUTH2MCPUpload, search, and manage photos and albums in Google Photos. Once connected, Grok Bot can read and act on Google Photos from chat — pairing, token refresh, and tool wiring handled for you.
Grok Bot runs on its own cloud computer, so most Google Photos guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Google Photos setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Google Photos actions from chat with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into Grok Bot. It runs the ClawLink CLI in its own terminal and pairs your account.
Set up ClawLink for me and tell me when it's ready.
1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait:
npx -y @useclawlink/cli login
2. I'll approve it in my browser, then reply "approved".
3. When I say approved, connect the app:
npx -y @useclawlink/cli connect googlephotos
4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready.Setup
It takes three steps to connect Grok Bot to Google Photos.
1Pair from the terminal
Ask Grok Bot to run the ClawLink CLI. It prints a link you approve once in your browser:
npx -y @useclawlink/cli login- 2
Connect Google Photos
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask Grok Bot: "What can you do with Google Photos?"
Install by command
The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval:
npx -y @useclawlink/cli login # prints an approval link, approve it in your browser
npx -y @useclawlink/cli connect googlephotosPair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add https://claw-link.dev/api/mcp as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI.
Verify the connection by asking Grok Bot:
Use Google Photos to add enrichment and walk me through the result in plain English.
Using a different agent?
The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Google Photos is connected in the dashboard, that agent calls the same 10 Google Photos tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Google Photos MCP for Grok Bot
Looking for a Google Photos MCP server for Grok Bot? ClawLink connects Google Photos to Grok Bot and exposes 10 Google Photos tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using a different agent? The OpenClaw Google Photos integration and the Hermes Google Photos integration connect the same ClawLink account the same way.
What the Grok Bot Google Photos integration can do
10 Google Photos tools are ready for Grok Bot once the account is connected.
All 10 Google Photos tools for Grok Bot
| Tool | What it does |
|---|---|
Add enrichment googlephotos_add_enrichment | Adds an enrichment at a specified position in a defined album. |
Batch add media items googlephotos_batch_add_media_items | Adds one or more media items to an album in Google Photos. |
Batch get media items googlephotos_batch_get_media_items | Returns the list of media items for the specified media item identifiers. |
Get album googlephotos_get_album | Returns the album based on the specified albumId. |
Get media item download googlephotos_get_media_item_download | Downloads a media item from Google Photos and returns it as a file. |
List albums googlephotos_list_albums | Lists all albums shown to a user in the Albums tab of Google Photos. |
List media items googlephotos_list_media_items | Lists media items created by this application from Google Photos. |
Search media items googlephotos_search_media_items | Searches for media items in a user's Google Photos library. |
Update album googlephotos_update_album | Updates an album's title or cover photo in Google Photos. |
Update media item googlephotos_update_media_item | Updates a media item's description in Google Photos. |
Try it: find the Google Photos tool you need
Browse the 10 Google Photos tools
Click any tool to see exactly what Grok Bot can do and copy a ready-to-use prompt.
Example prompts
Use Google Photos to add enrichment and walk me through the result in plain English.
Use Google Photos to batch add media items and walk me through the result in plain English.
Use Google Photos to batch get media items and walk me through the result in plain English.
Pull the relevant data from Google Photos, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Google Photos working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Google Photos app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Google Photos through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Google Photos. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Google Photos actions to the runtime in a format your agent can reliably use. | 10 tools for Google Photos are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Google Photos to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Grok Bot users instead. You install the plugin once, connect Google Photos in the browser, and the 10 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
Grok Bot says it cannot add ClawLink as an MCP server
Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run npx -y @useclawlink/cli login in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add https://claw-link.dev/api/mcp as a custom connector at grok.com/connectors and approve the ClawLink sign-in.
Connection succeeds but no tools appear
Reconnect Google Photos from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Google Photos tools
Google Photos tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Google Photos call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Google Photos returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
OAuth finished in the browser but the account is still missing
Try reconnecting Google Photos and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a Grok Bot Google Photos integration?
Yes. ClawLink is the fastest way to connect Grok Bot to Google Photos: link your Google Photos account once in the browser and Grok Bot can call the Google Photos API through 10 ready-made tools — no custom code or token handling.
How do I connect Google Photos to Grok Bot with ClawLink?
Ask Grok Bot to run npx -y @useclawlink/cli login in its terminal and approve the link it prints, then npx -y @useclawlink/cli connect googlephotos to authorize Google Photos. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files or API keys to manage.
How long does it take to connect Google Photos to Grok Bot?
About two minutes. Sign in, click Connect next to Google Photos in the dashboard, authenticate, and Grok Bot can use it from the next chat message.
Why use ClawLink instead of wiring Google Photos up myself?
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Google Photos working from chat.
Grok Bot says it cannot add ClawLink as an MCP server
Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run npx -y @useclawlink/cli login in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add https://claw-link.dev/api/mcp as a custom connector at grok.com/connectors and approve the ClawLink sign-in.
