Forktime MCP

Two MCP servers. One to run your own restaurant, one to book a table at any restaurant on Forktime.

Two servers, two jobs

Forktime exposes two Model Context Protocol servers. They look similar but are deliberately separate — different audience, different powers, different auth.

Manage MCP

Run your own restaurant from an AI assistant — bookings, floor plan, menu, schedule, settings, guests, messaging, analytics. Full read + write, scoped to the brands you belong to.

For: owners · operators · agencies. Get started →

Book MCP

Let any AI assistant discover a venue and book a table anywhere on Forktime — search by city / cuisine, check availability, reserve. Booking only; guests edit or cancel through the SMS link they receive.

For: concierge agents · booking apps · guests. Get started →

Which one do I want?

	Manage MCP	Book MCP
Endpoint	`api.forktime.ai/mcp`	`api.forktime.ai/booking/mcp`
Who it’s for	owners · operators · agencies	any AI assistant booking for a guest
Which restaurants	only yours (brand membership)	any venue on Forktime
What it does	69 tools — full read + write	3 tools — search → availability → book
What it can’t do	—	no edit, no cancel
Auth	dashboard sign-in · `gfk_live_` API key · OAuth	`gfk_dev_` developer key (rate-limited)
Data it sees	your full internal data (guests, analytics)	public venue info + availability only

Rule of thumb: managing a restaurant you run → Manage MCP. Booking a table somewhere → Book MCP.

Start here

Owner / operator? → Manage MCP quickstart and tool reference.
Building a booking / concierge experience? → Book MCP overview.

Runnable examples

Prefer to start from working code? The forktime-mcp-quickstart repo has copy-paste Python and Node.js / TypeScript examples for both servers — clone it, drop in a key, and you’re connected in a couple of minutes. It also covers connecting from Claude Desktop, Claude Code, and raw curl.

git clone https://github.com/Fork-Time/forktime-mcp-quickstart