Hapana 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 from https://cotlet.dev/app. Required for 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.
Hapana through Cotlet.dev. Call hapana_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 |
|---|---|
| hapana_guideA | How to work in Hapana (manage studio clients, memberships, bookings and payments): its screens and the sign-in link. Call this first. |
| hapana_statusA | Check that your Cotlet.dev account and Hapana are ready: account, credits and Hapana connection. |
| hapana_openB | Open a Hapana page in your signed-in Cloud Browser (default https://core.hapana.com) to work with manage studio clients, memberships, bookings and payments. |
| hapana_readB | Read the current Hapana page: its text and numbered buttons, links and fields. |
| hapana_clickC | Click a numbered element on the current Hapana page. |
| hapana_typeB | Type text into a numbered field on the current Hapana page. |
| hapana_closeA | Close the Hapana 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 targets a distinct step in a browser-automation workflow: guide (instructions), status (account/connection readiness), open (launch session/page), read (inspect page), click (act on element), type (fill field), close (end session). There is no meaningful overlap, and the numbered-element convention in read/click/type reinforces clear boundaries.
All tools share a consistent hapana_ prefix with short, lowercase names, making the set easy to scan. Minor deviation: guide and status are nouns while open/read/click/type/close are verbs, but the pattern remains predictable.
Seven tools is well-scoped for a guided browser-automation server: a setup pair (guide, status), a session lifecycle (open, close), and page primitives (read, click, type). No tool feels redundant or missing from the core loop.
The surface covers the essential loop of opening a page, inspecting it, interacting via clicks and typing, and closing the session, with guidance and status checks included. Minor gaps exist for common web actions like scrolling, selecting dropdown options, or pressing keys (e.g., Enter to submit), but these can often be worked around via click/type.