Developer Platform

MCP Server Guide

Connect Claude Desktop, custom GPTs, or any Model Context Protocol client to your venue. Read schedule, members, passes, bookings, revenue, and alerts conversationally — using the same API key that powers the REST API.

Endpoint

POST https://bookingbible.com/api/mcp

Transport: HTTP, JSON-RPC 2.0. Protocol version 2025-03-26. Single requests and batch arrays are both accepted. Authenticate every request with an X-API-Key: bb_live_… header. SSE / streaming is not yet supported.

Quick start — curl

curl -X POST https://bookingbible.com/api/mcp \
  -H "Content-Type: application/json" \
  -H "X-API-Key: bb_live_..." \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Claude Desktop

Add this to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on Windows / Linux:

{
  "mcpServers": {
    "booking-bible": {
      "transport": {
        "type": "http",
        "url": "https://bookingbible.com/api/mcp",
        "headers": { "X-API-Key": "bb_live_..." }
      }
    }
  }
}

Restart Claude Desktop. The venue's resources and tools should appear automatically.

Resources (8)

MCP resources are read-only views over your venue's data. Each URI is templated; the client substitutes the path parameter and calls resources/read.

URI	Name	Required scopes
venue://schedule/{date}	Daily schedule	read:schedule
venue://classes/{date_range}	Class instances by range	read:schedule
venue://members/{query}	Member search	read:members
venue://member/{id}	Member detail	read:members
venue://passes	Active pass types	read:passes
venue://bookings/{date}	Bookings on date	read:bookings
venue://revenue/{period}	Revenue summary	read:reports
venue://alerts	Active alerts	read:operations

Tools (6)

Tools are invokable functions. Inputs are validated against a JSON Schema returned by tools/list; call with tools/call.

Name	Purpose	Required scopes
search_schedule	Find classes by date / type / instructor	read:schedule
check_availability	Capacity + remaining seats for a class instance	read:schedule
search_members	Find members by name / email / display ID	read:members
get_member_details	Profile + active passes + recent bookings	read:members
get_revenue_summary	Revenue totals by currency for a period	read:reports
get_today_overview	Snapshot: today's classes, bookings, open alerts	read:schedule, read:bookings, read:operations

Plan + scope requirements

Your venue's plan must include API access (Pro / Enterprise) AND the platform must have activated feature_provisioning.api_enabled.
Issue an API key at /admin/settings/api-keys. Grant the read scopes you want exposed (typically read:schedule, read:members, read:bookings, read:passes, read:reports, read:operations).
Rate limiting follows the same per-key window as the REST API (default 100/min).

Error codes

-32601 Method not found / unknown tool
-32602 Invalid params (Zod validation failure)
-32001 Unauthorized (missing or bad X-API-Key)
-32002 Forbidden (API key missing required scope)
-32003 Rate limited
-32004 Plan does not include API access
-32005 Resource not found

Out of scope (v1)

Write operations — read-only in v1; mutations stay on the REST API.
Stdio transport — HTTP only.
MCP prompts — resources + tools cover the v1 use cases.
Real-time subscriptions — poll-based for now.