Pixifi API and MCP server Let your AI agent run the studio paperwork.

Pixifi publishes no public API documentation and no MCP server (checked 16 Nov 2026). Cotlet runs a hosted Pixifi MCP server with 38 tools that ChatGPT and Claude use in your own studio account. Proposals, contracts, invoices and anything else that reaches a client wait for your OK.

  • Free 7-day trial, no card
  • Unofficial, not affiliated with Pixifi

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Pixifi. Pixifi is a trademark of its owner. If Pixifi's own integrations cover what you need, use them first.

Pixifi Cloud Browser

38 tools Read and write

Studio office work

What can your AI agent do in Pixifi? The office side of a photography studio, from inquiry to final payment.

  • Turn an inquiry into a lead and a proposal

  • Send the event contract and questionnaire

  • Build the wedding day timeline and assign staff

  • Create and send event invoices

  • Chase open balances every Monday

  • Log expenses and mileage, read the P&L

Partner keys, no MCP

Does Pixifi have an MCP server or an API? The official Pixifi routes, checked 16 November 2026.

Pixifi publishes no public API documentation, and pixifi.com/api answers 404. In its 1 November 2023 webinar Pixifi described its API as bespoke, with keys issued to partner vendors. No Pixifi MCP server and no official ChatGPT or Claude connector was found.

  • Pixifi's pricing FAQ lists integrations with Zapier, ShootProof, MailChimp and Google Calendar.
  • Payments run through Square, Stripe and PayPal; Pixifi records them, the processor moves the money.
  • Pixifi has iOS and Android apps for the schedule, client information and invoices.
Pixifi's own routes, working by hand and Cotlet compared
What you need Pixifi APIBy handCotlet
Ask ChatGPT or Claude to do the work No MCP server found Copy and paste Hosted MCP server
Start today with your own login Keys for partner vendors Your login Your login, once
Proposals, contracts, invoices and payments No public endpoints One screen at a time 38 tools, writes after your OK
Run from n8n or a script No public docs Manual only REST, same key

Checked 16 Nov 2026. Sources: Pixifi pricing and FAQ · Pixifi webinar transcript, 1 Nov 2023 · Pixifi Academy · Academy: Add and edit a client · Academy: Manage your lead pipeline · Academy: Create and send a proposal · Academy: Contract for an event · Academy: Invoice for an event · Academy: Accounts Receivable · Academy: Refund a client · Academy: Assign staff to an event · Academy: Create a workshop

Set up once

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

  1. 1Log in to Pixifi

    Once, in a browser we host for you.

  2. 2Connect your AI agent

    One address in its settings.

  3. 3Hand it the studio office

    Draft the proposal, then approve it.

Your agent works in your own signed-in Cloud Browser. Writes, and anything that reaches a client, wait for your OK. Who can see your session

Any MCP client

How to connect Pixifi to your AI agent

  1. 1

    Sign in to Pixifi in a Cloud Browser. Open www.pixifi.com/admin in your Cotlet Cloud Browser and log in with your own Pixifi username.

  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.

Pixifi shares the address https://cotlet.dev/mcp/v1 with every other app you turn on, so one connector reaches all of them. Turned Pixifi on later? Refresh the connector and the 38 Pixifi tools show up.

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: view_accounts_receivable
4 read, 34 write

All 38 Pixifi MCP tools

One tool per owner workflow in Pixifi Academy. Many take an `action`: `list` and `get` only read, the other actions write and ask first.

Clients and leads8

Contacts > Clients and Leads. Moving a lead to a new status starts the automations you attached to that status.

  • filter_clients List Pixifi clients that match the filters you give. read

    Reads Contacts > Clients with Filter Options applied. Pixifi saves the filter you last used and shows it again next time you open the list, in the app too. It changes no client, so it runs without asking.

    MCP callpixifi_read → filter_clients

    REST endpointGET https://cotlet.dev/api/v1/pixifi/clients/filter

    Parameters

    Parameters: filter_clients
    NameTypeDescription
    filters object object Filter Options fields as Pixifi labels them, for example brand, category or created date. Leave empty to list all.

    Example response

    {
      "filters": {
        "category": "Wedding 2027"
      },
      "clients": [
        {
          "name": "Example Couple",
          "email": "couple@example.com",
          "category": "Wedding 2027"
        },
        {
          "name": "Sample Family",
          "email": "family@example.com",
          "category": "Wedding 2027"
        }
      ]
    }
  • manage_clients Read one client record, add a client or edit one. writeAsks first

    Follows Contacts > Clients > Actions. A record opens in View mode, where the common fields are editable; the Edit toggle shows the rest, events included. Fields you leave out stay as they are. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → manage_clients

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/clients/manage

    Parameters

    Parameters: manage_clients
    NameTypeDescription
    action string required string One of `get`, `create`, `update`. `list` and `get` only read.
    client string string Client name or ID, for `get` and `update`.
    quick boolean boolean For `create`: true for Add a Quick Client with the basic fields, false for the full Add a New Client form.
    fields object object For `create` and `update`: the client form fields in Pixifi's labels, such as name, email and phone.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "client": "Example Couple",
      "email": "couple@example.com",
      "phone": "+1 555 0142",
      "saved": true
    }
  • import_clients Import a client list from a .csv file into Pixifi. writeAsks first

    Runs Contacts > Clients > Actions > Import Clients, sets the brand, category and column mapping, then Import Data. The agent shows you the mapping first, because an import adds every row at once. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → import_clients

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/clients

    Parameters

    Parameters: import_clients
    NameTypeDescription
    file_url string required string Link the Cloud Browser can download the .csv from. Pixifi takes only .csv.
    brand string required string Brand the new clients are assigned to.
    category string string Category applied to every imported client, if any.
    columns object object Which .csv column fills which Pixifi client field.

    Example input

    {
      "file_url": "https://example.com",
      "brand": "brand"
    }

    Example response

    {
      "file": "clients-2026.csv",
      "brand": "Example Studio",
      "category": "Imported",
      "imported": 48
    }
  • share_client_portal Get a client's portal setup link or email it to them. writeAsks first

    Reads the Client Portal Setup URL under Additional Info on the client record; the client uses it to create their own login. With a template it sends the email from the client's Contact tab, which reaches your client. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → share_client_portal

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/client-portal/share

    Parameters

    Parameters: share_client_portal
    NameTypeDescription
    client string required string Client name or ID, as manage_clients or filter_clients returns it.
    send_with_template string string Email template of type Client that carries the Client Portal Setup URL. Leave empty to only return the link.

    Example input

    {
      "client": "client"
    }

    Example response

    {
      "client": "Example Couple",
      "portal_setup_url": "https://www.pixifi.com/portal/setup/example",
      "emailed": false
    }
  • manage_leads Read a lead, add one as a Quick Lead or a full lead, or edit it. writeAsks first

    Follows Contacts > Leads > Actions. Add New Lead takes more event and contact information than the Quick Lead form. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → manage_leads

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/leads/manage

    Parameters

    Parameters: manage_leads
    NameTypeDescription
    action string required string One of `get`, `create`, `update`. `list` and `get` only read.
    lead string string Lead name or ID, for `get` and `update`.
    quick boolean boolean For `create`: true for Add Quick Lead, false for Add New Lead with event and contact details.
    fields object object Lead fields in Pixifi's labels, such as name, email, event type and date.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "lead": "Sample Engagement",
      "email": "lead@example.com",
      "event_type": "Engagement",
      "event_date": "2027-05-15",
      "saved": true
    }
  • manage_lead_pipeline Read the Lead Pipeline by status, or move a lead to another status. writeAsks first

    Statuses, their names, colours and order are your own. Moving a lead starts any automation you attached to the new status at once, so the agent names that status before it moves the lead. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → manage_lead_pipeline

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/lead-pipeline/manage

    Parameters

    Parameters: manage_lead_pipeline
    NameTypeDescription
    action string required string One of `list`, `move`. `list` and `get` only read.
    lead string string Lead to move, for `move`.
    status string string Target status column, in your own status names.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "pipeline": [
        {
          "status": "New inquiry",
          "leads": 4
        },
        {
          "status": "Proposal sent",
          "leads": 2
        },
        {
          "status": "Booked",
          "leads": 1
        }
      ]
    }
  • share_lead Share a lead with a studio connected to yours. writeAsks first

    Runs Share Lead under Actions. Only studios set up under Settings > Sharing appear; an empty list means sharing is not set up. The lead reaches another business. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → share_lead

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/lead/share

    Parameters

    Parameters: share_lead
    NameTypeDescription
    lead string required string The lead to share.
    studio string required string Studio to share with, from your sharing connections.
    lead_type string required string Lead type from the other studio's list, not yours.

    Example input

    {
      "lead": "lead",
      "studio": "studio",
      "lead_type": "lead type"
    }

    Example response

    {
      "lead": "Sample Engagement",
      "studio": "Example Second Shooter Studio",
      "lead_type": "Engagement",
      "shared": true
    }
  • create_inquiry_form Build an inquiry form for a brand and return its link and embed code. writeAsks first

    Follows Settings > Brands > your brand > Inquiry > Create New Form. Returns the View link to share and the Embed snippet for your website. Leads that fill it in land in Pixifi. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → create_inquiry_form

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/inquiry-forms

    Parameters

    Parameters: create_inquiry_form
    NameTypeDescription
    brand string required string Brand the form belongs to.
    name string required string Form name.
    fields array required array Form fields in order, from the field list Pixifi offers.

    Example input

    {
      "brand": "brand",
      "name": "Jane Doe",
      "fields": "fields"
    }

    Example response

    {
      "brand": "Example Studio",
      "form": "Wedding inquiry",
      "view_url": "https://www.pixifi.com/forms/example",
      "embed": "<script src=\"...\">",
      "saved": true
    }

Booking pages, pricing pages and products4

What clients see and book on their own: services with time slots and prices, pricing pages with packages, and product templates.

  • manage_booking_pages List booking pages or add a service clients can book themselves. writeAsks first

    A booking page lets clients and leads pick a date and time for a service. The service settings decide who is scheduled, the price and tax, and which contract, event and invoice each booking creates. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → manage_booking_pages

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/booking-pages/manage

    Parameters

    Parameters: manage_booking_pages
    NameTypeDescription
    action string required string One of `list`, `get`, `create_service`. `list` and `get` only read.
    booking_page string string Booking page name.
    service object object For `create_service`: name, fixed time slots and duration, assigned staff, price and taxable, show as sold out when full, and the contract, event and invoice titles.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "booking_page": "Mini sessions",
      "service": "Fall mini session",
      "duration_minutes": 20,
      "price": 175,
      "staff": [
        "Owner"
      ],
      "saved": true
    }
  • set_service_availability Turn days on or off for a booking page service, with a time or price change. writeAsks first

    Uses Show Advanced Options on the service in Settings > Booking Pages. Clients see the change on the booking page at once. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → set_service_availability

    REST endpointPUT https://cotlet.dev/api/v1/pixifi/service-availability

    Parameters

    Parameters: set_service_availability
    NameTypeDescription
    booking_page string required string Booking page.
    service string required string Service on that page.
    days array required array Days with `available` true or false, and optional time and price difference. A negative price difference makes that day cheaper.

    Example input

    {
      "booking_page": "booking page",
      "service": "service",
      "days": "days"
    }

    Example response

    {
      "booking_page": "Mini sessions",
      "service": "Fall mini session",
      "days": [
        {
          "day": "Saturday",
          "available": true,
          "price_difference": 0
        },
        {
          "day": "Sunday",
          "available": true,
          "price_difference": -25
        }
      ],
      "saved": true
    }
  • manage_pricing_pages Create a pricing page and add packages, add-ons and services to it. writeAsks first

    Settings > Pricing Pages. Clients see the page at its URL as soon as it is saved. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → manage_pricing_pages

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/pricing-pages/manage

    Parameters

    Parameters: manage_pricing_pages
    NameTypeDescription
    action string required string One of `list`, `create`, `add_package`. `list` and `get` only read.
    page object object For `create`: page name, page URL, description and tax.
    pricing_page string string For `add_package`: the page.
    package object object For `add_package`: a package template, or a name and price.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "pricing_page": "Wedding collections",
      "url": "weddings",
      "packages": [
        {
          "name": "Half day",
          "price": 1900
        },
        {
          "name": "Full day",
          "price": 3200
        }
      ],
      "saved": true
    }
  • manage_product_templates List product and service templates or add one. writeAsks first

    Templates > Product & Service Templates > Product Templates. Images on a template show on your pricing, proposal and booking pages. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → manage_product_templates

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/product-templates/manage

    Parameters

    Parameters: manage_product_templates
    NameTypeDescription
    action string required string One of `list`, `create`. `list` and `get` only read.
    type string string Product type, for `create`.
    name string string Product name.
    price number number Price.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "template": "10x10 lay-flat album",
      "type": "Album",
      "price": 650,
      "saved": true
    }

Events and shoot days8

The calendar, staff and roles, wedding day timelines, reminders, workflows, locations and the miles you drive.

  • view_events Read events by day, week or listing, with filters and event stats. read

    Reads Things to Do > Events. Returns each event with date, type and client. It changes nothing and runs without asking.

    MCP callpixifi_read → view_events

    REST endpointGET https://cotlet.dev/api/v1/pixifi/events/view

    Parameters

    Parameters: view_events
    NameTypeDescription
    view string string `day`, `week` or `listing`. Default `listing`.
    filters object object Filter Options fields, such as date range, event type or status.
    stats boolean boolean True to add the Stats totals of the events found.

    Example response

    {
      "view": "listing",
      "events": [
        {
          "event": "Example Couple wedding",
          "type": "Wedding",
          "date": "2027-06-12"
        },
        {
          "event": "Sample Family portraits",
          "type": "Portrait",
          "date": "2026-11-22"
        }
      ]
    }
  • manage_events Read an event, add a Quick Event or a full one, or edit it. writeAsks first

    Pixifi adds events from Quick Actions, the Events calendar, listing or pipeline, a date on the calendar or the client record; the tool uses the same form. Settings you leave out can be edited later. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → manage_events

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/events/manage

    Parameters

    Parameters: manage_events
    NameTypeDescription
    action string required string One of `get`, `create`, `update`. `list` and `get` only read.
    event string string Event name or ID, for `get` and `update`.
    fields object object Event Name and Event Type are required for `create`; client, date, brand and the rest are optional.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "event": "Example Couple wedding",
      "event_type": "Wedding",
      "date": "2027-06-12",
      "client": "Example Couple",
      "saved": true
    }
  • assign_event_staff Assign a staff member to an event with a role. writeAsks first

    Runs Assign Staff on the event. On the Essential plan you can only assign yourself, so the call fails there for anyone else. After the assignment you can add contracts and questionnaires for that person in Pixifi. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → assign_event_staff

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/event-staff/assign

    Parameters

    Parameters: assign_event_staff
    NameTypeDescription
    event string required string Event name or ID, as view_events returns it.
    staff string required string Staff member. Pixifi shows whether they are free for the event.
    role string required string Staff role, for example Second shooter.
    auto_confirm boolean boolean False makes the staff member confirm their participation themselves.

    Example input

    {
      "event": "event",
      "staff": "staff",
      "role": "role"
    }

    Example response

    {
      "event": "Example Couple wedding",
      "staff": "Second Shooter A",
      "role": "Second shooter",
      "auto_confirm": false,
      "saved": true
    }
  • manage_timelines Create a timeline template or put a timeline on an event. writeAsks first

    Templates live in Things to Do > Timelines > Templates. `apply` adds the template, or the items you give, to the event's Timelines tab, where you can share it with your clients. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → manage_timelines

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/timelines/manage

    Parameters

    Parameters: manage_timelines
    NameTypeDescription
    action string required string One of `list_templates`, `create_template`, `apply`. `list` and `get` only read.
    template string string Timeline template name.
    items array array For `create_template`: timeline items with time and title.
    event string string For `apply`: the event that gets the timeline.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "event": "Example Couple wedding",
      "template": "Wedding day, 8 hours",
      "items": [
        {
          "time": "14:00",
          "title": "Getting ready"
        },
        {
          "time": "16:30",
          "title": "Ceremony"
        },
        {
          "time": "18:00",
          "title": "Family portraits"
        }
      ],
      "saved": true
    }
  • create_event_reminders Create an automated event reminder from your email templates. writeAsks first

    Adds a template under Events > Reminders. You then choose it when you create or edit an event, and from then on Pixifi emails your client on its own. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → create_event_reminders

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/event-reminders

    Parameters

    Parameters: create_event_reminders
    NameTypeDescription
    name string required string Reminder template name.
    reminders array required array Each reminder with the email template it sends and when.

    Example input

    {
      "name": "Jane Doe",
      "reminders": "reminders"
    }

    Example response

    {
      "reminder": "Session reminders",
      "reminders": [
        {
          "email_template": "Your session is next week",
          "when": "7 days before"
        },
        {
          "email_template": "See you tomorrow",
          "when": "1 day before"
        }
      ],
      "saved": true
    }
  • apply_event_workflow Apply a workflow template to an event. writeAsks first

    Runs Workflow > Apply Workflow on the event and saves it. The workflow's steps then run on that event as you set them up in Pixifi. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → apply_event_workflow

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/event-workflow/apply

    Parameters

    Parameters: apply_event_workflow
    NameTypeDescription
    event string required string Event name or ID, as view_events returns it.
    workflow string required string Workflow template to apply.

    Example input

    {
      "event": "event",
      "workflow": "workflow"
    }

    Example response

    {
      "event": "Example Couple wedding",
      "workflow": "Wedding client journey",
      "applied": true
    }
  • add_event_mileage Add mileage to an event, optionally as an expense, or read the mileage report. writeAsks first

    Uses Add Mileage on the event's Locations. A mileage expense shows under the event's Money. `list` reads Finances > Mileage, the report of all mileage you can export for your accounting. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → add_event_mileage

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/event-mileages

    Parameters

    Parameters: add_event_mileage
    NameTypeDescription
    action string required string One of `list`, `add`. `list` and `get` only read.
    event string string Event, for `add`.
    miles number number Distance driven.
    as_expense boolean boolean True to log it as an expense on the event as well.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "event": "Example Couple wedding",
      "miles": 46,
      "as_expense": true,
      "saved": true
    }
  • manage_locations List shoot locations, add one or import a .csv of them. writeAsks first

    Things to Do > Events > Locations. An import assigns a brand and maps the .csv columns to location fields, like the client import. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → manage_locations

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/locations/manage

    Parameters

    Parameters: manage_locations
    NameTypeDescription
    action string required string One of `list`, `add`, `import`. `list` and `get` only read.
    name string string Location Name, the one required field for `add`.
    fields object object Optional address and notes.
    file_url string string For `import`: the .csv to import.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "location": "Riverside Park gazebo",
      "saved": true
    }

Proposals, contracts and questionnaires5

Everything a client signs or fills in, and the templates behind it. Sending waits for your OK.

  • send_proposals Apply a proposal template to a lead or client and send it by email or SMS. writeAsks first

    A Pixifi proposal bundles a contract, booking page, package choices, add-ons and an invoice built from the payment terms. The agent applies the template, shows you what the client will see, then sends it. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → send_proposals

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/proposals

    Parameters

    Parameters: send_proposals
    NameTypeDescription
    recipient string required string Lead or client.
    template string required string Proposal template from Templates > Proposals.
    send_by string string `email`, `sms` or `none` to prepare it only.

    Example input

    {
      "recipient": "recipient",
      "template": "template"
    }

    Example response

    {
      "recipient": "Sample Engagement",
      "template": "Wedding collections",
      "send_by": "email",
      "sent": false
    }
  • send_event_contracts Create a contract for an event from a template and send it to the client. writeAsks first

    Runs Contracts > Create New Contract on the event. The event's brand fills in on its own. A sent contract reaches your client for signing. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → send_event_contracts

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/event-contracts

    Parameters

    Parameters: send_event_contracts
    NameTypeDescription
    event string required string Event name or ID, as view_events returns it.
    template string required string Contract template.
    invoice string string Invoice the contract refers to. Pixifi preselects the event's latest one.
    send boolean boolean True to send it to the client after saving.

    Example input

    {
      "event": "event",
      "template": "template"
    }

    Example response

    {
      "event": "Example Couple wedding",
      "contract": "Wedding contract 2027",
      "invoice": "INV-1042",
      "sent": false
    }
  • create_contract_templates List contract templates or add one with your contract text. writeAsks first

    Templates > Contract Templates. The agent pastes the wording you give; it does not write legal terms for you. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → create_contract_templates

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/contract-templates

    Parameters

    Parameters: create_contract_templates
    NameTypeDescription
    action string required string One of `list`, `create`, `update`. `list` and `get` only read.
    name string string Template name.
    type string string `Event` or `Project`. The type sets which variables the contract can use.
    body string string Your contract text, pasted in as you wrote it.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "template": "Wedding contract 2027",
      "type": "Event",
      "saved": true
    }
  • send_questionnaires Create a questionnaire template or send one to a lead or client. writeAsks first

    Templates live under Questionnaires in your template listing. Sending one reaches your client. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → send_questionnaires

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/questionnaires

    Parameters

    Parameters: send_questionnaires
    NameTypeDescription
    action string required string One of `list`, `create`, `send`. `list` and `get` only read.
    title string string Questionnaire title.
    questions array array For `create`: labels, text inputs, text areas and multiple choice questions, each optionally required.
    recipient string string For `send`: the lead or client.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "title": "Headshot portrait",
      "questions": 4,
      "recipient": "Sample Client",
      "sent": false
    }
  • manage_email_templates List email templates or add one with Pixifi variables. writeAsks first

    Templates > Emails & SMS > Add Email Template. Reminders, portal invitations and proposals use these templates. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → manage_email_templates

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/email-templates/manage

    Parameters

    Parameters: manage_email_templates
    NameTypeDescription
    action string required string One of `list`, `create`. `list` and `get` only read.
    name string string Template name.
    type string string Template Type. It decides which variables the template can use.
    subject string string Subject, variables allowed.
    body string string Message, variables allowed.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "template": "Your session is next week",
      "type": "Event",
      "subject": "See you soon, {client first name}",
      "saved": true
    }

Invoices, payments and the books7

Finances > Money. A refund is recorded in Pixifi; you send the money back in Stripe or Square yourself.

  • manage_event_invoices List an event's invoices or create one with product lines. writeAsks first

    Runs Invoices > Create New Invoice on the event, then fills the invoice editor. Creating does not send anything; send_invoices does. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → manage_event_invoices

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/event-invoices/manage

    Parameters

    Parameters: manage_event_invoices
    NameTypeDescription
    action string required string One of `list`, `get`, `create`. `list` and `get` only read.
    event string string Event the invoice belongs to.
    issue_date string string ISO date.
    due_date string string ISO date.
    lines array array For `create`: products from your product list, or manual lines with description and amount.

    Example input

    {
      "action": "create",
      "event": "Example Couple wedding",
      "issue_date": "2026-11-16",
      "due_date": "2027-05-12",
      "lines": [
        {
          "description": "Full day coverage",
          "amount": 3200
        },
        {
          "description": "Engagement session",
          "amount": 450
        }
      ]
    }

    Example response

    {
      "event": "Example Couple wedding",
      "invoice": "INV-1042",
      "lines": [
        {
          "description": "Full day coverage",
          "amount": 3200
        },
        {
          "description": "Engagement session",
          "amount": 450
        }
      ],
      "total": 3650,
      "saved": true
    }
  • send_invoices Send a client invoice, or return its direct link. writeAsks first

    Opens the invoice with VIEW and sends it the way you choose. A sent invoice reaches your client and asks them to pay. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → send_invoices

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/invoices

    Parameters

    Parameters: send_invoices
    NameTypeDescription
    invoice string required string Invoice number.
    send_by string string A sending option Pixifi offers on the invoice view, or `link` to only return the link.

    Example input

    {
      "invoice": "invoice"
    }

    Example response

    {
      "invoice": "INV-1042",
      "client": "Example Couple",
      "total": 3650,
      "link": "https://www.pixifi.com/invoice/example",
      "sent": false
    }
  • view_accounts_receivable Read unpaid required payments and open invoice balances for a year. read

    Finances > Money > Accounts Receivable. Unpaid payments are the Required Payments on invoices that are still open; invoice balances are invoices with money left to pay. It changes nothing and runs without asking.

    MCP callpixifi_read → view_accounts_receivable

    REST endpointGET https://cotlet.dev/api/v1/pixifi/accounts-receivables/view

    Parameters

    Parameters: view_accounts_receivable
    NameTypeDescription
    year number number Year. Default this year.
    tab string string `unpaid_payments` or `invoice_balances`. Default `invoice_balances`.

    Example response

    {
      "year": 2026,
      "tab": "invoice_balances",
      "invoices": [
        {
          "invoice": "INV-1042",
          "client": "Example Couple",
          "balance": 2650
        },
        {
          "invoice": "INV-1039",
          "client": "Sample Family",
          "balance": 450
        },
        {
          "invoice": "INV-1031",
          "client": "Example Brand",
          "balance": 1200
        }
      ]
    }
  • manage_payments_received Read payments received, add one or batch update several. writeAsks first

    Finances > Money > Payments Received. Batch Update can delete payments, so the agent lists the selected ones before it runs. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → manage_payments_received

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/payments-received/manage

    Parameters

    Parameters: manage_payments_received
    NameTypeDescription
    action string required string One of `list`, `add`, `batch_update`. `list` and `get` only read.
    year number number Year to read. Default this year.
    filters object object Category, brand, type, account or date range.
    payment object object For `add`: amount, date, type and invoice.
    change string string For `batch_update`: brand, payment type, payment category, add a fee expense, or delete.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "year": 2026,
      "payments": [
        {
          "client": "Example Couple",
          "amount": 1000,
          "type": "Retainer",
          "date": "2026-10-02"
        },
        {
          "client": "Sample Family",
          "amount": 350,
          "type": "Card",
          "date": "2026-11-08"
        }
      ]
    }
  • record_refund Record a refund on an invoice as a negative payment of type Refund. writeAsks first

    Follows Pixifi's refund steps: Add Paid Payment with a negative amount and Payment Type Refund. Pixifi does not move the money: you issue the refund yourself in Stripe or Square. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → record_refund

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/refunds

    Parameters

    Parameters: record_refund
    NameTypeDescription
    invoice string required string Invoice the refund belongs to.
    amount number required number Refund amount. The tool enters it as a negative number.

    Example input

    {
      "invoice": "invoice",
      "amount": 1
    }

    Example response

    {
      "invoice": "INV-1042",
      "amount": -200,
      "payment_type": "Refund",
      "saved": true
    }
  • manage_expenses Read expenses by year and category, add one, duplicate one or batch update. writeAsks first

    Finances > Money > Expenses, where Pixifi charts the year by expense category and against payments. Batch Update can delete, so the agent lists the selected expenses first. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → manage_expenses

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/expenses/manage

    Parameters

    Parameters: manage_expenses
    NameTypeDescription
    action string required string One of `list`, `add`, `duplicate`, `batch_update`. `list` and `get` only read.
    year number number Year to read.
    expense object object For `add`: amount, date, vendor, category and account.
    change string string For `batch_update`: brand, vendor, expense category, account, or delete.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "year": 2026,
      "by_category": [
        {
          "category": "Gear",
          "total": 2180
        },
        {
          "category": "Travel",
          "total": 640
        },
        {
          "category": "Software",
          "total": 410
        }
      ]
    }
  • view_profit_and_loss Read the Profit & Loss statement for a year, or export it. read

    Finances > Money > Profit & Loss: total revenue, sales tax collected, expenses paid and gross margin for the year. It changes nothing and runs without asking.

    MCP callpixifi_read → view_profit_and_loss

    REST endpointGET https://cotlet.dev/api/v1/pixifi/profit-and-loss/view

    Parameters

    Parameters: view_profit_and_loss
    NameTypeDescription
    year number number Calendar year. Default this year.
    filters object object Filter Options, such as brand.
    export string string `csv` or `pdf` to return the exported report.

    Example response

    {
      "year": 2026,
      "revenue": 48200,
      "sales_tax_collected": 1960,
      "expenses": 9850,
      "gross_margin": 38350
    }

Projects, tasks, vendors and workshops6

Longer jobs with tracked time, the task list, your vendor list, and workshops with tickets (Studio Pro plan or higher).

  • manage_projects List projects or create one for a client. writeAsks first

    Projects hold work that is not a single event, with tasks and time. The tool uses the same Add Project form as the Projects module. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → manage_projects

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/projects/manage

    Parameters

    Parameters: manage_projects
    NameTypeDescription
    action string required string One of `list`, `get`, `create`. `list` and `get` only read.
    client string string Client the project is for.
    fields object object Project name and the other project fields.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "project": "Example Brand product catalog",
      "client": "Example Brand",
      "saved": true
    }
  • track_project_time Read a project's time, add a time entry, or invoice billable time. writeAsks first

    `summary` reads Time Tracking: time by task, invoiced against not invoiced, billable against non-billable. `invoice` runs Invoice Time, which puts the billable entries on an invoice. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → track_project_time

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/project-time/track

    Parameters

    Parameters: track_project_time
    NameTypeDescription
    action string required string One of `summary`, `add`, `invoice`. `list` and `get` only read.
    project string required string The project.
    task string string For `add`: the task the time is for.
    hours number number For `add`: hours worked.
    billable boolean boolean For `add`: billable or not.

    Example input

    {
      "action": "action",
      "project": "project"
    }

    Example response

    {
      "project": "Example Brand product catalog",
      "hours": {
        "total": 14.5,
        "billable": 12,
        "invoiced": 6
      }
    }
  • manage_tasks List tasks, add a general task or batch update several. writeAsks first

    Things to Do > Tasks. Batch Update changes every selected task in one step, so the agent lists them for you first. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → manage_tasks

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/tasks/manage

    Parameters

    Parameters: manage_tasks
    NameTypeDescription
    action string required string One of `list`, `create`, `batch_update`. `list` and `get` only read.
    title string string Task title, for `create`.
    fields object object For `create`: assignee, due date and the other task fields.
    tasks array array For `batch_update`: the tasks to change.
    change object object For `batch_update`: the change Batch Update Tasks applies to all of them.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "tasks": [
        {
          "title": "Cull Example Couple engagement",
          "due": "2026-11-20",
          "done": false
        },
        {
          "title": "Order album proofs",
          "due": "2026-11-24",
          "done": false
        }
      ]
    }
  • manage_vendors List vendors or add one with a type and category. writeAsks first

    Contacts > Vendors. `get` also shows which events the vendor has been linked to over the years. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → manage_vendors

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/vendors/manage

    Parameters

    Parameters: manage_vendors
    NameTypeDescription
    action string required string One of `list`, `get`, `create`. `list` and `get` only read.
    name string string Vendor name.
    type string string Vendor type, for example Florist or Venue.
    category string string Vendor category.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "vendor": "Example Florals",
      "type": "Florist",
      "category": "Preferred",
      "events_linked": 6
    }
  • manage_workshops List workshops or create one with dates and capacity. writeAsks first

    Things to Do > Workshops. Pixifi marks Workshops as Pro: it needs the Studio Pro plan or higher. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → manage_workshops

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/workshops/manage

    Parameters

    Parameters: manage_workshops
    NameTypeDescription
    action string required string One of `list`, `create`. `list` and `get` only read.
    brand string string Brand of the workshop.
    name string string Workshop name.
    start_date string string ISO date.
    end_date string string ISO date.
    capacity number number Maximum capacity.
    description string string Description shown on the workshop page.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "workshop": "Off-camera flash basics",
      "start_date": "2027-03-06",
      "end_date": "2027-03-06",
      "capacity": 12,
      "saved": true
    }
  • manage_workshop_tickets Add a ticket type to a workshop with price and quantity. writeAsks first

    Ticket quantities may add up to more than the workshop's capacity, but buyers can never take more places than the capacity. Tickets go on sale on the workshop page. By default you confirm each call; you can switch that off for this tool.

    MCP callpixifi_write → manage_workshop_tickets

    REST endpointPOST https://cotlet.dev/api/v1/pixifi/workshop-tickets/manage

    Parameters

    Parameters: manage_workshop_tickets
    NameTypeDescription
    workshop string required string The workshop.
    name string required string Ticket name.
    price number number Price per ticket. Leave out for a free workshop.
    quantity number required number Tickets available.
    payment_terms string string Payment Terms Template. Without one the buyer pays the full price.

    Example input

    {
      "workshop": "workshop",
      "name": "Jane Doe",
      "quantity": 1
    }

    Example response

    {
      "workshop": "Off-camera flash basics",
      "ticket": "General admission",
      "price": 149,
      "quantity": 12,
      "saved": true
    }
Encrypted, revocable

Who can see my Pixifi session, and how do I revoke it?

  • What we store

    Your signed-in Pixifi browser profile, AES-256-GCM encrypted, in Finland. Never your password.

  • What your agent gets

    The 38 Pixifi tools. The session cookie stays in the Cloud Browser.

  • What the session sees

    The clients, events and money records your Pixifi user and plan can open, and nothing more.

  • What no tool touches

    Your Pixifi settings and staff permissions, the Twilio SMS setup, payment processor accounts and the dashboard layout.

  • If Pixifi signs you out

    You log in again yourself, in the same Cloud Browser. Two-factor sign-in stays with you.

  • How to cut access

    Disable Pixifi for agents, reset the browser, or change your Pixifi password.

Cotlet never sees or stores your password: you type it yourself, and the agent only uses the session that login leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).

34 tools ask first

Approvals, undo and mistakes Clients get nothing until you say so.

  1. 01 Read the event manage_events returns the date and client.
  2. 02 Build the invoice Lines and total, shown to you first.
  3. 03 Save after your OK manage_event_invoices creates it, unsent.
  4. 04 Send when you say send_invoices is a separate call.
Fixing a Pixifi write that went wrong
ActionHow to put it right
Client, lead, event or task fieldsCall the same tool again with the earlier values
Lead moved to the wrong statusMove it back; automations of the wrong status may already have run
Proposal, contract or invoice sentAlready with your client: talk to them before you change it
Payments or expenses batch deletedAdd them again from your records; Pixifi has no undo for a batch delete

All 34 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 4 read tools (clients, the calendar, accounts receivable and the P&L) run at once.

MCP call
{
  "name": "manage_event_invoices",
  "arguments": {
    "action": "create",
    "event": "Example Couple wedding",
    "issue_date": "2026-11-16",
    "due_date": "2027-05-12",
    "lines": [
      {
        "description": "Full day coverage",
        "amount": 3200
      },
      {
        "description": "Engagement session",
        "amount": 450
      }
    ]
  }
}
REST
curl -X POST https://cotlet.dev/api/v1/pixifi/event-invoices/manage \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"action":"create","event":"Example Couple wedding","issue_date":"2026-11-16","due_date":"2027-05-12","lines":[{"description":"Full day coverage","amount":3200},{"description":"Engagement session","amount":450}]}'
Response
{
  "event": "Example Couple wedding",
  "invoice": "INV-1042",
  "lines": [
    {
      "description": "Full day coverage",
      "amount": 3200
    },
    {
      "description": "Engagement session",
      "amount": 450
    }
  ],
  "total": 3650,
  "saved": true
}

The example bills $3,200 for full day coverage and $450 for the engagement session: $3,650. Nothing is sent to the couple until send_invoices runs. A cron job or n8n flow makes the same call over REST at /api/v1/pixifi with the same key and price. Failed calls are free.

Pay per call

How much does the Pixifi MCP server cost?

About $27 a monthfor a studio shooting about eight sessions a month, 4,700 credits. Your Pixifi plan stays as it is.

Illustrative month, our assumption: successful calls for this workload
JobCallsCredits
New inquiries into leads and proposals2 × 25500
Contracts, timelines and staff for booked shoots3 × 8240
Event invoices created and sent2 × 16320
Monday receivables check and reminders4 × 4160
Payments received and expenses entered1 × 80800
Weekly calendar and task review2 × 480
Questionnaires sent before sessions1 × 20200
Client and lead lookups1 × 90900
Cloud Browser, 30 days1,500
Total320 calls4,700

The smallest pack, 5,000 credits for $29, covers this month. A busy wedding season uses more calls.

  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • Your Pixifi plan and user apply as they are

Credit packs are one-time purchases, not a subscription. The month above is 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

Pixifi MCP server: other ways to connect What each route does for a photography studio, and where it stops.

Other ways to work with Pixifi, checked 16 Nov 2026
OptionWhat it doesWhere it stops
Pixifi APIDescribed by Pixifi in 2023 as keys issued to partner vendors.No public documentation or self-serve key for a studio.
Zapier integrationListed by Pixifi among its integrations.Trigger and action recipes you set up in Zapier, not an agent working in Pixifi.
Pixifi mobile appsSchedule, client information and invoices on iOS and Android.Your hands on the phone; no AI agent route.
By handOpen each client, event and invoice in Pixifi.One screen at a time, only while you are at the desk.

If one of Pixifi's own integrations already covers your job, use it: it is the vendor's route. Cotlet fits when you want ChatGPT, Claude or a script doing the studio paperwork in Pixifi today, from your own login, with nothing to host.

EU company, since 2019

Who runs Cotlet A company you can look up.

Cotlet is built by Take Group sp. z o.o., registered in Poland, EU (VAT PL6342984273) and in business since 2019, with founders Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Pixifi tools go to contact@cotlet.dev.

Pixifi MCP server: questions

How do I get access?

Sign up free at https://cotlet.dev/signup?app=pixifi, turn on Pixifi under Integrations in the console and log in at https://www.pixifi.com/admin/ in your Cloud Browser. Then connect your AI agent and ask it about your clients or events. The trial needs no card.

Does Pixifi have an API?

Pixifi publishes no public API documentation: pixifi.com/api answers 404, and in its 1 Nov 2023 webinar Pixifi described its API as bespoke, with keys issued to partner vendors (checked 16 Nov 2026). No Pixifi MCP server and no official ChatGPT or Claude connector was found. Cotlet does not use that API: it works in your own signed-in Pixifi account.

Which Pixifi plan do the staff and workshop tools need?

Pixifi Academy says that on the Essential plan you can only assign yourself to an event, and that Workshops need the Studio Pro plan or higher. The tools follow your plan: they cannot do what your plan does not allow.

Does record_refund send money back to my client?

No. Pixifi records a refund as a negative payment of type Refund; you issue the money back yourself in Stripe or Square, as Pixifi Academy describes.

Which Pixifi user should I log in with?

The user whose work the agent should do, usually the studio owner. The agent sees only what that user and your plan can see in Pixifi.

Is the MCP server different from the REST API?

Only in how it is called. Both carry the same 38 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.

Is Cotlet affiliated with Pixifi?

No. Cotlet is independent and not affiliated with Pixifi.

Hand your next Pixifi proposal to your agent.

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