Fresha MCP server for ChatGPT, Claude and any AI agent: list appointments, create appointment, reschedule appointment, list clients and get sales summary in your own Fresha account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Fresha yourself; Cotlet does not store your password and you need no Fresha API key. About the official Fresha API: Fresha has no public API and no developer docs (checked 11 Oct 2026). Its only official data connection is the paid Data Connector add-on, which syncs your data out to reporting tools through a Snowflake database connection. Setup and FAQ: https://cotlet.dev/integrations/fresha-api-mcp-server
Scored across 47 tools
Five fresha_* guide tools (fresha_list_appointments, fresha_list_clients, fresha_create_appointment, fresha_reschedule_appointment, fresha_get_sales_summary) directly shadow the real domain tools (list_appointments, list_clients, create_appointment, reschedule_appointment, get_sales_summary) but only return step-by-step instructions instead of data. An agent can easily pick the guide tool and get prose where it expected records. The 25 cotlet_browser_* primitives are individually distinct, but the overall set forces the agent to reason about two layers (dedicated tools vs. browser automation) plus a guide layer.
There is a namespace convention (bare verb_noun for Fresha domain tools, cotlet_browser_<verb> for primitives, cotlet_<x> for account helpers, fresha_<verb_noun> for guides), which is readable once understood. But the verbs are inconsistent across layers (add_client vs create_appointment vs cotlet_browser_open), and the fresha_ prefix pairs near-identically named tools with opposite behavior, so naming actively misleads in places.
47 tools is well past the heavy threshold, and a meaningful chunk is redundant: the 5 fresha_* guide tools restate capabilities the dedicated tools already cover. The 25 generic browser primitives are justified for covering anything Fresha's tools do not, but shipping both layers plus guides makes the surface bloated for what is essentially one app integration.
Core workflows are covered: list/get/create/reschedule/cancel appointments, find_available_slots, clients with notes, sales, reviews with replies, services, team members and locations, blocked time. But it is read-heavy and one-directional — no update or delete for clients, no editing service catalogue or pricing, no payments/checkout, no membership or gift-card operations, and no way to edit an appointment's services in place. The browser fallback partly compensates, but the dedicated surface has notable gaps.
Block a time slot in a team member's calendar so nobody books it. Adds blocked time as Add > Blocked time in the calendar does: one block on one day for one team member at one location (default: their primary location), with a title and a note for the team. It does not repeat. Clients cannot book it online unless allow_online_booking is true. Nobody is told.
Inputs: end_at (required), start_at (required), team_member_id (required), title, +3 more.
Add a client to the business's client list. Adds a client as Add client in the Client list does: name, email, mobile and gender. With appointment_messages (default true) Fresha sends the client booking confirmations and reminders to the email and mobile given; marketing (default false) records consent to marketing messages. Nothing is sent when the client is added.
Inputs: first_name (required), email, phone, gender, +3 more.
Add a note to a client's profile, seen by the team only. Adds a note to the client's Notes tab for all locations, as the profile's Add note does. Only the team sees it; the client is not told. Line breaks become paragraphs.
Inputs: text (required), client_id (required).
Cancel an appointment without a charge, optionally telling the client. Cancels the appointment as Cancel in its drawer does, with one of the business's cancellation reasons. With notify_client (default true) Fresha sends the client a cancellation message, so this can reach the client; false cancels quietly. whole_series also cancels the later appointments of a repeating series. An appointment with a cancellation fee or a paid deposit is refused: cancel it in Fresha. It cannot be undone here. By default you confirm each call; you can switch that off for this tool. Waits for the owner's approval.
Inputs: appointment_id (required), scope, reason, notify_client.
How to work in an app by clicking in the user's Cloud Browser with Cotlet's browser tools: which browser to use for this workspace and the sign-in link, the method step by step, the app's screens, menus and actions, notes, and the app's dedicated tools when Cotlet has them. Call it before the first browser step in an app. Works for any web app; one outside Cotlet's catalog gets the general method. Free, no browser session. For Fresha it covers these actions: List appointments, Create appointment, Reschedule appointment, List clients, Get sales summary.
Inputs: app, task.
The apps of the user's workspace and whether each works now: the app account in the user's Cloud Browser (connected, signed out, signed in but not connected), and the one step the user has to take, with the console link. Free. Needs the user's Cotlet API key or sign-in.
Inputs: app.
Clicks element element, or point x, y of the screenshot; double double-clicks, button: right right-clicks. Answers the page after it: the elements and text in view, with the same numbers. Says when nothing changed. A link that would open a new tab opens in this one. Buttons that pay or buy, and sign-in and account pages, are refused.
Inputs: x, y, button, dialog, +3 more.
Ends the browser session when the task is done: the browser keeps its cookies and sleeps, and the per-minute charge stops. Answers the session's minutes and credits.
Inputs: no named parameters.
Gets the file that clicking element (a download link or button) or opening url starts, also an image or PDF it only opens: answers its name, type, size and a link valid 15 minutes; CSV, JSON and other text files also as text.
Inputs: url, element.
Drags from one element or point to another: a card between columns, a piece on a board, a slider's handle. Answers the page after it: the elements and text in view, with the same numbers.
Inputs: to (required), from (required), dialog, dialog_text.
Runs a JavaScript function body on the page and answers what it returns, as JSON. Use it to extract data the page holds (a table, a list, attributes); act with the other tools. It cannot send requests, click, submit, or read cookies or storage; a filled field's value reads [hidden by Cotlet]. Example: return [...document.querySelectorAll('h2')].map(h => h.innerText)
Inputs: script (required).
Fills several fields in one step: text fields take text, drop-downs an option's label, checkboxes, radios and switches true or false. Stops at the first field that fails and names those filled. Does not send the form: click its button after. Answers the page after it: the elements and text in view, with the same numbers.
Inputs: fields (required), dialog, dialog_text.
Finds text on the whole current page, frames included: the elements whose label holds it, with their numbers, and each line of text that holds it. Use it instead of reading or scrolling a long page for one thing.
Inputs: text (required), kind.
Rests the pointer on an element or a point, to open a hover menu, a tooltip or a preview. Answers the page after it: the elements and text in view, with the same numbers.
Inputs: x, y, element.
Starts the user's Fresha Cloud Browser (a real Chrome on Cotlet, signed in to Fresha as the user; use it for what the Fresha tools do not cover) and opens url. Call it first. Only Fresha pages open. Answers the page after it: the elements and text in view, with the same numbers. In Fresha it serves these actions: List appointments, Create appointment, Reschedule appointment, List clients, Get sales summary.
Inputs: url.
Presses a key on the focused element: Enter to send, Tab to the next field, Escape to close a pop-up, arrows in a list or slider, or one character (a site's shortcut). Answers the page after it: the elements and text in view, with the same numbers.
Inputs: key (required), dialog, repeat, dialog_text.
The whole current page: its text (up to 20,000 characters) and a numbered list of its links, buttons, fields and other controls, open dialogs first. Use it on a new page or when a step's answer is not enough; element reads only inside one element (a dialog, a form, a list). Never returns field values, cookies or storage.
Inputs: element.
A JPEG of the visible part of the page. Use it for boards, canvases, maps, charts and layout that the text does not show, then click or drag by x, y of the image.
Inputs: no named parameters.
Scrolls with the mouse wheel: down or up by screens, to top or bottom, until element is in view, or inside a panel or list (inside). Content that loads on scroll appears. Answers the page after it: the elements and text in view, with the same numbers.
Inputs: inside, element, screens, direction.
Chooses option (its label as listed, or its value) in drop-down element. For a home-made drop-down, click it, then click the option. Answers the page after it: the elements and text in view, with the same numbers.
Inputs: option (required), element (required), dialog, dialog_text.
Types text into field element, replacing what it held; submit presses Enter after it. For several fields use fill_form. Without element the text goes where the focus is, as a person types after clicking: for spreadsheet cells and editors that read does not number (Google Sheets, Docs), click the place first; there a tab in text presses Tab and a line break Enter, so one call fills a table. Answers the page after it: the elements and text in view, with the same numbers. Password, card and one-time code fields are refused: the user types them.
Inputs: text (required), dialog, slowly, submit, +2 more.
Puts files into file field or upload button element: each file is {"url": "https://..."} or {"file_id": "..."} of a file uploaded to Cotlet; up to 10 files, 20 MB each. Answers the page after it: the elements and text in view, with the same numbers.
Inputs: files (required), element (required).
Waits until text shows on the page (at most seconds, default 5, up to 20), or just seconds: for results that load slowly. Says whether the text appeared. Answers the page after it: the elements and text in view, with the same numbers.
Inputs: text, seconds.
Status of an earlier Cotlet call, by its call_id: pending (waits for the owner's approval in the Cotlet console), approved, running, success, rejected, expired, blocked or failed. For a call that answered with status pending or running.
Inputs: call_id (required).
Sends a report to the Cotlet team: a tool that failed or returned wrong data, an error you could not get past, or a step the browser could not do, with the page, the step and what you saw. A missing dedicated tool is not a problem to report: do the task in the browser. A feature the user asks for goes as feature_request. A report promises nothing: tell the user it was sent, never that something will be built or fixed, or when. The report carries the error text and call_id when there is one, never passwords or tokens. Needs the user's Cotlet API key or sign-in.
Inputs: kind (required), title (required), description (required), app, +3 more.
Requests access to apps for the user's workspace, as Request access in the console: every app is granted at once. Not needed to work in an app: the user's AI works in any web app in their Web browser with cotlet_app_guide. An app with dedicated tools gets them after the user signs in to it in their Cloud Browser. Access says nothing about whether a task works there: check that in the browser. Takes app slugs as listed at https://cotlet.dev/api/v1/apps. Free. Needs the user's Cotlet API key or sign-in.
Inputs: apps (required), use_case.
Returns a one-time upload_url and a file_id for a local file (an image for a post, an attachment). The file is sent to upload_url with an HTTP PUT; an argument that takes a file accepts {"file_id": "..."}. Up to 25 MB, the URL works once. Free. Needs the user's Cotlet API key or sign-in.
Inputs: name, content_type.
The Cotlet account this connection acts as: email, workspace, access status, the API key or OAuth client in use with its scope, the apps the workspace may call and its credit balance. Free. Needs the user's Cotlet API key or sign-in.
Inputs: no named parameters.
Book an appointment for a client: services, team member and start time. Books the services one after another from start_at with one team member at one location, as New appointment in the calendar does, at each service's catalogue price. Give service_ids (service_id from list_services), or pricing_level_ids to pick a pricing level other than a service's first. In a business with several locations, pass location_id and a team member who works there (location_ids in list_team_members); without it the team member's primary location is used. Fresha may send the client a booking confirmation by their notification settings (get_client), so this can reach the client. Find free times with find_available_slots first: Fresha books over other appointments and returns its warnings. By default you confirm each call; you can switch that off for this tool. Waits for the owner's approval.
Inputs: start_at (required), client_id, location_id, service_ids, +2 more.
Free start times for one or more services with a team member, day by day. Asks the calendar for free start times as New appointment does, for the services done one after another, with one team member at one location, over up to 14 days. Give service_ids (service_id from list_services), or pricing_level_ids to pick a pricing level other than a service's first. In a business with several locations, pass location_id and a team member who works there (location_ids in list_team_members); without it the team member's primary location is used. Times are wall clock in the business's time zone; closed days have no times. Book a time with create_appointment, with the same team member and location.
Inputs: date (required), days, location_id, service_ids, +2 more.
Create appointment in the user's own Fresha account from ChatGPT, Claude or any AI agent. Returns how to do it in Fresha step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Fresha Cloud Browser. Fresha's official API: Fresha has no public API and no developer docs (checked 11 Oct 2026).
Inputs: no named parameters.
Get sales summary in the user's own Fresha account from ChatGPT, Claude or any AI agent. Returns how to do it in Fresha step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Fresha Cloud Browser. Fresha's official API: Fresha has no public API and no developer docs (checked 11 Oct 2026).
Inputs: no named parameters.
List appointments in the user's own Fresha account from ChatGPT, Claude or any AI agent. Returns how to do it in Fresha step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Fresha Cloud Browser. Fresha's official API: Fresha has no public API and no developer docs (checked 11 Oct 2026).
Inputs: no named parameters.
List clients in the user's own Fresha account from ChatGPT, Claude or any AI agent. Returns how to do it in Fresha step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Fresha Cloud Browser. Fresha's official API: Fresha has no public API and no developer docs (checked 11 Oct 2026).
Inputs: no named parameters.
Reschedule appointment in the user's own Fresha account from ChatGPT, Claude or any AI agent. Returns how to do it in Fresha step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Fresha Cloud Browser. Fresha's official API: Fresha has no public API and no developer docs (checked 11 Oct 2026).
Inputs: no named parameters.
One appointment: client, services, team member, times, status, price and notes. Reads the appointment as its drawer in the calendar shows it: status, start and end (wall clock in the business's time zone), the client, each booked service with its team member and length, the total and what is left to pay, and the appointment notes.
Inputs: appointment_id (required).
One client: contact, notification settings, booking stats, upcoming appointments, notes. Reads the client profile as the client's page shows it: name, email, mobile, gender, birthday, whether Fresha sends them appointment messages and marketing by email, SMS and WhatsApp, booking and sales totals, the next 10 appointments and the latest 10 notes.
Inputs: client_id (required).
Sales summary for a period: sales, refunds, discounts, taxes and payments by type. Reads Reports > Sales summary for the days given: one row per sale type (services, products, memberships, gift cards and so on) with Fresha's own columns (gross and net sales, discounts, refunds, taxes) and a totals row. columns names each key. A period without sales has no rows. Amounts are in the business's currency.
Inputs: from (required), to.
Appointments in a date range, with client, service, team member, price and status. Lists appointments that start between from and to (both days included; from defaults to today, to to from) as Sales > Appointments shows them, latest first: one row per booked service with its appointment id, reference, start (wall clock in the business's time zone), length, client, team member, price, status and channel (online or offline). Cancelled appointments are included with their status. location_id keeps one location of a business with several. Page with next_cursor. The report itself has no status, team member or client filter, so those three apply to the first 100 rows of the date range: for a busy range, narrow the dates.
Inputs: to, from, limit, cursor, +4 more.
Clients of the business, searchable by name, email or phone. Lists clients as the Client list shows them, newest first by default, with email, mobile, gender, total sales, review count and whether they are blocked. search matches name, email or phone. total is the number of matching clients. Page with next_cursor.
Inputs: sort, limit, cursor, search.
Client reviews of the business with rating, text and replies. Lists reviews as Online reputation shows them, newest first: star rating, text, author, the client and appointment it is about, source (Fresha or Google) and the replies. Filter by rating, source, words or reviews still without a reply. Page with next_cursor.
Inputs: limit, cursor, search, source, +2 more.
Sales (invoices) in a date range: number, date, client, status and totals. Lists sales as Sales > Sales list shows them for the days given, one row per sale with Fresha's columns (sale number, date, client, status, gross total and so on; linked records come with an _id). Amounts are in the business's currency. Page with next_cursor.
Inputs: from (required), to, limit, cursor.
Services of the business with category, duration and price. Lists the active services of one location as the Catalogue shows them, with their category, duration in minutes, price and whether clients can book them online. A business with several locations: pass location_id (from list_team_members) and use the same location_id when you book. A service with several prices (by length or level) lists each as a pricing level; service_ids book the first one, pricing_level_ids a chosen one. Use service_id in find_available_slots and create_appointment.
Inputs: search, location_id.
Team members with role, contact, services they do and whether they take bookings. Lists the team as Team members shows it: name, email, mobile, role (owner, manager, basic), job title, whether they take bookings and online bookings, the services assigned to them, their primary location (location_id) and every location they work at (location_ids). Also lists the business's locations. Use team_member_id in the calendar tools, with location_id set to one of that member's location_ids when the business has several.
Inputs: location_id, include_former.
Post a public reply to a client's review. Posts a reply under the review as Reply in Online reputation does, signed as the business or the team member. The reply is public on the business's Fresha page and the client is told, so this reaches people. It needs a review that exists: take review_id from list_reviews. By default you confirm each call; you can switch that off for this tool. Waits for the owner's approval.
Inputs: text (required), review_id (required), reply_as.
Move an appointment to a new start time, optionally to another team member. Moves every service of the appointment by the same amount so the first starts at start_at, as Reschedule in the appointment drawer does; lengths and prices stay. team_member_id moves all services to that team member, who must work at the appointment's location (location_ids in list_team_members); the location itself stays. With notify_client (default true) Fresha sends the client a reschedule message by their notification settings; false moves it quietly. Cancelled, completed and no-show appointments are refused. By default you confirm each call; you can switch that off for this tool. Waits for the owner's approval.
Inputs: start_at (required), appointment_id (required), notify_client, team_member_id.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Phorest MCP server for ChatGPT, Claude and any AI agent: book appointment, reschedule appointment, list clients, find free slots and add client note in your own Phorest account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Phorest yourself; Cotlet does not store your password and you need no Phorest API key. About the official Phorest API: Phorest has an API, but credentials come only through Phorest Support with your account number, and Phorest says integration needs your own development team (checked 8 Nov 2026). It has no webhooks and no official MCP server. Setup and FAQ: https://cotlet.dev/integrations/phorest-api-mcp-server
Salonized MCP server for ChatGPT, Claude and any AI agent: list appointments, book appointment, find customer, add customer note and get sales report in your own Salonized account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Salonized yourself; Cotlet does not store your password and you need no Salonized API key. About the official Salonized API: Salonized has no public API, webhooks or MCP server (checked 31 Oct 2026). Its help center has no article on any of them, and the only public endpoints, a 2018 wiki page, serve the online booking widget. Setup and FAQ: https://cotlet.dev/integrations/salonized-api-mcp-server
GlossGenius MCP server for ChatGPT, Claude and any AI agent: list appointments, book appointment, reschedule appointment, find client and get sales summary in your own GlossGenius account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to GlossGenius yourself; Cotlet does not store your password and you need no GlossGenius API key. About the official GlossGenius API: GlossGenius has no public API, developer docs, webhooks or MCP server (checked 24 Oct 2026). Its help center says it offers no direct integrations with accounting or reporting tools; data leaves only as reports and a client list CSV you download by hand. Setup and FAQ: https://cotlet.dev/integrations/glossgenius-api-mcp-server
Salonist MCP server for ChatGPT, Claude and any AI agent: book appointment, reschedule appointment, list clients, create bill and assign package in your own Salonist account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Salonist yourself; Cotlet does not store your password and you need no Salonist API key. About the official Salonist API: Salonist lists API access and custom integrations only on its top Expert plan, and its public API covers mainly booking widget calls (checked 8 Nov 2026). It has no official MCP server. Setup and FAQ: https://cotlet.dev/integrations/salonist-api-mcp-server
Add one secure layer between your agents and this server.
