Bookingmood MCP integration for AI agents.
Connect AI agents to Bookingmood through 3 structured actions, including list bookings, list products, and query availability. Review authentication, inputs…
- ACTION CONTRACTS
- 3
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Bookingmood integration exposes
The Bookingmood Agent App exposes 3 provider-backed actions for productivity work. Its current contract lets an authorized agent list bookingmood bookings with optional postgrest select, pagination, ordering, and id filters, list bookingmood products with optional postgrest select, pagination, ordering, and id filters, and fetch bookingmood availability for a product using the official availability endpoint. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Bookingmood account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Bookingmood capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
list_bookingsREADList Bookingmood bookings with optional PostgREST select, pagination, ordering, and ID filters.
INPUTS: select / limit / offset / order / id
list_productsREADList Bookingmood products with optional PostgREST select, pagination, ordering, and ID filters.
INPUTS: select / limit / offset / order / id
query_availabilityREADFetch Bookingmood availability for a product using the official availability endpoint.
INPUTS: product_id / start / end
INPUT CONTRACTS
Know what the action needs before it runs.
list_bookings
selectOPTIONAL- Columns to select from the bookings endpoint.
limitOPTIONAL- Maximum number of bookings to return.
offsetOPTIONAL- Number of bookings to skip before returning results.
orderOPTIONAL- PostgREST order expression for bookings, such as created_at.desc or updated_at.asc.
idOPTIONAL- PostgREST filter for a specific booking ID.
list_products
selectOPTIONAL- Columns to select from the products endpoint.
limitOPTIONAL- Maximum number of products to return.
offsetOPTIONAL- Number of products to skip before returning results.
orderOPTIONAL- PostgREST order expression for products, such as created_at.desc or updated_at.asc.
idOPTIONAL- PostgREST filter for a specific product ID.
query_availability
product_idREQUIRED- Bookingmood product ID to query availability for.
startOPTIONAL- Start date for the availability window.
endOPTIONAL- End date for the availability window.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect List Bookings
List Bookingmood bookings with optional PostgREST select, pagination, ordering, and ID filters. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
list_bookingsVerify with List Products
List Bookingmood products with optional PostgREST select, pagination, ordering, and ID filters. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_productsSAFETY BOUNDARY
Operate Bookingmood with explicit limits
- Authorize Bookingmood with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Bookingmood data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Bookingmood rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Bookingmood task completed successfully.
CONNECTION MODEL
API key
Bookingmood API key used as an Authorization Bearer token. Create or view it from your Bookingmood account API settings: https://www.bookingmood.com/en-US/api-reference.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Bookingmood.