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

# NextSessio API and MCP server: Let your AI agent watch every prepaid pack.

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

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.

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

## What can your AI agent do in NextSessio?

- Find clients with one credit left
- Read today's bookings by staff member
- Verify a 6-digit visit code
- Launch a new prepaid package
- Change a team member's hours
- Get the booking link for Instagram

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

- NextSessio publishes an llms.txt and a Markdown price list for AI readers; both describe the product, neither offers an API.
- Package sales settle in your own Stripe account through Stripe Connect, with no NextSessio fee on client payments.
- The Starter plan is $29 a month and includes prepaid packages, multi-staff scheduling and visit codes.

| 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](https://www.nextsessio.com/llms.txt), [NextSessio pricing (Markdown)](https://www.nextsessio.com/pricing.md), [NextSessio home](https://www.nextsessio.com/en), [Feature: prepaid packages](https://www.nextsessio.com/en/features/prepaid-packages), [Feature: verification codes](https://www.nextsessio.com/en/features/verification-codes), [Feature: multi-staff scheduling](https://www.nextsessio.com/en/features/multi-staff-scheduling), [Feature: guest checkout](https://www.nextsessio.com/en/features/guest-checkout), [Feature: Stripe Connect payouts](https://www.nextsessio.com/en/features/stripe-connect-payouts)

## How does the NextSessio MCP server work?

1. **Sign in to NextSessio.** Once, in a browser we host for you.
2. **Connect your AI agent.** One address in its settings.
3. **Ask about your packs.** 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.

## How to connect NextSessio to your AI agent

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

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.

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

## All 6 NextSessio MCP tools

Built around the NextSessio workflow: sell a pack, clients book with credits, you verify each visit with its code.

### Today and the team

The dashboard's bookings, marked confirmed, credit or walk-in, and each team member's hours and services.

- **View the business dashboard** (`view_business_dashboard`, read): Read the day's bookings from the NextSessio dashboard, with staff and status.
- **Manage staff schedules** (`manage_staff_schedules`, write, asks first): Read a team member's hours and services, or change them.

### Packages and credits

The offers on your booking page and the credits each client has left. A new package waits for your OK.

- **Track package balances** (`track_package_balances`, read): List clients with a prepaid package and the credits left on it.
- **Sell prepaid session packages** (`sell_session_packages`, write, asks first): List your package offers or create one for the booking page.

### Visits and the booking page

Verify a 6-digit code or redeem a walk-in credit, and fetch the link clients book from.

- **Verify prepaid session visits** (`verify_session_visits`, write, asks first): Confirm a visit with the client's 6-digit code, or redeem a walk-in credit.
- **Share a booking link** (`share_booking_link`, read): Get your public NextSessio booking page address.

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

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

- **What we store.** Your signed-in NextSessio browser profile, AES-256-GCM encrypted, in Finland. Never your password.
- **What your agent gets.** The 6 NextSessio tools. The session cookie stays in the Cloud Browser.
- **What the session sees.** Your merchant dashboard: bookings, clients, packages, credits and staff schedules.
- **What no tool touches.** Your Stripe account and payouts, your NextSessio subscription, and refunds.
- **If NextSessio signs you out.** You sign in again yourself, in the same Cloud Browser.
- **How to cut access.** 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](https://cotlet.dev/security.md)).

## What happens when NextSessio changes?

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.

## Approvals, undo and mistakes

1. **Client shows a code.** You read the 6 digits to your agent.
2. **Match the booking.** verify_session_visits finds today's visit for it.
3. **Show you the visit.** Client, service and credits before anything changes.
4. **Verify after your OK.** One credit deducted, attendance recorded.

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

MCP call:

```
{
  "name": "verify_session_visits",
  "arguments": {
    "code": "482917"
  }
}
```

REST:

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

Response:

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

## How much does the NextSessio MCP server cost?

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

- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- NextSessio Starter is $29 a month, billed by NextSessio

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

## NextSessio MCP server: other ways to connect

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

## 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 NextSessio tools.

## NextSessio MCP server: questions

### How do I get access?

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.

### Does NextSessio have an API?

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.

### Does the agent touch my Stripe account?

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.

### I run a therapy or massage practice on NextSessio. Is this HIPAA compliant?

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.

### Can a team member verify visits through the agent?

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.

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

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.

### Is Cotlet affiliated with NextSessio?

No. Cotlet is independent and not affiliated with NextSessio.

---

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.
