Fresha by Cotlet MCP server

Fresha API and MCP server, self-hosted

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

It is for technical people who want to run it themselves, for noncommercial use only (license). If you want it running 24/7 on a server, kept working when Fresha changes its panel, for a team or a business, use the hosted version at cotlet.dev.

git clone https://github.com/cotletdev/fresha-api-mcp-server.git && cd fresha-api-mcp-server
python3 -m venv .venv && . .venv/bin/activate && pip install -e .
fresha-mcp connect                                 # reads your Fresha session from Chrome
fresha-mcp call list_services
claude mcp add fresha -- "$PWD/.venv/bin/fresha-mcp" mcp

Contents

• 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

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 curlcffi, which copies Chrome's TLS fingerprint. No headless browser runs.

The session lives in one cookie, freshapartnerssession. 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

Shortened. The full README is on GitHub.