Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYYesAPI key created in the Cotlet.dev console. Used as a Bearer token for the hosted MCP endpoint and by the local stdio bridge.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Booker through Cotlet.dev. Call booker_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
booker_guideA

How to work in Booker (salon and spa appointments, client messages, marketing and sales): its screens and the sign-in link. Call this first.

booker_statusA

Check that your Cotlet.dev account and Booker are ready: account, credits and Booker connection.

booker_openA

Open a Booker page in your signed-in Cloud Browser (default https://signin.booker.com) to work with salon and spa appointments, client messages, marketing and sales.

booker_readA

Read the current Booker page: its text and numbered buttons, links and fields.

booker_clickC

Click a numbered element on the current Booker page.

booker_typeC

Type text into a numbered field on the current Booker page.

booker_closeA

Close the Booker browser session when the work is done, so credits stop running.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct step in a browser-session workflow: guide is static documentation, status checks account/connection readiness, and open/read/click/type/close map one-to-one onto discrete browser primitives. The only mild adjacency is guide vs. status (both are pre-flight orientation), but their outputs and purposes are clearly separable.

Naming Consistency5/5

Every tool uses the same booker_ prefix followed by a single lowercase verb or noun (guide, status, open, read, click, type, close), with no mixing of camelCase, snake_case, or verb/noun styles. The set is fully predictable.

Tool Count5/5

Seven tools is a tight, well-scoped surface for a browser-automation wrapper over one SaaS product: two orientation tools plus five primitives that form a complete act-observe loop. No tool looks redundant or padded.

Completeness4/5

The open/read/click/type/close loop covers the core lifecycle of driving a signed-in session, including explicit credit-saving teardown. Minor gaps remain for richer interaction such as selecting dropdown options, sending key presses (Enter/Escape), or waiting for async page loads, which agents may have to work around by clicking.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues