SalonBridge 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, available at https://cotlet.dev/app. Without it, tool calls fail and return: "Set COTLET_API_KEY. Get it 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.
SalonBridge through Cotlet.dev. Call salonbridge_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 |
|---|---|
| salonbridge_guideA | How to work in SalonBridge (salon appointments, clients, payments, stock and reports): its screens and the sign-in link. Call this first. |
| salonbridge_statusA | Check that your Cotlet.dev account and SalonBridge are ready: account, credits and SalonBridge connection. |
| salonbridge_openA | Open a SalonBridge page in your signed-in Cloud Browser (default https://online.mysalonbridge.com) to work with salon appointments, clients, payments, stock and reports. |
| salonbridge_readB | Read the current SalonBridge page: its text and numbered buttons, links and fields. |
| salonbridge_clickB | Click a numbered element on the current SalonBridge page. |
| salonbridge_typeB | Type text into a numbered field on the current SalonBridge page. |
| salonbridge_closeA | Close the SalonBridge 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
The core browser primitives (open, read, click, type, close) target clearly distinct actions and resources, so an agent is unlikely to misselect among them. The only mild overlap is between salonbridge_guide and salonbridge_status, which both serve onboarding/setup and could be confused at the start of a session, though the descriptions differentiate documentation from account readiness checks.
All tools share a stable 'salonbridge_' prefix, giving a predictable namespace. The suffixes are mostly verbs (open, read, click, type, close) with two noun-style names (guide, status), a minor deviation that remains readable and unsurprising.
Seven tools is well-scoped for a browser-driven app automation server: one guide, one readiness check, and five session primitives that each earn their place. There is no padding or redundancy.
The surface covers the basic lifecycle (onboard, open, read, click, type, close), but lacks common interaction operations a salon-app workflow would need, such as direct navigation/URL entry, dropdown or date-picker selection, and key submission (Enter/Tab). Agents can work around some of this by clicking numbered elements, but form filling with selects and date fields will likely stall.