Platform MCP

Connect Hermes, Claude, OpenClaw, or Cursor

One hosted MCP endpoint lets agents find and book local appointments—even when the shop has no API. Customer consent is required; human-ops covers the rest.

How agents connect

Demand-side agents use a PLATFORM_CLIENT key against the hosted Streamable HTTP endpoint. Company-bound assistants use a different path.

01

Mint a platform client key

From the dashboard (Platform agent) or CLI with audience platform-client and scopes read + book. Copy the bearer token once.

02

Point your agent at the MCP URL

POST https://api.trybookbridge.com/mcp — Streamable HTTP, no company slug. Drop in a config pack below for Hermes, Claude Desktop, Cursor, or OpenClaw.

Authorization: Bearer <PLATFORM_CLIENT_TOKEN>
BOOKBRIDGE_API_URL=https://api.trybookbridge.com
03

Book with consent

find_local_businessbook_local_appointment → if confirmation_required, show the summary → confirm_consent → retry with the same idempotency key. Poll check_fulfillment when the shop needs browser or human-ops.

Consent is not optional. Never skip showing the consent summary to the human before confirm_consent. If automation cannot finish, BookBridge can fall back to browser or staff-assisted fulfillment.

Config packs

Same packs as integrations/platform-mcp/ in the repo. Replace placeholders (or set env vars) before loading into your client.

Tools

Hosted POST /mcp exposes the demand-side booking surface.

ToolScopeRole
find_local_businessreadResolve a shop by name / place
book_local_appointmentbookOne-shot book (consent-gated)
get_consentreadInspect confirmation challenge
confirm_consentbookRecord customer confirmation
check_fulfillmentreadPoll browser / voice / human-ops jobs
accept_alternativebookAccept a proposed alternate slot
decline_alternativesbookDecline all proposed slots

Company-specific assistants use POST /mcp/{slug} with an MCP audience key — see the API reference and company MCP guide.