MCP.so
Sign In

Floyd MCP Server

@floyd-run

Basic information

Category

Other

Transports

stdio

Author

floyd-run

Submitted by

Ali Davut

About Floyd MCP Server

MCP server for AI-powered scheduling and booking. Check availability, hold slots, and confirm appointments.

Floyd MCP Server config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Floyd MCP Server tools

7

Check available appointment times for a service

Place a temporary hold on a time slot

Confirm a held booking (requires explicit user consent)

Cancel a held or confirmed booking

Move a booking to a new time

Update a booking's metadata

Retrieve booking details and status

Overview

What is Floyd?

Floyd is an MCP server that exposes scheduling and booking tools from the Floyd API to AI agents. It uses the Model Context Protocol's Streamable HTTP transport, allowing AI assistants to check available appointment slots, hold, confirm, cancel, reschedule, and update bookings.

How to use Floyd?

Install via pnpm install, then run in HTTP mode with pnpm dev (endpoint: POST /) or in stdio mode with pnpm dev -- --stdio. Set the FLOYD_BASE_URL environment variable (defaults to https://api.floyd.run/v1). Agents provide their API key via an Authorization: Bearer header or a token query parameter.

Key features of Floyd

  • Seven booking and scheduling tools for AI agents
  • Streamable HTTP and stdio transport modes
  • Booking lifecycle: hold, confirm, cancel, reschedule, update
  • Signed slotId tokens for secure slot reservations
  • Configurable API base URL and server port
  • Graceful shutdown on SIGTERM/SIGINT

Use cases of Floyd

  • AI assistants scheduling appointments for users
  • Automated booking management in customer support workflows
  • Self-service rescheduling or cancellation of existing bookings
  • Updating booking metadata (e.g., party size, special requests)

Frequently asked questions

1

What tools does Floyd provide?

Floyd provides seven tools: `floyd_get_available_slots`, `floyd_hold_booking`, `floyd_confirm_booking`, `floyd_cancel_booking`, `floyd_reschedule_booking`, `floyd_update_booking`, and `floyd_get_booking`.

2

How does authentication work?

Agents supply their API key either via the `Authorization: Bearer <token>` header or the `?token=<value>` query parameter. The key is forwarded to the Floyd engine on each request. If the engine has auth disabled (e.g., self-hosted), no key is needed.

3

What transport modes are supported?

Floyd supports both Streamable HTTP (default, endpoint `POST /`) and stdio mode (run with `--stdio` flag). A health check endpoint is available at `GET /health`.

4

What is the booking flow?

The recommended flow is: `get_available_slots` → `hold_booking` → `confirm_booking`. The `confirm_booking` tool requires explicit user consent (`userConfirmed: true`). Bookings can also be cancelled, rescheduled, or updated after holding.

5

What are the runtime dependencies?

Floyd requires Node.js and pnpm. It bundles with tsup and has a 10-second timeout on HTTP requests to the Floyd API. No other external services are required by the server itself.

Comments

More Other MCP servers