Bookibles MCP Server
# Bookibles MCP server for ChatGPT and Claude
Connect Bookibles to ChatGPT, Claude, Codex and Claude Code through the hosted MCP server from Cotlet.dev. Work with bookings, services, availability and customer messages in your own signed-in Bookibles Cloud Browser.
Bookibles publishes no public API or official MCP server, and no official ChatGPT or Claude connector was found, according to the [live Bookibles integration page](https://cotlet.dev/integrations/bookibles-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=bookibles), checked 15 November 2026. This is an unofficial integration, not affiliated with Bookibles.
## Connect Bookibles
1. [Get access through Cotlet.dev](https://cotlet.dev/signup?app=bookibles).
2. Open `bookibles.com/login` in your Cotlet Cloud Browser and sign in yourself with email and password or Google.
3. Add `https://cotlet.dev/mcp/v1/connect` in ChatGPT or Claude as a connector using OAuth.
4. Enable Bookibles and refresh your connector if necessary.
For Codex, Claude Code and other clients that use an API key, create a key in the Cotlet console and connect to `https://cotlet.dev/mcp/v1`.
```toml
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```
```sh
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY"
```
## Bookibles workflows
The live page describes 12 workflows: 6 reads and 6 writes. Writes ask for confirmation by default; you can change this per tool.
| Workflow | Access |
|---|---|
| `list_bookings` | Read bookings by date and status |
| `get_booking` | Read details, timeline and permitted actions |
| `update_booking_status` | Confirm, decline, cancel, complete or mark no-show |
| `reschedule_booking` | Move a scheduled booking after availability checks |
| `list_services` | Read services, duration, pricing and capacity |
| `create_service` | Add a bookable service within your plan |
| `set_booking_rules` | Change booking type, auto-accept or capacity |
| `get_availability` | Read hours, breaks and dated closures |
| `edit_availability` | Change hours, breaks or dated closures |
| `read_conversation` | Read a signed-in customer's conversation |
| `message_customer` | Send a booking message to an eligible signed-in customer |
| `get_booking_analytics` | Read completed-booking analytics on Pro and above |
Example requests:
> Show pending booking requests for tomorrow and the actions each one allows.
> Check availability before proposing a new time for this booking. Show me the change before saving it.
> Summarize last month's completed bookings and explain completed booking value.
Flexible requests have no slot and cannot be rescheduled as scheduled bookings. Guest and manual bookings have no customer conversation. Completed booking value is based on recorded booking prices; it is not money collected. Cancellation, decline, completion and no-show are final states in Bookibles.
## Optional local stdio bridge
The hosted connector works without installing this repository. The included Python bridge exposes seven browser tools for Bookibles and forwards them to the hosted Cotlet MCP server. These browser tools are separate from the 12 workflows described on the integration page.
```sh
export COTLET_API_KEY='your-key'
python bookibles_agent.py serve
```
Python 3.10 or later is required. The bridge uses the standard library. Set the key in your local environment and keep it out of source control.
## Session and access
You sign in yourself and sign in again if Bookibles signs you out. Your signed-in browser profile is encrypted. Disable Bookibles for agents or reset the browser to revoke access. Bookibles plan and role restrictions continue to apply.
See the [Bookibles connection guide](https://cotlet.dev/integrations/bookibles-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=bookibles) for current setup instructions and pricing.
## License
Elastic License 2.0. See [LICENSE](LICENSE).
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.