Skip to main content
Glama
README.md
# NextSessio MCP server

Connect NextSessio to ChatGPT, Claude and any AI agent through Cotlet.dev. Work in your own merchant dashboard with 6 hosted tools for bookings, prepaid packages, visit codes and staff schedules. The 3 write tools ask for approval by default.

## What you can ask

> Show today's bookings by staff member.

> List clients with one package credit left.

> Get my public booking page link.

## Connect in 2 minutes

Get your API key at https://cotlet.dev/app and export it as `COTLET_API_KEY`.

### ChatGPT

Settings → Apps & Connectors → Create, with connector URL `https://cotlet.dev/mcp/v1/connect`, then sign in with Cotlet.dev. No API key needed.

### Claude

Settings → Connectors → Add custom connector, with URL `https://cotlet.dev/mcp/v1/connect`, then sign in with Cotlet.dev.

### Claude Code

```bash
claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"
```

### Cursor

Copy `.cursor/mcp.json` from this repo into your project:

```json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

## Run it locally (stdio)

This repo is a real MCP server. It speaks MCP over stdio, lists its NextSessio tools without any key, and forwards every tool call to the hosted Cotlet.dev server. The hosted URL above stays the recommended way. Use this when your client only starts local servers.

Run the included Python module with Python 3.10 or later:

```bash
python3 nextsessio_agent.py serve
```

Or with Docker:

```bash
docker build -t nextsessio-mcp .
docker run -i --rm -e COTLET_API_KEY nextsessio-mcp
```

Tools: `nextsessio_guide`, `nextsessio_status`, `nextsessio_open`, `nextsessio_read`, `nextsessio_click`, `nextsessio_type`, `nextsessio_close`. Without `COTLET_API_KEY` a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app".

## Command line

Python 3.10+, with no third-party runtime dependencies. Clone this repository and run:

```bash
export COTLET_API_KEY="your-key"
python3 nextsessio_agent.py connect   # ready config for ChatGPT, Claude, Claude Code and Cursor
python3 nextsessio_agent.py status    # is NextSessio ready in your Cotlet.dev account
python3 nextsessio_agent.py guide     # NextSessio screens and sign-in link
python3 nextsessio_agent.py read      # open NextSessio, read the page, close the browser
python3 nextsessio_agent.py tools     # list Cotlet.dev tools
python3 nextsessio_agent.py serve     # start the stdio MCP server (same as no argument)
```

## Questions from NextSessio users

**Which NextSessio account should I connect?**

Sign in at https://www.nextsessio.com/login in your Cotlet Cloud Browser with email or Google, and open your merchant dashboard.

**Which actions ask for approval?**

manage_staff_schedules, sell_session_packages and verify_session_visits ask for approval by default. Verifying a visit deducts a package credit.

**Is Cotlet affiliated with NextSessio?**

No. Cotlet.dev is independent and not affiliated with NextSessio.

## Learn more

- [NextSessio integration and hosted tools](https://cotlet.dev/integrations/nextsessio-api-mcp-server)

---

More: https://cotlet.dev/integrations/nextsessio-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=nextsessio

Request access: https://cotlet.dev/signup?app=nextsessio&utm_source=github&utm_medium=readme&utm_campaign=nextsessio

## Workflows on the hosted integration

The live integration page documents these 6 operations:

- `view_business_dashboard`
- `manage_staff_schedules`
- `track_package_balances`
- `sell_session_packages`
- `verify_session_visits`
- `share_booking_link`

The local stdio adapter exposes seven browser helpers listed above. These helpers forward to Cotlet.dev; the workflow operations are documented on the hosted integration page.

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct role in the browser workflow: status checks readiness, guide explains usage, open starts a session, read inspects the page, click/type interact, and close ends the session. There is little risk of confusing one tool for another.

Naming Consistency5/5

All tools use the same nextsessio_ prefix followed by a concise action verb. The pattern is predictable and consistent throughout the set.

Tool Count5/5

Seven tools is well-scoped for a browser-automation workflow. Each tool earns its place, with no obvious redundancy or missing core action.

Completeness4/5

The set covers the essential lifecycle: readiness check, guidance, opening a page, reading, clicking, typing, and closing. Minor gaps like explicit navigation/back/scroll controls are not present, but the core workflow is covered.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues