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

# Portrait Care MCP server: Let your AI agent run the Portrait schedule.

> Portrait Care has no MCP server, no ChatGPT or Claude app, no public API and no Zapier app; it is built as a closed all-in-one platform (checked 9 Nov 2026). Cotlet runs 5 Portrait Care tools hosted, over MCP for agents and REST for scripts, in your own Portrait login, for the schedule and patient contact details only.

Your AI agent books consults and treatments from messages, moves a provider's day and finds patients due back. Sign in to Portrait once in your own Cloud Browser. Charts stay untouched.

- Free 7-day trial, no card
- Unofficial, not affiliated with Portrait Care
- Page: https://cotlet.dev/integrations/portrait-care-api-mcp-server

## What can your AI agent do in Portrait Care?

- Book from messages
- Find free slots per provider
- Move a provider's day
- Find patients due back
- See tomorrow per provider
- Charts stay untouched

## Does Portrait Care have an MCP server or an API?

- Portrait Care publishes no developer docs.
- Portrait Care has no Zapier app.
- Portrait Care has no connector in the ChatGPT apps directory or in Claude.

| What you need | Portrait API | By hand | Cotlet |
|---|---|---|---|
| Schedule and free times | No API | Yes, one by one | Yes |
| Book or move | No API | Yes, one by one | Yes, after your OK |
| Patients due back | No API | Patient by patient | Yes |
| Ask in ChatGPT or Claude | No | No | Yes |
| Charts and notes | No API | Yes | Not touched |

Checked 8 Nov 2026. Sources: [Portrait Care site](https://www.portraitcare.com/), [Portrait vs Mindbody (features, integrations)](https://www.portraitcare.com/post/portrait-care-vs-mindbody), [Portrait web app login](https://go.portraitcare.com/login)

## How does the Portrait Care MCP server work?

1. **Sign in to Portrait Care.** Once, in a browser we host for you.
2. **Connect your AI agent.** One address in its settings.
3. **Hand it the busywork.** It drafts the work, you OK what customers get.

We never keep your Portrait password, the tools never open charts, and no booking or move goes through until you approve it.

## How to connect Portrait Care to your AI agent

1. **Sign in to Portrait Care in a Cloud Browser.** Create a Cotlet account, open Portrait Care in its Cloud Browser, sign in with your Portrait login and press Enable for agents.
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.

Portrait Care shares the address `https://cotlet.dev/mcp/v1` with every other app you enable, so one connector covers them all. Turned Portrait Care on after connecting? Refresh the connector and the 5 tools appear.

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

ChatGPT:

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

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

Make, Zapier:

```
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: portrait_care_write
```

## All 5 Portrait Care MCP tools

### Schedule

Free slots come from the schedule. Bookings and moves wait for your OK; Portrait sends its usual messages.

- **List appointments** (`list_appointments`, read): Appointments for a day or range, by provider.
- **Find free slots** (`find_free_slots`, read): Open times for a service, optionally with one provider.
- **Book appointment** (`book_appointment`, write, asks first): Books a service for a patient with a provider.
- **Reschedule appointment** (`reschedule_appointment`, write, asks first): Moves an appointment to a new time or provider.

### Patients

Contact details, last visit and last service only. No charts or clinical notes.

- **List patients** (`list_patients`, read): Patients, searchable by name, phone or email, with last visit.

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

## Who can see my Portrait Care session, and how do I revoke it?

- **What we store.** Your signed-in Portrait Care profile, AES-256-GCM encrypted, in Finland. No password.
- **What your agent gets.** The 5 Portrait Care tools, never the session cookie.
- **What the session sees.** What your login sees on the schedule and patient contact details.
- **What no tool touches.** Charts, clinical notes, exams, payments, inventory, deletes.
- **If Portrait Care signs you out.** You sign in again yourself, in the same Cloud Browser.
- **How to cut access.** Disable for agents, reset the browser, or change your Portrait Care password.

Cotlet never types your password: you sign in yourself, and the agent only uses the session. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)).

## What happens when Portrait Care changes?

- **12 h** between tests of the Portrait Care reads
- **24 h** between tests of sends a customer would notice
- **$0** for a call to a Portrait Care tool paused for repair

When Portrait moves a button on the schedule or renames a patient tab, we fix the tool and your agent calls it the same way. [status.cotlet.dev](https://status.cotlet.dev) checks the site, console and API every 3 minutes.

## Approvals, undo and mistakes

1. **Finds the patient.** By name, phone or email.
2. **Checks free slots.** For the service and provider.
3. **Proposes the booking.** With time and provider.
4. **Waits, then books.** The booking shows up in your Cotlet console first.

| Action | Undo |
|---|---|
| Book an appointment | Yes, cancel it |
| Move an appointment | Move it back; a message already sent stays sent |

2 of 5 tools ask first: book_appointment, reschedule_appointment. You can turn the wait off per tool once you trust a routine.

MCP call:

```
{
  "name": "book_appointment",
  "arguments": {
    "patient_id": "PT-7790",
    "service": "Dermal filler consult",
    "provider": "Dr. Patel",
    "start": "2026-11-13T14:30"
  }
}
```

REST:

```
curl -X POST https://cotlet.dev/api/v1/portrait-care/patients/PT-7790/appointments \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"service":"Dermal filler consult","provider":"Dr. Patel","start":"2026-11-13T14:30"}'
```

Response:

```
{
  "appointment_id": "AP-50877",
  "patient": "Emily Carter",
  "service": "Dermal filler consult",
  "provider": "Dr. Patel",
  "start": "2026-11-13T14:30",
  "status": "Booked"
}
```

A cron job or n8n flow can call the same tools over REST at `/api/v1/portrait-care` with the same key and price, in JSON. Failed calls are free. Each tool row above shows its REST path.

## How much does the Portrait Care MCP server cost?

**About $27 a month** for a med spa with 2 providers, 4,690 credits. Your Portrait Care plan stays as it is.

| Job | Calls | Credits |
|---|---|---|
| Booking from a message | 3 × 80 | 2,400 |
| Patients due back, weekly | 2 × 4 | 80 |
| Appointment moved | 3 × 15 | 450 |
| Tomorrow checked, daily | 1 × 26 | 260 |
| Cloud Browser, 30 days |  | 1,500 |
| Total |  | 4,690 |

- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Works on your current Portrait plan

Portrait publishes no booking counts, so the month is our example. Dollars at the $29 pack rate.

## Portrait Care MCP server on GitHub, Zapier or hosted: which to use

| Option | What it does | Where it stops |
|---|---|---|
| Portrait online booking | Patients book themselves. | Only the patient books; no moves or lists for you. |
| Portrait CRM | Follow-ups inside Portrait. | Set up in Portrait; nothing you can ask in plain words. |
| By hand | Every screen of Portrait, one booking at a time. | Your front desk's time. |

Portrait Care has no API or Zapier app, so there is nothing to connect a script to. To book, move and bring patients back from ChatGPT or Claude this week, Cotlet works in the Portrait account you already have.

## Who runs Cotlet

Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), in business since 2019, led by its founders Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Portrait Care tools go to contact@cotlet.dev.

## Portrait Care MCP server: questions

### How do I get access?

Sign up free at https://cotlet.dev, open Portrait Care under Integrations in the console and sign in to Portrait Care in its Cloud Browser. The trial starts with your first app and asks for no card.

### How do I connect Portrait Care to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Portrait Care once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Portrait Care account through Cotlet, in their phone apps too.

### What can ChatGPT do in Portrait Care?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Portrait Care: book consults from messages; bring patients back; move a provider's day. You ask in plain words, and anything that reaches other people waits for your OK first.

### Is there an official ChatGPT or Claude app for Portrait Care?

No. Portrait Care has no ChatGPT or Claude connector of its own and Portrait Care has no official MCP server (checked 9 Nov 2026). Cotlet is an independent one that works in ChatGPT, Claude, Cursor and any MCP client, on your signed-in account.

### Can ChatGPT book appointments in Portrait Care?

Yes, with Cotlet. ChatGPT finds the patient, checks free slots and books the service with the provider you name. Booking waits for your OK by default.

### Can ChatGPT find patients due back in Portrait Care?

Yes, with Cotlet. ChatGPT lists patients who have not been back in the time you name, with their last service, so your team can reach out.

### Does Cotlet read patient charts in Portrait Care?

No. The Portrait Care tools cover the schedule and patient contact details. Charts, clinical notes and Good Faith Exams are not part of them.

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

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

### Is Cotlet affiliated with Portrait Care?

No. Cotlet is independent and not affiliated with Portrait Care.

---

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.
