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

# Pikit API and MCP server: Let your AI agent keep the front desk moving.

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

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.

- Free 7-day trial, no card
- Unofficial, not affiliated with Pikit
- Page: https://cotlet.dev/integrations/pikit-api-mcp-server

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

## What can your AI agent do in Pikit?

- Fill a cancelled slot from the waitlist
- Start the day from the front desk queue
- Answer client texts for your OK
- Restock retail products
- Review cancellations by staff member
- Block a staff day off and move bookings

## Does Pikit have an MCP server or an API?

- Pikit AI is Pikit's own staff assistant in the dashboard; the SEO Agent is an add-on for Pikit-built sites.
- Calendars: Google and Outlook connections, and a read-only ICS feed for Apple Calendar.
- Online payments run on Stripe Connect; two-way SMS runs on a Twilio-backed business number.

| 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](https://pikit.io/features), [Pikit pricing](https://pikit.io/us/pricing), [Integrations](https://pikit.io/us/features/integrations), [Online Booking](https://pikit.io/us/features/online-booking), [Calendar & Front Desk](https://pikit.io/us/features/calendar), [Appointment Reminders](https://pikit.io/us/features/appointment-reminders), [Payments & Deposits](https://pikit.io/us/features/payments), [Gift Cards](https://pikit.io/us/features/gift-cards), [Products & Inventory](https://pikit.io/us/features/inventory), [Client Management](https://pikit.io/us/features/client-management), [Staff Management](https://pikit.io/us/features/staff-management), [Form Builder](https://pikit.io/us/features/form-builder), [Reports & Analytics](https://pikit.io/us/features/reports), [SMS Messaging](https://pikit.io/us/features/sms-messaging), [Website Builder](https://pikit.io/us/features/website-builder), [Pikit AI](https://pikit.io/us/features/pikit-ai), [SEO Agent](https://pikit.io/us/features/seo-agent)

## How does the Pikit MCP server work?

1. **Sign in to Pikit.** Once, in a browser we host for you.
2. **Connect your AI agent.** One address in its settings.
3. **Hand it the desk work.** 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.

## How to connect Pikit to your AI agent

1. **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.
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.

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.

ChatGPT:

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

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

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

## All 14 Pikit MCP tools

One tool per Pikit feature. Most take an `action`: `list` and `get` only read, the other actions write and ask first.

### The day's bookings

Front Desk, the calendar and the waitlist. Changes send clients the emails your settings turn on.

- **Read the front desk queue** (`view_front_desk`, read): Read today's Front Desk queue: who is expected, who has arrived, who needs checkout.
- **Book, move and cancel appointments** (`manage_appointments`, write, asks first): List the calendar, create an appointment, move or cancel it, or change its status.
- **Offer waitlist openings** (`manage_waitlist`, write, asks first): Read the waitlist, offer an opening, or send a client a Smart Booking invitation.

### Clients and messages

Client profiles with history, notes and tags, intake forms, and the Pikit Messages inbox.

- **Add clients, notes and tags** (`manage_clients`, write, asks first): Search clients and read their visit history, or add a client, a note or a tag.
- **Build forms and read submissions** (`manage_forms`, write, asks first): List forms and their submissions, or create a form with your own questions.
- **Text clients** (`send_sms`, write, asks first): Read conversations in Pikit Messages, or text a client from the business number.

### Money and stock

Checkout with cash or a saved card, gift cards, products, restocks and reports.

- **Check out visits** (`checkout_visit`, write, asks first): Read payment history, or close a visit at checkout with cash or a saved card.
- **Issue and redeem gift cards** (`manage_gift_cards`, write, asks first): List gift cards with balances, or issue a new one.
- **Restock products** (`manage_inventory`, write, asks first): List products and stock, add a product or variant, or record a restock or adjustment.
- **Read reports** (`view_reports`, read): Run a Pikit report on appointments, sales, gift cards, staff time or inventory.

### Settings that clients see

Services, booking rules, reminder emails, staff hours and your Pikit-built site. Each change shows before it saves.

- **Set services and booking rules** (`configure_online_booking`, write, asks first): Edit the service menu, booking payment mode and cancellation and rescheduling rules.
- **Set reminders and feedback emails** (`configure_notifications`, write, asks first): Edit the confirmation, reminder, change and cancellation emails and the post-visit feedback request.
- **Set staff schedules** (`manage_staff`, write, asks first): List staff, set working hours and exceptions, assign services, or invite a staff member.
- **Edit website pages** (`edit_website`, write, asks first): Edit the text of a Pikit-built website page and publish it.

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

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

- **What we store.** Your signed-in Pikit browser profile, AES-256-GCM encrypted, in Finland. Never your password.
- **What your agent gets.** The 14 Pikit tools. The session cookie stays in the Cloud Browser.
- **What the session sees.** The dashboard areas your Pikit permission group opens, and nothing more.
- **What no tool touches.** Permission groups, your Stripe and Twilio setup, card readers, refunds and your Pikit subscription.
- **If Pikit signs you out.** You sign in again yourself, in the same Cloud Browser.
- **How to cut access.** 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](https://cotlet.dev/security.md)).

## Approvals, undo and mistakes

1. **Read the visit.** view_front_desk finds it in the checkout column.
2. **Show you the order.** Service, products, deposit and gift card.
3. **Wait for your OK.** The balance is what gets charged.
4. **Check out.** checkout_visit closes the visit.

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

MCP call:

```
{
  "name": "checkout_visit",
  "arguments": {
    "action": "checkout",
    "appointment": "APT-48211",
    "products": [
      "Repair shampoo, 250 ml"
    ],
    "gift_card": "GC-7Q4M",
    "method": "saved_card"
  }
}
```

REST:

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

Response:

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

## How much does the Pikit MCP server cost?

**About $21 a month** for 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.

- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Your Pikit plan and permissions apply as they are

Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, not measured customer usage.

## Pikit MCP server: other ways to connect

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

## Who runs Cotlet

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.

## Pikit MCP server: questions

### How do I get access?

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.

### Does Pikit have an API?

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.

### How is this different from Pikit AI?

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.

### Can the agent take a card payment at the desk?

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.

### Which Pikit user should I sign in with?

A manager or front desk user whose permission group covers the jobs. The agent sees only the dashboard areas that group opens.

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

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.

### Is Cotlet affiliated with Pikit?

No. Cotlet is independent and not affiliated with Pikit.

---

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.
