Local services & SaaS
Squire
Appointments, barbers, clients, waitlist and reports for your barbershop.
11 endpoints
NextSessio publishes no public API and no MCP server (checked 15 Nov 2026). Cotlet runs a hosted NextSessio MCP server with 6 tools that ChatGPT and Claude use in your own merchant dashboard. Verifying visits, new packages and staff hours wait for your OK.
6 tools Read and write
NextSessio publishes no public API, no developer documentation and no API keys. No NextSessio MCP server and no official ChatGPT or Claude connector was found.
| What you need | NextSessio API | By hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude about your clients | No API or MCP server | Copy and paste | Hosted MCP server |
| Credits left on every package | Not available | Client by client | One list, filtered |
| Weekly check from n8n or a script | Not available | Only when you look | REST, same key |
Checked 15 Nov 2026. Sources: NextSessio llms.txt · NextSessio pricing (Markdown) · NextSessio home · Feature: prepaid packages · Feature: verification codes · Feature: multi-staff scheduling · Feature: guest checkout · Feature: Stripe Connect payouts
Once, in a browser we host for you.
One address in its settings.
Who is low on credits, who is in today.
Your agent works in your own signed-in Cloud Browser. Verifying a visit uses a client's credit, so it waits for your OK, like new packages and staff hours. Who can see your session
Sign in to NextSessio in a Cloud Browser. Open nextsessio.com/login in your Cotlet Cloud Browser and sign in to your merchant dashboard with email or Google.
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.
NextSessio shares the address https://cotlet.dev/mcp/v1 with the other apps you turn on, so one connector covers them all. Turned NextSessio on later? Refresh the connector to see its 6 tools.
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: nextsessio_read Built around the NextSessio workflow: sell a pack, clients book with credits, you verify each visit with its code.
The dashboard's bookings, marked confirmed, credit or walk-in, and each team member's hours and services.
Returns each booking with its time, client, service and staff member, and whether it is a confirmed booking, a package credit booking or a walk-in, as the dashboard shows them. Read only.
MCP callnextsessio_read → view_business_dashboard
REST endpointGET https://cotlet.dev/api/v1/nextsessio/business-dashboards/view
| Name | Type | Description |
|---|---|---|
| date string | string | ISO date. Defaults to today. |
| staff string | string | One team member. Leave empty for the whole shop. |
{
"date": "2026-11-16",
"bookings": [
{
"time": "09:00",
"client": "Client A",
"service": "Haircut",
"staff": "Barber 1",
"status": "Confirmed"
},
{
"time": "11:30",
"client": "Client B",
"service": "Package",
"staff": "Barber 2",
"status": "Credit"
},
{
"time": "16:30",
"client": "Walk-in",
"service": "Haircut",
"staff": "Barber 1",
"status": "Walk-in"
}
],
"total": 3
} Each team member in NextSessio has their own availability and services, and clients pick their provider from one booking page. Changed hours change the times clients can book, so the agent shows the change first. By default you confirm each call; you can switch that off for this tool.
MCP callnextsessio_write → manage_staff_schedules
REST endpointPOST https://cotlet.dev/api/v1/nextsessio/staff-schedules/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `update`. `get` only reads. |
| staff string required | string | Team member name. |
| hours object | object | For `update`: working hours per weekday, and days off. |
| services array | array | For `update`: the services this person takes. |
{
"action": "action",
"staff": "staff"
} {
"staff": "Barber 2",
"hours": {
"sat": "09:00-14:00",
"sun": "off"
},
"services": [
"Haircut",
"Beard trim"
],
"saved": true
} The offers on your booking page and the credits each client has left. A new package waits for your OK.
NextSessio tracks credits per client, including bonus sessions, and links them to the client's email. Clients buy a new pack from your booking page when credits run out, so this is the list to check before they do. Read only.
MCP callnextsessio_read → track_package_balances
REST endpointGET https://cotlet.dev/api/v1/nextsessio/package-balances/track
| Name | Type | Description |
|---|---|---|
| max_credits number | number | Only clients with this many credits or fewer, for example 1 to find packs about to run out. |
| client string | string | One client by name or email. |
{
"clients": [
{
"client": "Client B",
"email": "client.b@example.com",
"package": "5-cut package",
"credits_left": 1
},
{
"client": "Client C",
"email": "client.c@example.com",
"package": "10-cut pack + 1 free",
"credits_left": 0
}
]
} A new package appears on your public booking page, where clients buy it and the money goes to your own Stripe account through Stripe Connect. The agent shows name, sessions, bonus and price before it saves. By default you confirm each call; you can switch that off for this tool.
MCP callnextsessio_write → sell_session_packages
REST endpointPOST https://cotlet.dev/api/v1/nextsessio/session-packages/sell
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. `list` only reads. |
| name string | string | For `create`: the package name clients see, for example 5-cut package. |
| service string | string | For `create`: the service the credits book. |
| sessions number | number | For `create`: number of sessions. |
| bonus_sessions number | number | For `create`: free sessions on top. |
| price number | number | For `create`: package price. |
| expiry string | string | For `create`: optional expiry, as NextSessio offers it. |
{
"action": "action"
} {
"package": "5-cut package",
"service": "Haircut",
"sessions": 5,
"bonus_sessions": 0,
"price": 110,
"saved": true
} Verify a 6-digit code or redeem a walk-in credit, and fetch the link clients book from.
Verifying marks the visit complete and deducts one package credit in the same step. A walk-in redemption creates a visit with its own code. Credits are money the client paid in advance, so each call waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callnextsessio_write → verify_session_visits
REST endpointPOST https://cotlet.dev/api/v1/nextsessio/session-visits/verify
| Name | Type | Description |
|---|---|---|
| code string | string | The 6-digit visit code the client shows on arrival. |
| walk_in_client string | string | Instead of a code: the email of a package client who walked in, to redeem one credit. |
{
"code": "482917"
} {
"code": "482917",
"client": "Client B",
"service": "Haircut",
"verified": true,
"credits_left": 0
} Your signed-in NextSessio browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 6 NextSessio tools. The session cookie stays in the Cloud Browser.
Your merchant dashboard: bookings, clients, packages, credits and staff schedules.
Your Stripe account and payouts, your NextSessio subscription, and refunds.
You sign in again yourself, in the same Cloud Browser.
Disable NextSessio for agents, reset the browser, or change your NextSessio password.
Cotlet never sees or stores your password. You sign in yourself, with email and password or with Google, and the agent only uses the session that sign-in leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Cotlet watches the apps it serves and updates the NextSessio server when NextSessio changes its dashboard, so your agent keeps working without a change on your side.
When NextSessio adds features to your plan, the server can add tools for them. Today the tools cover what the Starter plan includes: bookings, packages, credits, visit codes and staff schedules.
If NextSessio signs you out, one click in the Cotlet console reopens the Cloud Browser so you can sign in again.
| Action | How to put it right |
|---|---|
| Staff hours changed | Call manage_staff_schedules again with the earlier hours |
| Package created by mistake | Change it in the NextSessio dashboard before a client buys it |
| Wrong visit verified | The credit is already used: sort it out with the client |
All 3 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 3 read tools run at once and never move a credit.
{
"name": "verify_session_visits",
"arguments": {
"code": "482917"
}
} curl -X POST https://cotlet.dev/api/v1/nextsessio/session-visits/verify \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"code":"482917"}' {
"code": "482917",
"client": "Client B",
"service": "Haircut",
"verified": true,
"credits_left": 0
} The example verifies code 482917 for Client B, who used the last credit of a 5-cut package. A script or n8n flow can make the same call over REST at /api/v1/nextsessio with the same key and price, in JSON. Failed calls are free.
About $18 a monthfor a two-chair shop verifying package visits every day, 3,040 credits. Your NextSessio plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Morning look at today's bookings | 1 × 26 | 260 |
| Visit codes verified | 1 × 120 | 1,200 |
| Clients low on credits | 1 × 4 | 40 |
| New package and booking link | 2 × 1 | 20 |
| Staff hours changes | 1 × 2 | 20 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 154 calls | 3,040 |
The smallest pack, 5,000 credits for $29, covers this month. Verifying codes in the dashboard yourself and asking the agent only for the lists costs less.
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 |
|---|---|---|
| NextSessio dashboard | Bookings, packages, credits and visit codes in one place. | You check each client yourself, between appointments. |
| Stripe dashboard | Shows the package payments that reached your Stripe account. | Knows payments, not credits left or visits verified. |
| NextSessio llms.txt | Tells AI assistants what NextSessio is and costs. | Public product facts only, nothing from your account. |
If NextSessio publishes an API that covers your job, use it: it is the vendor's own route. Cotlet fits when you want ChatGPT, Claude or a script working in NextSessio today, from your own sign-in, 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 NextSessio tools.
Sign up free at https://cotlet.dev/signup?app=nextsessio, turn on NextSessio under Integrations in the console and sign in at https://www.nextsessio.com/login in your Cloud Browser. Then connect your AI agent and ask it who is low on credits. The trial needs no card.
NextSessio publishes no public API, developer documentation or API keys (checked 15 Nov 2026). No NextSessio MCP server and no official ChatGPT or Claude connector was found; payments run through Stripe Connect into your own Stripe account. Cotlet does not need one: it works in your own signed-in NextSessio dashboard.
No. NextSessio pays package sales into your own Stripe account through Stripe Connect and takes no platform fee on them. No Cotlet tool opens Stripe, changes payouts or charges a client; the tools work only inside the NextSessio dashboard.
Cotlet signs no BAA and makes no HIPAA claim. The NextSessio tools read bookings, package credits, staff hours and visit codes. No tool opens clinical notes.
In NextSessio any staff member can confirm a code and deduct a credit. Through Cotlet the agent verifies from the merchant dashboard you signed in to, and each verification waits for your OK unless you switch that off.
Only in how it is called. Both carry the same 6 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 NextSessio.
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