[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# oto.photo API and MCP server: Let your AI agent keep the studio admin moving.

> 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.

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.

- Free 7-day trial, no card
- Unofficial, not affiliated with oto.photo
- Page: https://cotlet.dev/integrations/oto-photo-api-mcp-server

## What can your AI agent do in oto.photo?

- Pull a client's favourites for Lightroom
- Book a session with price and deposit
- Share a wedding in one folder link
- List birthdays and anniversaries ahead
- Issue and redeem gift certificates
- Add recent work to the portfolio

## Does oto.photo have an MCP server or an API?

- oto.photo publishes an llms.txt that describes the product for AI readers; it exposes nothing from your account.
- Every plan has every tool. Hobby is free with 2 GB; Pro is $7 a month for 200 GB and Max $14 for 500 GB.
- The interface is in English and Ukrainian, and clients never need an account to view or download a gallery.

| 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](https://oto.photo/), [oto.photo llms.txt](https://oto.photo/llms.txt), [oto.photo pricing](https://oto.photo/pricing), [Client galleries](https://oto.photo/client-galleries), [Client list](https://oto.photo/client-crm), [Booking calendar](https://oto.photo/booking-calendar), [Gift certificates](https://oto.photo/gift-certificates), [Portfolio](https://oto.photo/portfolio)

## How does the oto.photo MCP server work?

1. **Sign in to oto.photo.** Once, with Google, in a browser we host.
2. **Connect your AI agent.** One address in its settings.
3. **Ask for the next admin job.** 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.

## How to connect oto.photo to your AI agent

1. **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.
2. **Add the Cotlet address.** Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
3. **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.

ChatGPT:

```
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
```

Claude:

```
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:

```
// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}
```

Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

n8n:

```
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: oto_photo_read
```

## All 10 oto.photo MCP tools

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.

### Client galleries

Albums, folders and the favourites clients pick. Encrypted albums stay closed to the agent.

- **View client galleries** (`view_client_galleries`, read): List your albums and folders, or read one album with the favourites the client picked.
- **Share a client gallery** (`share_client_gallery`, write, asks first): Group albums into a folder and get the one link to send your client.

### Booking calendar

Sessions with client, location, type, price and deposit, and the album delivered for each.

- **View booking calendar** (`view_booking_calendar`, read): List sessions for a period with client, location, session type, price and deposit.
- **Manage booking calendar** (`manage_booking_calendar`, write, asks first): Add or change a session, or link the delivered album to it.

### Client list

Cards, tags, notes, birthdays and anniversaries. Your private workspace, so updates run without asking.

- **View client list** (`view_client_list`, read): Read a client card, or list clients with birthdays and anniversaries coming up.
- **Update client list** (`update_client_list`, write): Add a client, or change contact details, tags, notes, birthdays or anniversaries.

### Gift certificates and portfolio

Vouchers with a QR and public page, and the public page of your work at oto.photo/u/.

- **View gift certificates** (`view_gift_certificates`, read): List gift certificates with code, status and validity date.
- **Create a gift certificate** (`create_gift_certificate`, write, asks first): Issue a gift certificate with its code, QR and public page, or redeem one against a session.
- **View portfolio** (`view_portfolio`, read): Read your portfolio page: handle, bio, contacts and the albums it shows.
- **Update portfolio** (`update_portfolio`, write, asks first): Choose which albums your portfolio page shows, or change its bio and contacts.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/oto-photo-api-mcp-server#tools

## Who can see my oto.photo session, and how do I revoke it?

- **What we store.** Your signed-in oto.photo browser profile, AES-256-GCM encrypted, in Finland. Never your Google password.
- **What your agent gets.** The 10 oto.photo tools. The session cookie stays in the Cloud Browser.
- **What the session sees.** Your albums, calendar, client list, gift certificates and portfolio, as your oto.photo account shows them.
- **What no tool touches.** Encrypted albums, photo uploads and deletions, your plan and storage, and your Google account.
- **If oto.photo signs you out.** You continue with Google again yourself, in the same Cloud Browser.
- **How to cut access.** 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](https://cotlet.dev/security.md)).

## What happens when oto.photo changes?

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.

## Approvals, undo and mistakes

1. **Find the client.** view_client_list reads the card.
2. **Check the day.** view_booking_calendar lists that week.
3. **Show you the session.** Date, place, price and deposit, before saving.
4. **Save after your OK.** manage_booking_calendar adds it; the public page updates.

| 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.

MCP call:

```
{
  "name": "manage_booking_calendar",
  "arguments": {
    "action": "create",
    "date": "2026-11-22",
    "client": "Example Couple",
    "fields": {
      "type": "Engagement",
      "location": "Riverside park",
      "price": 300,
      "deposit": 100
    }
  }
}
```

REST:

```
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}}'
```

Response:

```
{
  "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.

## How much does the oto.photo MCP server cost?

**About $15 a month** for 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.

- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- oto.photo stays free on Hobby, or $7 and $14 a month for Pro and Max

Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, not measured customer usage.

## oto.photo MCP server: other ways to connect

| 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.

## Who runs Cotlet

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.

## oto.photo MCP server: questions

### How do I get access?

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.

### Does oto.photo have an API?

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.

### Can the agent open my encrypted albums?

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.

### Does the agent upload photos?

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.

### Does the agent message my clients?

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.

### Is the MCP server different from the REST API?

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.

### Is Cotlet affiliated with oto.photo?

No. Cotlet is independent and not affiliated with oto.photo.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.
