NextSessio MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key, obtained at https://cotlet.dev/app. Required for the local stdio MCP server to forward tool calls; without it, tool calls answer: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app". |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
NextSessio through Cotlet.dev. Call nextsessio_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nextsessio_guideA | How to work in NextSessio (review bookings, track prepaid package balances and verify visits): its screens and the sign-in link. Call this first. |
| nextsessio_statusA | Check that your Cotlet.dev account and NextSessio are ready: account, credits and NextSessio connection. |
| nextsessio_openB | Open a NextSessio page in your signed-in Cloud Browser (default https://nextsessio.com) to work with review bookings, track prepaid package balances and verify visits. |
| nextsessio_readB | Read the current NextSessio page: its text and numbered buttons, links and fields. |
| nextsessio_clickB | Click a numbered element on the current NextSessio page. |
| nextsessio_typeC | Type text into a numbered field on the current NextSessio page. |
| nextsessio_closeA | Close the NextSessio browser session when the work is done, so credits stop running. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
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.
All tools use the same nextsessio_ prefix followed by a concise action verb. The pattern is predictable and consistent throughout the set.
Seven tools is well-scoped for a browser-automation workflow. Each tool earns its place, with no obvious redundancy or missing core action.
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.