Skip to main content
Glama
Pabau MCP Server

Pabau MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYYesYour Cotlet.dev API key, obtained at https://cotlet.dev/app. It is used as `Authorization: Bearer $COTLET_API_KEY` for the hosted MCP endpoint (`https://cotlet.dev/mcp/v1`) and by the local stdio bridge (`python3 pabau_agent.py serve`). Without a key, the local bridge can still list its helper tools, but tool calls return setup instructions.

Instructions

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

Pabau through Cotlet.dev. Call pabau_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
pabau_guideA

How to work in Pabau (review appointment calendars and contact records for reception work): its screens and the sign-in link. Call this first.

pabau_statusA

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

pabau_openB

Open a Pabau page in your signed-in Cloud Browser (default https://app.pabau.com) to work with review appointment calendars and contact records for reception work.

pabau_readA

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

pabau_clickB

Click a numbered element on the current Pabau page.

pabau_typeC

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

pabau_closeA

Close the Pabau 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 has a clearly distinct role: guide/status are informational, while open/read/click/type/close map to distinct browser-session actions. The lifecycle is easy to follow, with little risk of selecting the wrong tool.

Naming Consistency5/5

All tools use a consistent pabau_ prefix, snake_case, and short readable names. Although guide and status are nouns rather than verbs, the overall convention is predictable and coherent.

Tool Count5/5

Seven tools is well-scoped for a browser automation server. Each tool corresponds to a necessary setup, interaction, inspection, or cleanup step.

Completeness4/5

The core browser lifecycle is covered: guidance, readiness check, open, read, click, type, and close. Minor gaps exist around explicit navigation, scrolling, or keyboard submission, but most reception workflows can likely be completed through clicking and typing.