Bookibles MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | No | API key created in the Cotlet console for clients that use an API key (e.g., Codex, Claude Code, or the optional local stdio bridge). Not required when using OAuth-based connectors. Set it in your local environment and keep it out of source control. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Bookibles through Cotlet.dev. Call bookibles_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 |
|---|---|
| bookibles_guideA | How to work in Bookibles (bookings, services, availability and customer messages): its screens and the sign-in link. Call this first. |
| bookibles_statusA | Check that your Cotlet.dev account and Bookibles are ready: account, credits and Bookibles connection. |
| bookibles_openA | Open a Bookibles page in your signed-in Cloud Browser (default https://bookibles.com/login) to work with bookings, services, availability and customer messages. |
| bookibles_readB | Read the current Bookibles page: its text and numbered buttons, links and fields. |
| bookibles_clickB | Click a numbered element on the current Bookibles page. |
| bookibles_typeB | Type text into a numbered field on the current Bookibles page. |
| bookibles_closeA | Close the Bookibles 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 maps to a distinct step in the browser workflow: guide (instructions), status (readiness check), open (start session), read (inspect page), click, type, and close. There is no meaningful overlap between tools; the boundary between guide and status is clear (instructions vs. account/connection check).
All tools share a consistent `bookibles_` prefix with short, readable suffixes. Most suffixes are verbs (open, read, click, type, close), while guide and status are nouns, which is a minor deviation from a pure verb pattern but still predictable and easy to follow.
Seven tools is well-scoped for a focused browser-automation server. Each tool earns its place in the session lifecycle without redundancy or missing core actions.
The surface covers the essential browser lifecycle: onboarding, session start, page reading, element interaction, and cleanup. Some interaction primitives are missing (e.g., explicit scroll, keyboard press, or wait), but agents can likely work around these via clicking links or reading numbered elements.