
Floyd
โ 2from floyd-run
Scheduling and booking engine for AI agents. Check availability, hold slots, and confirm appointments with two-phase booking and conflict-free resource management.
Floyd MCP Server
MCP server that exposes Floyd scheduling and booking tools to AI agents. Built on the Model Context Protocol Streamable HTTP transport.
For full API documentation, see docs.floyd.run.
Tools
| Tool | Description |
|---|---|
floyd_get_available_slots | Check available appointment times for a service |
floyd_hold_booking | Place a temporary hold on a time slot |
floyd_confirm_booking | Confirm a held booking (requires explicit user consent) |
floyd_cancel_booking | Cancel a held or confirmed booking |
floyd_reschedule_booking | Move a booking to a new time |
floyd_update_booking | Update a booking's metadata |
floyd_get_booking | Retrieve booking details and status |
Booking flow
get_available_slots โ hold_booking โ confirm_booking
โ cancel_booking
โ reschedule_booking
โ update_booking (metadata)- Get slots โ query available times, returns signed
slotIdtokens - Hold โ reserve a slot using the
slotId(or explicit fields). Creates a booking inheldstate - Confirm โ finalize the booking. Requires
userConfirmed: true - Cancel โ release a held or confirmed booking
- Reschedule โ move a booking to a new time, preserving its identity
- Update โ attach or replace metadata (e.g. party size, special requests)
Development
pnpm test # run tests
pnpm typecheck # type-check
pnpm lint # eslint
pnpm format # prettier
pnpm build # bundle with tsupProduction
pnpm build
pnpm startThe server handles SIGTERM/SIGINT for graceful shutdown. HTTP requests to the Floyd API have a 10-second timeout.
pnpm installSetup
pnpm installEnvironment variables
| Variable | Required | Default | Description |
|---|---|---|---|
FLOYD_BASE_URL | No | https://api.floyd.run/v1 | Floyd API base URL |
PORT | No | 3000 | HTTP server port |
Usage
HTTP mode (Streamable HTTP)
pnpm devMCP endpoint: POST /
Health check: GET /health
Stdio mode
pnpm dev -- --stdioAuthentication
When the Floyd engine requires authentication, connecting agents provide their API key via:
Authorization: Bearer <token>header (preferred)?token=<value>query parameter
The API key is forwarded to the Floyd engine on each request. If the engine has auth disabled (e.g. self-hosted), no key is needed.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.