Fresha MCP Server and API by Cotlet

Fresha API and MCP server: connect Fresha to ChatGPT and Claude

Yes, ChatGPT, Claude and other AI agents can work in your Fresha account. That includes Cursor, Codex, OpenClaw and any MCP client, plus automations in n8n, Make and Zapier. Ask in plain words, and the AI reads your calendar and open slots, books and moves appointments, answers reviews and reports your sales. It shows you what it will do first and sends nothing to other people until you say so.

As of November 2026, this repo is the missing piece: 17 Fresha tools for AI assistants and scripts.

What you can ask

*Anna Smith emailed asking for a cut and colour with Sam on Friday afternoon. Find her, check the free times for both services and book the first one after my OK.*

*Sam is sick tomorrow. Block his day and show me which of his clients a colleague can take at the same time.*

*Yesterday's sales by sale type against the same day last week. Flag refunds over £50.*

*List the reviews without a reply and draft a short answer to each.*

Two ways to get it

Cotlet is best for salon, spa and wellness business owners who want ChatGPT, Claude or another AI agent to work in Fresha for them, with nothing to install.

[Start free at cotlet.dev →](https://cotlet.dev/signup?app=fresha&utm_source=github&utm_medium=readme&utm_campaign=fresha&utm_content=top-button)

Run it yourself

A Fresha API and a Fresha MCP server you run on your own computer, in Python, on the session of your own Google Chrome. All 17 Fresha tools we run in production at Cotlet: appointments, free slots, booking, rescheduling and cancelling, blocked time, clients and client notes, services and team, the Sales summary and Sales list reports, and reviews with replies.

Fresha has no public API and no official MCP server. Its only data connection is the paid Data Connector add-on, which copies your data out to a Snowflake database and cannot book anything. This repo gives you:

• MCP server for Claude Code, Claude Desktop, Cursor, Codex and any MCP client, over stdio or HTTP. Setup
• REST API on http://127.0.0.1:8787/api/v1/fresha, with OpenAPI docs at /docs. Setup
• Python: call("list_appointments", {"from": "2026-10-27", "to": "2026-10-27"}), plus 9 ready scripts in examples/.

Free for your own use, your own business included (license).

uv tool install fresha-api-mcp                  # or: pip install fresha-api-mcp

fresha-mcp connect # reads your Fresha session from Chrome fresha-mcp call list_services claude mcp add fresha -- uvx fresha-api-mcp mcp

Contents

• Questions from Fresha users
• How it works
• Requirements
• Install
• Connect your Chrome
• MCP server
• REST API
• Python and the example scripts
• All 17 tools
• Configuration
• Security and your Fresha account
• Errors
• Self-hosted or hosted
• FAQ
• License

Questions from Fresha users

Does Fresha have an API? No public one. Fresha publishes no API and no developer docs (checked 11 Oct 2026). Its Data Connector add-on, paid per location, syncs your data out to reporting tools through a Snowflake connection, and it cannot book, move or cancel appointments. This repo and Cotlet give you 17 Fresha tools as a REST API and an MCP server.

Can I get a Fresha API key? Not from Fresha for your own account. With Cotlet you get your own API key that works with your Fresha account, for scripts, n8n, Make, Zapier or any HTTP client. This repo needs no key: it runs on your computer, on your own Fresha session.

Is there an official ChatGPT integration for Fresha? Fresha's ChatGPT and Claude apps are for clients: they find salons and book open slots. They do not run your business. Cotlet connects your Fresha partner account to ChatGPT, Claude and other AI agents: your calendar, clients, team and sales.

How do I connect Fresha to ChatGPT? Sign up at cotlet.dev, sign in to Fresha once in your Cloud Browser there, and add Cotlet to ChatGPT, following the steps in your account. Then ask ChatGPT about your Fresha like you would ask an assistant. ChatGPT needs a server on the internet, so this repo alone, running on your computer, does not connect to ChatGPT.

Can ChatGPT manage my Fresha calendar? Yes, with Cotlet. It lists the day's appointments and gaps, finds open slots, books and moves appointments and blocks time. It shows you each change first.

Fresha has an AI receptionist. What does this add? Fresha's AI answers your clients. With Cotlet, your own AI works for you in the back office: the calendar, clients, team and sales reports.

Can I automate Fresha with Zapier, Make or n8n? Fresha has no Zapier or Make app. With Cotlet, n8n, Make and Zapier can read and book appointments and add clients, for example from a web form.

Can I use it from my phone? Yes, with Cotlet: once it is set up, the ChatGPT and Claude apps on your phone can use Fresha for you.

Do I need to be technical? For Cotlet, no: you sign in to Fresha and add Cotlet to ChatGPT or Claude, with step-by-step instructions in your account. This repo is for people who are fine with Python and a terminal.

Is my Fresha account safe? Yes. Neither Cotlet nor this repo sees or stores your Fresha password. You sign in yourself, the way you always do, and the AI works on that signed-in session. Anything that reaches other people asks for your OK first: in Cotlet by default, here through your MCP client.

Is it free? This repo is free, also in your own business. Cotlet is free for 7 days with no card, then one-time credit packs from $29, no subscription. Pricing.

I manage Fresha for several accounts or clients. Does that work? Yes, with Cotlet. Each Fresha login gets its own connection. Write to contact@cotlet.dev and tell us how many accounts you manage.

How it works

AI agent (MCP) / script (REST, Python) ──▶ fresha-mcp on your computer ──your cookies──▶ *.fresha.com

▲ fresha-mcp connect ──────┘ reads them once from your Chrome (DevTools Protocol)

1. You sign in to Fresha for business in your own Chrome at partners.fresha.com, the way you always do: an email code, then a text message code. Tick Trust this device.
2. fresha-mcp connect attaches to that Chrome through the Chrome DevTools Protocol, reads the fresha.com cookies and saves them to ~/.config/fresha-api-mcp/session.json, readable by your user only. It never sees or stores your password or the codes.
3. Every tool call is a request to the APIs the Fresha partner panel itself calls (partners-api, the partners-api-gateway GraphQL, customers-api, reports.fresha.com and a few more *.fresha.com hosts) with those cookies, sent with curl_cffi, which copies Chrome's TLS fingerprint. No headless browser runs.

The session lives in one cookie, fresha_partners_session. Fresha keeps it for 25 days and renews it while you use the panel or the tools. When Fresha signs you out, the server reads the cookies from Chrome again, if Chrome is open with remote debugging on.

Requirements

• Python 3.11 or newer.
• Google Chrome 144 or newer, signed in to partners.fresha.com. Any Chrome or Chromium works with a debugging port.
• macOS, Linux or Windows.
• A Fresha for business account. We build and test with the workspace owner. A team member login sees what Fresha shows that team member, and the two sales tools need its reporting permissions.

Install

From PyPI:

uv tool install fresha-api-mcp       # or: pipx install fresha-api-mcp, or: pip install fresha-api-mcp

fresha-mcp --version

MCP clients can also run it with no install: uvx fresha-api-mcp mcp.

From source:

git clone https://github.com/cotletdev/fresha-api-mcp-server.git

cd fresha-api-mcp-server python3 -m venv .venv . .venv/bin/activate # Windows: .venv\Scripts\activate pip install -e . fresha-mcp --version

With uv: uv venv && uv pip install -e ., then uv run fresha-mcp ....

Setting it up with an AI agent (Claude Code, Codex, Cursor)? Open it in this folder and ask it to set up the repo: AGENTS.md tells it every step, and it asks you only for the steps in Chrome.

To update: uv tool upgrade fresha-api-mcp (or pip install -U fresha-api-mcp), from source git pull && pip install -e .. We copy every change of the hosted Fresha tools into this repo.

Connect your Chrome

Option A: your everyday Chrome (recommended)

1. Open chrome://inspect/#remote-debugging in Chrome and switch remote debugging on. Chrome then accepts DevTools connections from programs on this computer, and asks you before each one.
2. Make sure you are signed in at partners.fresha.com.
3. Run:

   fresha-mcp connect

1. Chrome asks whether to allow the connection. Click Allow.

Saved 24 Fresha cookies to /Users/you/.config/fresha-api-mcp/session.json

Signed in to Fresha as Daniel Hughes (daniel@example.com)

You can switch remote debugging off again afterwards. Leave it on if you want the server to pick up a new session by itself after Fresha signs you out.

connect looks for Chrome's DevToolsActivePort file in the default profile folder. For Chrome Beta, Canary or a custom profile folder, pass --profile-dir " ".

Option B: a Chrome with a debugging port

Chrome does not open a debugging port on your default profile, so start a separate one, sign in to Fresha there once, and connect to it:

# mac