oto.photo MCP server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@oto.photo MCP server Show my bookings for next week"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
oto.photo MCP server for ChatGPT and Claude
oto.photo publishes no public API or official MCP server, checked 15 November 2026. Cotlet.dev connects ChatGPT, Claude and other AI agents to your own signed-in oto.photo account.
Source: oto.photo integration page.
What can your AI agent do?
The live page describes 10 hosted tools, with 5 reads and 5 writes:
Area | Read | Write |
Galleries |
|
|
Bookings |
|
|
Clients |
|
|
Certificates |
|
|
Portfolio |
|
|
Four write tools ask for confirmation by default; you can change this per tool. Private client-list updates run immediately. Read tools run immediately.
Encrypted albums stay closed. Photo uploads, deletions, your oto.photo subscription and your Google account stay outside these tools. The tools return gallery links and certificate pages; sending them to clients stays with you.
Related MCP server: Pixieset MCP Server
What can I ask?
List the favourites my client picked in the autumn family album.
Show my bookings for next week.
Prepare a new session with the date, price and deposit I provide, and ask before saving.
List clients with birthdays in the next month.
Group the wedding albums in one folder and ask before creating the gallery link.
Show my valid gift certificates.
Connect ChatGPT and Claude
Enable oto.photo in the console and sign in at
https://oto.photo/authin your Cotlet.dev Cloud Browser with your Google account.In ChatGPT, add
https://cotlet.dev/mcp/v1/connectin Settings > Apps & Connectors, with OAuth.In Claude, add the same URL in Settings > Connectors > Add custom connector.
Connect Codex and Claude Code
Create an API key in your Cotlet.dev console and set COTLET_API_KEY in your environment.
Codex:
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"Claude Code:
claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"Optional local MCP wrapper
Python 3.10+, standard library only. This repository provides seven generic browser helpers over the hosted Cotlet.dev tools: oto_photo_guide, oto_photo_status, oto_photo_open, oto_photo_read, oto_photo_click, oto_photo_type, oto_photo_close.
These helpers are separate from the 10 hosted business tools above. Listing helpers requires no key; calling them requires COTLET_API_KEY.
export COTLET_API_KEY="your-key"
python3 oto_photo_agent.py serveFor a local-only MCP client, use an absolute path:
{"mcpServers":{"oto-photo":{"command":"python3","args":["/absolute/path/to/oto_photo_agent.py","serve"],"env":{"COTLET_API_KEY":"your-key"}}}}Other commands: connect, status, guide, read, tools.
The read command opens the browser, reads the page and closes the browser session.
Questions
Does oto.photo have a public API or official MCP server?
The Cotlet.dev integration page reports no public API, developer documentation, API keys, official MCP server or official ChatGPT or Claude connector, checked 15 November 2026.
Can the agent upload photos or open encrypted albums?
No. Uploads stay with you. Encrypted albums stay closed to the agent.
Does the agent send messages to clients?
No. It returns gallery links, certificate pages and birthday lists. You send them yourself.
Is this official?
No. Cotlet.dev is independent and is not affiliated with oto.photo.
Access and control
Use your own oto.photo account. Disable oto.photo for agents, reset the browser or sign out of Google sessions in your Google account to revoke access. You complete Google sign-in and any two-step check yourself. Cotlet.dev is independent and is not affiliated with oto.photo.
Available Tools
7 toolsoto_photo_clickC
Click a numbered element on the current oto.photo page.
Inputs: element (required).
oto_photo_closeA
Close the oto.photo browser session when the work is done, so credits stop running.
Inputs: no named parameters.
oto_photo_guideA
How to work in oto.photo (organise galleries, bookings, clients, gift certificates and portfolio albums): its screens and the sign-in link. Call this first.
Inputs: task.
oto_photo_openB
Open a oto.photo page in your signed-in Cloud Browser (default https://oto.photo/auth) to work with organise galleries, bookings, clients, gift certificates and portfolio albums.
Inputs: url.
oto_photo_readA
Read the current oto.photo page: its text and numbered buttons, links and fields.
Inputs: element.
oto_photo_statusA
Check that your Cotlet.dev account and oto.photo are ready: account, credits and oto.photo connection.
Inputs: no named parameters.
oto_photo_typeB
Type text into a numbered field on the current oto.photo page.
Inputs: text (required), element (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
The core action tools (open, read, click, type, close) are clearly distinct, and guide vs status are separated by their descriptions (instructions vs account/credit check). There is mild conceptual overlap between read, guide and status as all returning information, but the descriptions resolve it.
Every tool follows the same oto_photo_<verb> snake_case pattern with short, concrete verbs. No mixed conventions or vague naming.
Seven tools is well-scoped for a browser-driven site controller: session lifecycle, page inspection, and two input primitives plus help/status. Each tool earns its place with no redundancy.
The basic interaction loop (open, read, click, type, close) plus guide/status is covered, but there is no scrolling, navigation/back, waiting for loads, or dropdown/checkbox handling, which are likely needed for gallery, booking and client workflows. Photo/album management arguably also implies upload/delete affordances not present.
Related MCP Connectors
ShootProof MCP server for ChatGPT, Claude and any AI agent: create gallery, share gallery, list orders, send contract and send invoice in your own ShootProof account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to ShootProof yourself; Cotlet does not store your password and you need no ShootProof API key. About the official ShootProof API: ShootProof has a documented OAuth API that is free with an account, but you get a client ID only by emailing ShootProof support with your app details (checked 8 Nov 2026). There is no self-service key and no official MCP server. Setup and FAQ: https://cotlet.dev/integrations/shootproof-api-mcp-server
Pixieset MCP server for ChatGPT, Claude and any AI agent: create gallery, upload photos, send invoice, list bookings and add client in your own Pixieset account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Pixieset yourself; Cotlet does not store your password and you need no Pixieset API key. About the official Pixieset API: Pixieset has no public API, no webhooks and no Zapier app (checked 11 Oct 2026). Its Apps & Plugins page lists the Lightroom plugin, the Studio Manager mobile app and Photo Editor, and no developer program. Setup and FAQ: https://cotlet.dev/integrations/pixieset-api-mcp-server
PhotoShelter MCP server for ChatGPT, Claude and any AI agent: create gallery, share gallery, search images, update captions and keywords and set gallery access in your own PhotoShelter account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to PhotoShelter yourself; Cotlet does not store your password and you need no PhotoShelter API key. About the official PhotoShelter API: PhotoShelter publishes API documentation, but customers contact support to get an API key instead of generating one (checked 8 Nov 2026). There are no self-service keys and no official MCP server. Setup and FAQ: https://cotlet.dev/integrations/photoshelter-api-mcp-server
Studio Ninja MCP server for ChatGPT, Claude and any AI agent: add lead, book job, send invoice, send contract and list overdue payments in your own Studio Ninja account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Studio Ninja yourself; Cotlet does not store your password and you need no Studio Ninja API key. About the official Studio Ninja API: Studio Ninja publishes no public API, webhooks or Zapier app; it connects only to built-in partners such as Xero, QuickBooks, Stripe and Pic-Time (checked 8 Nov 2026). It has no official MCP server. Setup and FAQ: https://cotlet.dev/integrations/studio-ninja-api-mcp-server
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables AI agents to manage a user's own SmugMug account in plain language — creating and securing galleries, auditing visits, renaming and organizing photos, and applying price lists — without needing a SmugMug API key, OAuth setup, or code.795 PyPIElastic 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to operate a user's signed-in Pixieset account through natural language, including delivering galleries, booking sessions, sending contracts and invoices, and following up with clients without requiring a Pixieset API key.7379 PyPIElastic 2.0
- AlicenseAqualityBmaintenanceEnables ChatGPT, Claude, and other AI agents to read and manage clients, photography sessions, contracts, and invoices in a signed-in Iris Works account, including creating drafts and saving changes only after user approval.7Elastic 2.0
- AlicenseNot gradedqualityCmaintenanceEnables ChatGPT, Claude, and AI agents to read Salonized appointments, customers, waiting list, notes, and sales reports, while requiring approval before writes or customer notifications.Elastic 2.0