Floyd

Server Details

Scheduling and booking engine for AI agents. Check availability, hold slots, and confirm appointments with two-phase booking and conflict-free resource management.

Status: Healthy
Last Tested: 2026-03-09 21:30
Transport: Streamable HTTP
URL

See and control every tool call

Log every tool call with full inputs and outputs

Control which tools are enabled per connector

Manage credentials once, use from any MCP client

Monitor uptime and get alerted when servers go down

Available Tools

7 tools

floyd_cancel_bookingInspect

Cancel a held or confirmed booking. Releases the time slot.

ParametersJSON Schema

Name	Required	Description
`reason`	No	Optional cancellation reason for record-keeping.
`bookingId`	Yes	The booking ID to cancel.
`idempotencyKey`	No	Forwarded as Idempotency-Key header.

floyd_confirm_bookingInspect

Confirm a held booking. Only call this after the user has explicitly agreed to finalize the booking.

ParametersJSON Schema

Name	Required	Description
`bookingId`	Yes	The booking ID from floyd_hold_booking.
`userConfirmed`	Yes	Must be true. Set to true only after the user has explicitly agreed to finalize the booking.
`idempotencyKey`	No	Forwarded as Idempotency-Key header.

floyd_get_available_slotsInspect

Check available appointment times for a service.

ParametersJSON Schema

Name	Required	Description
`limit`	No	Max slots to return. Default 10.
`endTime`	Yes	ISO 8601 UTC. End of the search range. Max 7 days from startTime.
`serviceId`	Yes	The service to check availability for.
`startTime`	Yes	ISO 8601 UTC. Start of the search range.
`durationMinutes`	Yes	Desired appointment length in minutes.

floyd_get_bookingInspect

Retrieve booking details. Use this for recap at end of session or to check current status.

ParametersJSON Schema

Name	Required	Description	Default
`bookingId`	Yes	The booking ID to retrieve.
`includeAllocations`	No	If true, includes time allocation details. Default false.

floyd_hold_bookingInspect

Place a temporary hold on a time slot. The hold expires automatically if not confirmed. Use a slotId from floyd_get_available_slots, or provide explicit fields.

ParametersJSON Schema

Name	Required	Description
`slotId`	No	Signed token from floyd_get_available_slots. Preferred over explicit fields.
`endTime`	No	ISO 8601 UTC. Required if no slotId.
`metadata`	No	Optional context (customer name, phone, notes).
`serviceId`	No	Required if no slotId.
`startTime`	No	ISO 8601 UTC. Required if no slotId.
`resourceId`	No	Required if no slotId.
`idempotencyKey`	No	Forwarded as Idempotency-Key header.

floyd_reschedule_bookingInspect

Move a held or confirmed booking to a new time. Preserves the booking identity and re-evaluates the service policy against the new time.

ParametersJSON Schema

Name	Required	Description
`endTime`	Yes	New appointment end time in ISO 8601 UTC (e.g. 2026-03-01T15:00:00Z).
`bookingId`	Yes	The booking ID to reschedule.
`startTime`	Yes	New appointment start time in ISO 8601 UTC (e.g. 2026-03-01T14:00:00Z).
`idempotencyKey`	No	Forwarded as Idempotency-Key header.

floyd_update_bookingInspect

Update a booking's metadata. Use this to attach context learned during the conversation (e.g. party size, special requests, cancellation reason). Works on bookings in any status.

ParametersJSON Schema

Name	Required	Description	Default
`metadata`	Yes	The new metadata object. Replaces the entire existing metadata.
`bookingId`	Yes	The booking ID to update.

To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "maintainers": [
    {
      "email": "your-email@example.com"
    }
  ]
}

The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.

Server Details

Available Tools

Discussions

Your Connectors

Resources