Invoicing & freelance CRM
Pixieset
Galleries, clients, invoices and bookings in your Pixieset studio.
13 endpoints
oto.photo publishes no public API and no MCP server (checked 15 Nov 2026). Cotlet runs a hosted oto.photo MCP server with 10 tools that ChatGPT and Claude use in your own oto.photo account. New sessions, gallery links, gift certificates and portfolio changes wait for your OK.
10 tools Read and write
oto.photo publishes no public API, no developer documentation and no API keys. No oto.photo MCP server and no official ChatGPT or Claude connector was found.
| What you need | oto.photo API | By hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude about your shoots | No API or MCP server | Copy and paste | Hosted MCP server |
| Galleries, sessions, clients, certificates | Not available | One screen at a time | 10 tools, public changes after your OK |
| A Monday list of birthdays from n8n | Not available | On the dashboard, when you look | REST, same key |
Checked 15 Nov 2026. Sources: oto.photo home · oto.photo llms.txt · oto.photo pricing · Client galleries · Client list · Booking calendar · Gift certificates · Portfolio
Once, with Google, in a browser we host.
One address in its settings.
Favourites, bookings, gallery links.
Your agent works in your own signed-in Cloud Browser. Anything clients or the public can see, a new session, a gallery link, a certificate or a portfolio album, waits for your OK. Who can see your session
Sign in to oto.photo in a Cloud Browser. Open oto.photo/auth in your Cotlet Cloud Browser and continue with the Google account you use for oto.photo.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
oto.photo is served from the shared address https://cotlet.dev/mcp/v1, as are the other apps you turn on, so one connector reaches them all. Turned oto.photo on later? Refresh the connector for its 10 tools.
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" // ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: oto_photo_read A read and a write for each part of oto.photo. Reads run at once; writes that clients or the public can see ask first.
Albums, folders and the favourites clients pick. Encrypted albums stay closed to the agent.
Each shoot is an album; folders group related albums behind one link. For one album the tool returns the photos the client marked as favourites, the same list oto.photo exports for Lightroom. Encrypted albums stay closed: they open only with the password you set in your own browser. Read only.
MCP calloto_photo_read → view_client_galleries
REST endpointGET https://cotlet.dev/api/v1/oto-photo/client-galleries/view
| Name | Type | Description |
|---|---|---|
| album string | string | Album or folder name. Leave empty to list them all. |
| client string | string | Only albums linked to this client. |
{
"album": "Example Family, autumn session",
"client": "Example Family",
"photos": 186,
"favourites": 24,
"favourite_files": [
"IMG_0412.jpg",
"IMG_0419.jpg",
"IMG_0457.jpg"
],
"link": "https://oto.photo/a/example-link"
} Sessions with client, location, type, price and deposit, and the album delivered for each.
Returns each session with the album linked to it after the shoot, if any. oto.photo records the price and deposit but processes no money, so these are your own notes of what was agreed. Read only.
MCP calloto_photo_read → view_booking_calendar
REST endpointGET https://cotlet.dev/api/v1/oto-photo/booking-calendars/view
| Name | Type | Description |
|---|---|---|
| from string | string | ISO date. Defaults to today. |
| to string | string | ISO date. Defaults to 30 days after `from`. |
{
"sessions": [
{
"date": "2026-11-22",
"client": "Example Couple",
"type": "Engagement",
"location": "Riverside park",
"price": 300,
"deposit": 100,
"album": null
},
{
"date": "2026-11-29",
"client": "Example Family",
"type": "Family",
"location": "Studio",
"price": 180,
"deposit": 50,
"album": null
}
]
} Your public availability page shows days as free, partly booked or full, so a new session changes what clients see. Inquiries from that page still wait for your confirmation in oto.photo. The free plan allows 5 sessions a month; Pro and Max are unlimited. By default you confirm each call; you can switch that off for this tool.
MCP calloto_photo_write → manage_booking_calendar
REST endpointPOST https://cotlet.dev/api/v1/oto-photo/booking-calendar/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `create`, `update`, `link_album`. |
| date string | string | ISO date of the session. |
| client string | string | Client from view_client_list. |
| fields object | object | For `create` and `update`: location, session type, price and deposit. |
| album string | string | For `link_album`: the delivered album. |
{
"action": "create",
"date": "2026-11-22",
"client": "Example Couple",
"fields": {
"type": "Engagement",
"location": "Riverside park",
"price": 300,
"deposit": 100
}
} {
"date": "2026-11-22",
"client": "Example Couple",
"type": "Engagement",
"location": "Riverside park",
"price": 300,
"deposit": 100,
"saved": true
} Cards, tags, notes, birthdays and anniversaries. Your private workspace, so updates run without asking.
A client card holds contact details, past sessions, notes, tags and every gallery the client received. Read only.
MCP calloto_photo_read → view_client_list
REST endpointGET https://cotlet.dev/api/v1/oto-photo/client-lists/view
| Name | Type | Description |
|---|---|---|
| client string | string | Client name. Leave empty to list clients. |
| upcoming_days number | number | List birthdays and anniversaries in the next N days. oto.photo shows 30 days ahead on the dashboard. |
| tag string | string | Only clients with this session type tag, for example weddings. |
{
"upcoming": [
{
"client": "Example Family",
"occasion": "Birthday (child)",
"date": "2026-12-03",
"tags": [
"family"
]
},
{
"client": "Example Couple",
"occasion": "Wedding anniversary",
"date": "2026-12-10",
"tags": [
"weddings"
]
}
]
} The client list is your private workspace: clients never see it, and a change is put back with one more call. That is why this tool runs without asking. The free Hobby plan holds up to 20 clients; Pro and Max are unlimited.
MCP calloto_photo_write → update_client_list
REST endpointPATCH https://cotlet.dev/api/v1/oto-photo/client-list
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name. A new name adds a client. |
| fields object | object | Contact details, session type tags, notes, birthday or anniversary dates. |
{
"client": "client"
} {
"client": "Example Couple",
"tags": [
"weddings"
],
"anniversary": "2026-12-10",
"notes": "Liked the riverside location. Prefers golden hour.",
"saved": true
} Vouchers with a QR and public page, and the public page of your work at oto.photo/u/.
Status is what each certificate's public page shows: valid, redeemed or expired. Outstanding certificates stay on the list until redeemed, so gifts from December are not lost by summer. Read only.
MCP calloto_photo_read → view_gift_certificates
REST endpointGET https://cotlet.dev/api/v1/oto-photo/gift-certificates/view
| Name | Type | Description |
|---|---|---|
| status string | string | One of `valid`, `redeemed`, `expired`, `all`. Defaults to `valid`. |
{
"certificates": [
{
"code": "GIFT-7Q2K",
"for": "Family session",
"status": "valid",
"valid_until": "2027-06-30"
},
{
"code": "GIFT-3MZP",
"for": "Portrait session",
"status": "valid",
"valid_until": null
}
]
} A new certificate gets a public page anyone can open with its QR, and the QR comes as a print-ready PNG for the paper certificate. oto.photo does not sell certificates; you sell them as you do today. Redeeming marks it used against a calendar session, which the recipient sees on the public page. The free plan allows 3 active certificates. By default you confirm each call; you can switch that off for this tool.
MCP calloto_photo_write → create_gift_certificate
REST endpointPOST https://cotlet.dev/api/v1/oto-photo/gift-certificates
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `create`, `redeem`. |
| for string | string | For `create`: what the certificate is for, for example Family session. |
| valid_until string | string | For `create`: optional ISO date. Leave empty for no expiry. |
| code string | string | For `redeem`: the certificate code. |
| session string | string | For `redeem`: the session date in your calendar. |
{
"action": "action"
} {
"code": "GIFT-7Q2K",
"for": "Family session",
"valid_until": "2027-06-30",
"status": "valid",
"public_page": "https://oto.photo/g/example",
"qr_png": "https://oto.photo/g/example/qr.png"
} The portfolio lives at oto.photo/u/ followed by your handle and is free on every plan. Read only.
MCP calloto_photo_read → view_portfolio
REST endpointGET https://cotlet.dev/api/v1/oto-photo/portfolios/view
No parameters.
{
"url": "https://oto.photo/u/example-photographer",
"albums": [
"Example wedding",
"Autumn family sessions",
"Studio portraits"
]
} Client galleries stay private unless you add them to the portfolio, and the portfolio is public. So adding an album makes a client's photos public, and the agent names each album before it saves. By default you confirm each call; you can switch that off for this tool.
MCP calloto_photo_write → update_portfolio
REST endpointPATCH https://cotlet.dev/api/v1/oto-photo/portfolio
| Name | Type | Description |
|---|---|---|
| add_albums array | array | Albums to show. |
| remove_albums array | array | Albums to hide. |
| bio string | string | New bio text. |
{
"url": "https://oto.photo/u/example-photographer",
"albums": [
"Example wedding",
"Autumn family sessions",
"Studio portraits",
"Newborn minis"
],
"saved": true
} Your signed-in oto.photo browser profile, AES-256-GCM encrypted, in Finland. Never your Google password.
The 10 oto.photo tools. The session cookie stays in the Cloud Browser.
Your albums, calendar, client list, gift certificates and portfolio, as your oto.photo account shows them.
Encrypted albums, photo uploads and deletions, your plan and storage, and your Google account.
You continue with Google again yourself, in the same Cloud Browser.
Disable oto.photo for agents, reset the browser, or sign out of Google sessions in your Google account.
Cotlet never sees or stores your password. oto.photo signs you in with Google: you complete that sign-in yourself, including any two-step check, and the agent only uses the session it leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Cotlet watches the apps it serves and updates the oto.photo server when oto.photo changes its dashboard, so your agent keeps working without a change on your side.
The free Hobby plan has limits the tools respect: 5 calendar sessions a month, 20 clients and 3 active gift certificates. Pro and Max lift them.
If oto.photo signs you out, one click in the Cotlet console reopens the Cloud Browser so you can sign in again.
| Action | How to put it right |
|---|---|
| Client card, tags or notes | Call update_client_list again with the earlier values |
| Session details | Call manage_booking_calendar with the right date, place or price |
| Portfolio album added | Remove it with update_portfolio; it was public in between |
| Gallery link already sent | Your client has it: the link stays as long as the album does |
4 of the 5 write tools ask first: by default you confirm each call, and you can switch that off per tool. update_client_list runs at once because clients never see the list. The 5 read tools run at once too.
{
"name": "manage_booking_calendar",
"arguments": {
"action": "create",
"date": "2026-11-22",
"client": "Example Couple",
"fields": {
"type": "Engagement",
"location": "Riverside park",
"price": 300,
"deposit": 100
}
}
} curl -X POST https://cotlet.dev/api/v1/oto-photo/booking-calendar/manage \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"action":"create","date":"2026-11-22","client":"Example Couple","fields":{"type":"Engagement","location":"Riverside park","price":300,"deposit":100}}' {
"date": "2026-11-22",
"client": "Example Couple",
"type": "Engagement",
"location": "Riverside park",
"price": 300,
"deposit": 100,
"saved": true
} The example books an engagement shoot at $300 with a $100 deposit. oto.photo records both and charges nothing: payments stay between you and your client. A script or n8n flow can make the same call over REST at /api/v1/oto-photo with the same key and price, in JSON. Failed calls are free.
About $15 a monthfor a photographer with about a dozen shoots, 2,630 credits. Your oto.photo plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Calendar look-ups | 1 × 30 | 300 |
| New sessions with price and deposit | 2 × 15 | 300 |
| Gallery link and album linked to the session | 2 × 12 | 240 |
| Client favourites for retouching | 1 × 12 | 120 |
| Monday birthday and anniversary list | 1 × 4 | 40 |
| Gift certificates issued and checked | 1 × 9 | 90 |
| Portfolio refresh | 2 × 2 | 40 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 113 calls | 2,630 |
The smallest pack, 5,000 credits for $29, covers this month. Wedding season means more sessions and more calls.
Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, not measured customer usage.
| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |
Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.
| Option | What it does | Where it stops |
|---|---|---|
| oto.photo dashboard | Albums, calendar, clients, certificates and portfolio, with birthdays shown 30 days ahead. | You open it and click through yourself. |
| Lightroom favourites export | Exports the photos a client picked as a list for Lightroom. | One album at a time, by hand. |
| oto.photo llms.txt | Tells AI assistants what oto.photo is and costs. | Public product facts only, nothing from your account. |
If oto.photo publishes an API that covers your job, use it: it is the vendor's own route. Cotlet fits when you want ChatGPT, Claude or a script working in oto.photo today, from your own sign-in, with nothing to host.
Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the oto.photo tools.
Sign up free at https://cotlet.dev/signup?app=oto-photo, turn on oto.photo under Integrations in the console and sign in at https://oto.photo/auth in your Cloud Browser. Then connect your AI agent and ask it what is booked this month. The trial needs no card.
oto.photo publishes no public API, developer documentation or API keys (checked 15 Nov 2026). No oto.photo MCP server and no official ChatGPT or Claude connector was found; its llms.txt describes the product only. Cotlet does not need one: it works in your own signed-in oto.photo account.
No. oto.photo encrypts those photos in your browser with a password you choose, before upload, and they open only with that password. Cotlet does not have it, so the agent sees that the album exists and nothing inside it.
No. Uploading a shoot stays with you. The tools organise what is already in oto.photo: albums into folders, sessions, clients, gift certificates and the portfolio.
No. The tools return gallery links, certificate pages and birthday lists; sending them stays with you, by messenger, email or SMS as you do today.
Only in how it is called. Both carry the same 10 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
No. Cotlet is independent and not affiliated with oto.photo.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy