mcpField
F
Floyd

Floyd

Local
floyd.runProductivity2Updated 6w ago

About Floyd

Floyd exposes Floyd Engine scheduling and booking operations to AI agents. Its tools cover slot availability, temporary holds, confirmation, cancellation, rescheduling, and booking updates.

Key features

  1. 01Check service availability
  2. 02Temporarily hold a time slot
  3. 03Confirm bookings with user consent
  4. 04Cancel held or confirmed bookings
  5. 05Reschedule bookings
  6. 06Retrieve or update booking details

Use cases

  1. 01Find appointment times for a service
  2. 02Hold a selected slot while arranging a booking
  3. 03Confirm or cancel an appointment
  4. 04Move a booking or update its metadata

MCP support

An MCP server that exposes Floyd Engine scheduling and booking tools over Streamable HTTP, with an optional stdio mode.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Floyd MCP Server

MCP server that exposes Floyd Engine scheduling and booking tools to AI agents. Built on the Model Context Protocol Streamable HTTP transport.

For the engine's API documentation, see the docs folder in the engine repo.

Tools

ToolDescription
floyd_get_available_slotsCheck available appointment times for a service
floyd_hold_bookingPlace a temporary hold on a time slot
floyd_confirm_bookingConfirm a held booking (requires explicit user consent)
floyd_cancel_bookingCancel a held or confirmed booking
floyd_reschedule_bookingMove a booking to a new time
floyd_update_bookingUpdate a booking's metadata
floyd_get_bookingRetrieve booking details and status

Setup

pnpm install
Environment variables
VariableRequiredDefaultDescription
FLOYD_BASE_URLNohttp://localhost:4000/v1Floyd Engine base URL
PORTNo3000HTTP server port

Usage

HTTP mode (Streamable HTTP)
pnpm dev

MCP endpoint: POST / Health check: GET /health

Stdio mode
pnpm dev -- --stdio
Authentication

When the Floyd engine requires authentication, connecting agents provide their API key via:

  1. Authorization: Bearer <token> header (preferred)
  2. ?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.

Booking flow

get_available_slots → hold_booking → confirm_booking
                                   ↘ cancel_booking
                                   ↘ reschedule_booking
                                   ↘ update_booking (metadata)
  1. Get slots — query available times, returns signed slotId tokens
  2. Hold — reserve a slot using the slotId (or explicit fields). Creates a booking in held state
  3. Confirm — finalize the booking. Requires userConfirmed: true
  4. Cancel — release a held or confirmed booking
  5. Reschedule — move a booking to a new time, preserving its identity
  6. 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 tsup

Production

pnpm build
pnpm start

The server handles SIGTERM/SIGINT for graceful shutdown. HTTP requests to the Floyd API have a 10-second timeout.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.