Floyd

Name: Floyd
Author: floyd-run

@floyd-run

代码仓库主页

关于 Floyd

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

基本信息

分类

其他

运行时

node

传输方式

stdio

发布者

floyd-run

提交者

Ali Davut

配置

暂无标准配置

该服务器的 README 中没有可解析的 MCP 配置块，请前往代码仓库查看安装说明。

代码仓库

工具

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

概览

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)

FAQ from Floyd

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.

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.

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.

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.

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.