Local services & SaaS
Fresha
Appointments, clients, sales and reviews for salons and spas.
17 endpoints
Pikit publishes no public API and no MCP server (checked 16 Nov 2026). Cotlet runs a hosted Pikit MCP server with 14 tools that ChatGPT and Claude use in your own Pikit dashboard. Texts, booking changes and checkouts wait for your OK.
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Pikit. Pikit is a trademark of its owner. If Pikit's own integrations cover what you need, use them first.
14 tools Read and write
Pikit publishes no public API: no developer docs, API key page or API pricing was found on its site, and pikit.io/api and pikit.io/developers return 404. Its integrations connect calendars, Stripe payments, Twilio texting and site tracking. No Pikit MCP server and no official ChatGPT or Claude connector was verified.
| What you need | Pikit integrations | By hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to do the work | No MCP server | Copy and paste | Hosted MCP server |
| See appointments outside Pikit | Calendar sync, ICS feed | In the dashboard | Read and change, after your OK |
| Clients, texts, stock and checkout | Not covered | One screen at a time | 14 tools, writes after your OK |
| Run from n8n or a script | No public API | Manual only | REST, same key |
Checked 16 Nov 2026. Sources: Pikit features · Pikit pricing · Integrations · Online Booking · Calendar & Front Desk · Appointment Reminders · Payments & Deposits · Gift Cards · Products & Inventory · Client Management · Staff Management · Form Builder · Reports & Analytics · SMS Messaging · Website Builder · Pikit AI · SEO Agent
Once, in a browser we host for you.
One address in its settings.
It drafts the reply, you approve the send.
Your agent works in your own signed-in Cloud Browser. Texts, booking changes and checkouts wait for your OK. Who can see your session
Sign in to Pikit in a Cloud Browser. Open app.pikit.io in your Cotlet Cloud Browser and sign in with your own Pikit user.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
Pikit shares the address https://cotlet.dev/mcp/v1 with every other app you enable, so one connector covers them all. Turned Pikit on after connecting? Refresh the connector and the 14 Pikit tools appear.
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth 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/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: pikit_read One tool per Pikit feature. Most take an `action`: `list` and `get` only read, the other actions write and ask first.
Front Desk, the calendar and the waitlist. Changes send clients the emails your settings turn on.
Returns today's appointments with client, service, staff member and visit status. Nothing is changed.
MCP callpikit_read → view_front_desk
REST endpointGET https://cotlet.dev/api/v1/pikit/front-desks/view
| Name | Type | Description |
|---|---|---|
| location string | string | For a business with several locations. |
{
"date": "2026-11-17",
"queue": [
{
"time": "10:00",
"client": "Example Client",
"service": "Cut and blow-dry",
"staff": "Stylist A",
"status": "Arrived"
},
{
"time": "10:30",
"client": "Sample Client",
"service": "Color refresh",
"staff": "Stylist B",
"status": "Expected"
}
]
} Availability follows business hours, staff schedules, days off and holiday closures. Changes and cancellations send the client the emails your notification settings turn on, so the agent names the client and time before it saves. By default you confirm each call; you can switch that off for this tool.
MCP callpikit_write → manage_appointments
REST endpointPOST https://cotlet.dev/api/v1/pikit/appointments/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `reschedule`, `cancel`, `set_status`. `list` and `get` only read. |
| appointment string | string | For every action but `list` and `create`. |
| date string | string | ISO date and time, or the day for `list`. |
| client string | string | Client name, phone or email, as manage_clients `list` returns it. |
| service string | string | Service from your menu. |
| staff string | string | Staff member. |
| status string | string | For `set_status`, as Front Desk shows it. |
{
"action": "action"
} {
"appointment": "APT-48211",
"date": "2026-11-19T14:00",
"client": "Example Client",
"service": "Color refresh",
"staff": "Stylist B",
"status": "Booked"
} An offer or invitation reaches the client, who claims the opening or finishes a guided booking themselves. By default you confirm each call; you can switch that off for this tool.
MCP callpikit_write → manage_waitlist
REST endpointPOST https://cotlet.dev/api/v1/pikit/waitlist/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `offer_opening`, `send_smart_booking`. `list` and `get` only read. |
| client string | string | Client name, phone or email, as manage_clients `list` returns it. |
| opening string | string | For `offer_opening`: ISO date and time. |
| service string | string | Service the invitation is for. |
{
"action": "action"
} {
"waitlist": [
{
"client": "Sample Client",
"service": "Balayage",
"wants": "Saturday morning"
}
]
} Client profiles with history, notes and tags, intake forms, and the Pikit Messages inbox.
`get` returns the client's appointment history and notes. Reference photos are added in Pikit itself. By default you confirm each call; you can switch that off for this tool.
MCP callpikit_write → manage_clients
REST endpointPOST https://cotlet.dev/api/v1/pikit/clients/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `update`, `add_note`, `tag`. `list` and `get` only read. |
| client string | string | Client name, phone or email, as manage_clients `list` returns it. |
| fields object | object | name, phone, email. |
| text string | string | For `add_note`, or the tag. |
{
"action": "action"
} {
"client": "Example Client",
"visits": 6,
"last_visit": "2026-10-22",
"tags": [
"Color"
],
"notes": 1
} Clients answer through Pikit's public form link or a form section on a Pikit-built site. By default you confirm each call; you can switch that off for this tool.
MCP callpikit_write → manage_forms
REST endpointPOST https://cotlet.dev/api/v1/pikit/forms/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `submissions`, `create`. `list` and `get` only read. |
| form string | string | Form name. |
| questions array | array | For `create`. |
{
"action": "action"
} {
"form": "New client questionnaire",
"submissions": [
{
"client": "Example Client",
"submitted": "2026-11-15"
}
]
} Two-way SMS needs an eligible business number, and each message uses the account's message allowance. A sent text cannot be pulled back. By default you confirm each call; you can switch that off for this tool.
MCP callpikit_write → send_sms
REST endpointPOST https://cotlet.dev/api/v1/pikit/sms
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `send`. `list` and `get` only read. |
| client string | string | Client name, phone or email, as manage_clients `list` returns it. |
| text string | string | For `send`. |
{
"action": "action"
} {
"client": "Example Client",
"text": "Hi, a 2 pm slot opened on Thursday. Want it?",
"sent": false
} Checkout with cash or a saved card, gift cards, products, restocks and reports.
Checkout takes money, so the agent shows the order, any deposit already paid and the balance first. By default you confirm each call; you can switch that off for this tool.
MCP callpikit_write → checkout_visit
REST endpointPOST https://cotlet.dev/api/v1/pikit/visit/checkout
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list_payments`, `checkout`. `list` and `get` only read. |
| appointment string | string | For `checkout`. |
| products array | array | Retail products added to the order. |
| gift_card string | string | Gift card code to redeem. |
| method string | string | `cash` or `saved_card`. Card-present Stripe Terminal payments stay at the desk. |
{
"action": "checkout",
"appointment": "APT-48211",
"products": [
"Repair shampoo, 250 ml"
],
"gift_card": "GC-7Q4M",
"method": "saved_card"
} {
"appointment": "APT-48211",
"service": 140,
"products": 28,
"deposit_paid": 40,
"gift_card": 50,
"balance": 78,
"method": "saved_card",
"paid": false
} Gift cards depend on your plan. Redeeming happens at checkout through checkout_visit. By default you confirm each call; you can switch that off for this tool.
MCP callpikit_write → manage_gift_cards
REST endpointPOST https://cotlet.dev/api/v1/pikit/gift-cards/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `issue`. `list` and `get` only read. |
| code string | string | For `get`. |
| amount number | number | For `issue`. |
| recipient string | string | For `issue`: who the card is for. |
{
"action": "action"
} {
"code": "GC-7Q4M",
"amount": 100,
"redeemed": 50,
"remaining": 50
} Each restock or adjustment is kept as an inventory movement, so a wrong count is corrected with another adjustment. By default you confirm each call; you can switch that off for this tool.
MCP callpikit_write → manage_inventory
REST endpointPOST https://cotlet.dev/api/v1/pikit/inventory/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `restock`, `adjust`. `list` and `get` only read. |
| product string | string | Product, and variant where it has one. |
| quantity number | number | For `restock` and `adjust`. |
| fields object | object | For `create`: category, variants, price. |
{
"action": "action"
} {
"product": "Repair shampoo, 250 ml",
"in_stock": 3,
"restocked": 12,
"now": 15
} Report availability can depend on your plan. Nothing is changed.
MCP callpikit_read → view_reports
REST endpointGET https://cotlet.dev/api/v1/pikit/reports/view
| Name | Type | Description |
|---|---|---|
| report string required | string | Report name as Pikit lists it, for example bookings, cancellations, sales, refunds, cash flow, gift cards, time clock, inventory. |
| from string | string | ISO start date. |
| to string | string | ISO end date. |
{
"report": "report"
} {
"report": "cancellations",
"from": "2026-11-01",
"to": "2026-11-15",
"rows": [
{
"staff": "Stylist A",
"cancelled": 4
},
{
"staff": "Stylist B",
"cancelled": 1
}
]
} Services, booking rules, reminder emails, staff hours and your Pikit-built site. Each change shows before it saves.
These settings change what every client sees on your booking page and widget, so the agent shows the change before saving. By default you confirm each call; you can switch that off for this tool.
MCP callpikit_write → configure_online_booking
REST endpointPOST https://cotlet.dev/api/v1/pikit/online-booking/configure
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list_services`, `update_service`, `set_payment_mode`, `set_rules`. `list` and `get` only read. |
| service object | object | For `update_service`: category, name, duration, price, pricing tier, staff. |
| payment_mode string | string | `pay_later`, `deposit` or `full_payment`. Online payment modes need a connected Stripe account. |
| rules object | object | Cancellation and rescheduling rules, and which self-service changes clients may make. |
{
"action": "action"
} {
"service": "Color refresh",
"duration_minutes": 90,
"price": 140,
"staff": [
"Stylist B"
],
"saved": true
} Email is the reliable channel; appointment SMS depends on account configuration, Pikit says. These emails reach every client with an appointment. By default you confirm each call; you can switch that off for this tool.
MCP callpikit_write → configure_notifications
REST endpointPOST https://cotlet.dev/api/v1/pikit/notifications/configure
| Name | Type | Description |
|---|---|---|
| template string required | string | `confirmation`, `reminder`, `update`, `cancellation` or `feedback`. |
| enabled boolean | boolean | Turn the email on or off. |
| text string | string | Wording, with Pikit's appointment variables. |
| review_link string | string | For `feedback`: your Google or Yelp review page. |
{
"template": "template"
} {
"template": "reminder",
"enabled": true,
"saved": true
} Staff hours drive online booking availability. Permission groups stay as you set them in Pikit. By default you confirm each call; you can switch that off for this tool.
MCP callpikit_write → manage_staff
REST endpointPOST https://cotlet.dev/api/v1/pikit/staff/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `set_schedule`, `add_exception`, `assign_services`, `invite`. `list` and `get` only read. |
| staff string | string | Staff member. |
| schedule object | object | Working hours per weekday, or the exception dates. |
| services array | array | For `assign_services`. |
| email string | string | For `invite`. |
{
"action": "action"
} {
"staff": "Stylist B",
"exception": {
"date": "2026-11-28",
"off": true
},
"saved": true
} Website Builder depends on your plan or add-on. Publishing makes the change public, so it is a separate call after you read the edit. By default you confirm each call; you can switch that off for this tool.
MCP callpikit_write → edit_website
REST endpointPATCH https://cotlet.dev/api/v1/pikit/website
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `edit`, `publish`. `list` and `get` only read. |
| page string | string | Page name. |
| changes string | string | For `edit`: what to change, in plain words. |
{
"action": "action"
} {
"page": "Services",
"edited": true,
"published": false
} Your signed-in Pikit browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 14 Pikit tools. The session cookie stays in the Cloud Browser.
The dashboard areas your Pikit permission group opens, and nothing more.
Permission groups, your Stripe and Twilio setup, card readers, refunds and your Pikit subscription.
You sign in again yourself, in the same Cloud Browser.
Disable Pikit for agents, reset the browser, or change your Pikit password.
Cotlet never sees or stores your password: you type it yourself, or use your Google sign-in, and the agent only uses the session it leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
| Action | How to put it right |
|---|---|
| Client fields, notes, staff hours | Call the same tool again with the earlier values |
| Stock count | Record another adjustment with manage_inventory |
| Moved appointment | Move it back; the client gets the update email again |
| Sent text or completed checkout | Already with the client: talk to them, refund in Pikit |
All 12 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 2 read tools, the front desk and reports, run at once.
{
"name": "checkout_visit",
"arguments": {
"action": "checkout",
"appointment": "APT-48211",
"products": [
"Repair shampoo, 250 ml"
],
"gift_card": "GC-7Q4M",
"method": "saved_card"
}
} curl -X POST https://cotlet.dev/api/v1/pikit/visit/checkout \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"action":"checkout","appointment":"APT-48211","products":["Repair shampoo, 250 ml"],"gift_card":"GC-7Q4M","method":"saved_card"}' {
"appointment": "APT-48211",
"service": 140,
"products": 28,
"deposit_paid": 40,
"gift_card": 50,
"balance": 78,
"method": "saved_card",
"paid": false
} The example adds a $28 shampoo to a $140 color refresh, takes off the $40 deposit and $50 of gift card, and leaves $78 to charge after your OK. A cron job or n8n flow can make the same call over REST at /api/v1/pikit with the same key and price, in JSON. Failed calls are free.
About $21 a monthfor a four-chair salon open 26 days, 3,590 credits. Your Pikit plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Morning front desk and intake form check | 2 × 26 | 520 |
| Client texts read and answered | 2 × 26 | 520 |
| Bookings moved or added from chat | 1 × 40 | 400 |
| Cancelled slots offered to the waitlist | 2 × 12 | 240 |
| Checkouts with saved card or cash | 1 × 30 | 300 |
| Monday low stock and restocks | 2 × 4 | 80 |
| Monthly reports | 3 × 1 | 30 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 209 calls | 3,590 |
The smallest pack, 5,000 credits for $29, covers this month. A busier business uses more calls.
Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, not measured customer usage.
| 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.
| Option | What it does | Where it stops |
|---|---|---|
| Google or Outlook calendar, ICS feed | Shows Pikit appointments in a staff member's calendar. | Calendar only; the ICS feed is read only. |
| Pikit AI | Pikit's staff assistant inside the dashboard. | Inside Pikit; no ChatGPT or Claude connector was verified. |
| WordPress plugin and booking widget | Puts Pikit booking on your own site. | Booking only; the desk work stays in Pikit. |
| By hand | Open each booking, message and product in Pikit. | One screen at a time, between clients. |
Keep Pikit's calendar sync and booking widget: they are its own routes. Cotlet fits the desk work around them, when you want ChatGPT, Claude or a script working in Pikit from your own login, with nothing to host.
Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Pikit tools.
Sign up free at https://cotlet.dev/signup?app=pikit, turn on Pikit under Integrations in the console and sign in at https://app.pikit.io/login in your Cloud Browser. Then connect your AI agent and ask it about today's front desk. The trial needs no card.
Pikit publishes no public API: no developer docs, API key page or API pricing was found on its site (checked 16 Nov 2026). Its integrations are calendar, Stripe, Twilio and tracking connections. No Pikit MCP server and no official ChatGPT or Claude connector was verified. Cotlet does not need one: it works in your own signed-in Pikit account.
Pikit AI is Pikit's own staff assistant inside the dashboard, and the SEO Agent is its add-on for Pikit-built sites. Cotlet is separate: it lets ChatGPT, Claude or a script you choose work in your Pikit account over MCP or REST.
No. Card-present payments on a Stripe Terminal reader stay with your front desk. checkout_visit closes a visit with cash or a saved card, after your OK.
A manager or front desk user whose permission group covers the jobs. The agent sees only the dashboard areas that group opens.
Only in how it is called. Both carry the same 14 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
No. Cotlet is independent and not affiliated with Pikit.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy