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

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
oto.photo logo oto.photo Cloud Browser

10 tools Read and write

Photography studio

What can your AI agent do in oto.photo? The admin between the shoot and the delivery.

  • 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

No API, no MCP

Does oto.photo have an MCP server or an API? The official oto.photo routes, checked 15 November 2026.

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 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.
Doing it by hand and Cotlet compared
What you need oto.photo APIBy handCotlet
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

Set up once

How does the oto.photo MCP server work? The oto.photo MCP server by Cotlet: your agent works in your own oto.photo account.

  1. 1Sign in to oto.photo

    Once, with Google, in a browser we host.

  2. 2Connect your AI agent

    One address in its settings.

  3. 3Ask 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. Who can see your session

Any MCP client

How to connect oto.photo to your AI agent

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

    Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.

  3. 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
5 read, 5 write

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 galleries2

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

  • view_client_galleries List your albums and folders, or read one album with the favourites the client picked. read

    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

    Parameters

    Parameters: view_client_galleries
    NameTypeDescription
    album string string Album or folder name. Leave empty to list them all.
    client string string Only albums linked to this client.

    Example response

    {
      "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"
    }

Booking calendar2

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

  • view_booking_calendar List sessions for a period with client, location, session type, price and deposit. read

    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

    Parameters

    Parameters: view_booking_calendar
    NameTypeDescription
    from string string ISO date. Defaults to today.
    to string string ISO date. Defaults to 30 days after `from`.

    Example response

    {
      "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
        }
      ]
    }
  • manage_booking_calendar Add or change a session, or link the delivered album to it. writeAsks first

    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

    Parameters

    Parameters: manage_booking_calendar
    NameTypeDescription
    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.

    Example input

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

    Example response

    {
      "date": "2026-11-22",
      "client": "Example Couple",
      "type": "Engagement",
      "location": "Riverside park",
      "price": 300,
      "deposit": 100,
      "saved": true
    }

Client list2

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

  • view_client_list Read a client card, or list clients with birthdays and anniversaries coming up. read

    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

    Parameters

    Parameters: view_client_list
    NameTypeDescription
    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.

    Example response

    {
      "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"
          ]
        }
      ]
    }
  • update_client_list Add a client, or change contact details, tags, notes, birthdays or anniversaries. write

    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

    Parameters

    Parameters: update_client_list
    NameTypeDescription
    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.

    Example input

    {
      "client": "client"
    }

    Example response

    {
      "client": "Example Couple",
      "tags": [
        "weddings"
      ],
      "anniversary": "2026-12-10",
      "notes": "Liked the riverside location. Prefers golden hour.",
      "saved": true
    }

Gift certificates and portfolio4

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

  • view_gift_certificates List gift certificates with code, status and validity date. read

    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

    Parameters

    Parameters: view_gift_certificates
    NameTypeDescription
    status string string One of `valid`, `redeemed`, `expired`, `all`. Defaults to `valid`.

    Example response

    {
      "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
        }
      ]
    }
  • create_gift_certificate Issue a gift certificate with its code, QR and public page, or redeem one against a session. writeAsks first

    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

    Parameters

    Parameters: create_gift_certificate
    NameTypeDescription
    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.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "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"
    }
  • view_portfolio Read your portfolio page: handle, bio, contacts and the albums it shows. read

    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

    Parameters

    No parameters.

    Example response

    {
      "url": "https://oto.photo/u/example-photographer",
      "albums": [
        "Example wedding",
        "Autumn family sessions",
        "Studio portraits"
      ]
    }
  • update_portfolio Choose which albums your portfolio page shows, or change its bio and contacts. writeAsks first

    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

    Parameters

    Parameters: update_portfolio
    NameTypeDescription
    add_albums array array Albums to show.
    remove_albums array array Albums to hide.
    bio string string New bio text.

    Example response

    {
      "url": "https://oto.photo/u/example-photographer",
      "albums": [
        "Example wedding",
        "Autumn family sessions",
        "Studio portraits",
        "Newborn minis"
      ],
      "saved": true
    }
Encrypted, revocable

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

We keep it working

What happens when oto.photo changes? oto.photo keeps a public changelog of what it adds.

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.

4 tools ask first

Approvals, undo and mistakes Nothing new reaches a client or the public until you say so.

  1. 01 Find the client view_client_list reads the card.
  2. 02 Check the day view_booking_calendar lists that week.
  3. 03 Show you the session Date, place, price and deposit, before saving.
  4. 04 Save after your OK manage_booking_calendar adds it; the public page updates.
Fixing an oto.photo write that went wrong
ActionHow to put it right
Client card, tags or notesCall update_client_list again with the earlier values
Session detailsCall manage_booking_calendar with the right date, place or price
Portfolio album addedRemove it with update_portfolio; it was public in between
Gallery link already sentYour 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.

Pay per call

How much does the oto.photo MCP server cost?

About $15 a monthfor a photographer with about a dozen shoots, 2,630 credits. Your oto.photo plan stays as it is.

Illustrative month, our assumption: successful calls for this workload
JobCallsCredits
Calendar look-ups1 × 30300
New sessions with price and deposit2 × 15300
Gallery link and album linked to the session2 × 12240
Client favourites for retouching1 × 12120
Monday birthday and anniversary list1 × 440
Gift certificates issued and checked1 × 990
Portfolio refresh2 × 240
Cloud Browser, 30 days1,500
Total113 calls2,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.

Cotlet credit packs: price, credits and calls at 10 credits each
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.

Other options

oto.photo MCP server: other ways to connect What each route does for a working photographer, and where it stops.

Other ways to work with oto.photo, checked 15 Nov 2026
OptionWhat it doesWhere it stops
oto.photo dashboardAlbums, calendar, clients, certificates and portfolio, with birthdays shown 30 days ahead.You open it and click through yourself.
Lightroom favourites exportExports the photos a client picked as a list for Lightroom.One album at a time, by hand.
oto.photo llms.txtTells 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.

EU company, since 2019

Who runs Cotlet A company you can look up.

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.

Hand your next booking to your agent.

Free 7-day trial with 2,000 credits, no card needed.