Bookeo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Your Bookeo API key | |
| API_SECRET | Yes | Your Bookeo secret key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_bookings_by_customerA | Search for bookings by customer name or email. Args: customer_name: Full or partial customer name to search for (case-insensitive) customer_email: Full or partial email address to search for (case-insensitive) days_back: How many days back to search (default 90, max 365) Returns: List of matching bookings with customer info, dates, and product details |
| get_bookingA | Look up a specific booking by its booking number. Args: booking_number: The Bookeo booking number (e.g., "123456789") Returns: Complete booking details including customer, pricing, and product info |
| search_bookings_by_dateB | Find all bookings within a date range. Args: start_date: Start date in YYYY-MM-DD format end_date: End date in YYYY-MM-DD format include_canceled: Whether to include canceled bookings Returns: List of bookings with summary info |
| get_booking_paymentsA | Get payment details for a specific booking. Args: booking_number: The Bookeo booking number Returns: Payment breakdown including methods, amounts, and manual vs Stripe detection |
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 4 tools
Each tool has a clearly distinct purpose: retrieving a single booking by number, getting payment details for a booking, searching by customer, and searching by date. No overlap.
All tool names follow a consistent verb_noun pattern: get_booking, get_booking_payments, search_bookings_by_customer, search_bookings_by_date.
4 tools is on the low side but acceptable for a read-only booking query server. However, the scope feels slightly thin.
The tool set is limited to read operations only, missing critical create, update, delete, or cancel booking tools, which are essential for booking management.