booking-mcp-app
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
booking-mcp-app
A view-only MCP App: an MCP server that exposes court-availability data and renders it as a
read-only panel inside an MCP host (Claude Desktop, VS Code, or the free local test host), using
the MCP Apps protocol (spec
2026-01-26).
This is the first phase of porting the generative-ui POC to MCP Apps. Read-only, no booking yet:
the important shift from generative-ui is that the data lives on the server (the tool), not
in the conversation. The UI only displays what the server returns.
What it does
The server registers one tool, get_court_availability, that returns which courts and time slots
are free for a given date + sport from in-memory mock data. The tool is linked to a UI resource
(ui://court-availability/panel.html) that the host renders in a sandboxed iframe as a read-only
grid of courts x time slots (free vs taken).
Two data paths, both handled the same way in the UI:
The host pushes a tool result to the app (
app.ontoolresult) whenever the agent callsget_court_availability, e.g. with a different date or sport. The panel updates.The app pulls its own initial data on load (
app.callServerTool). This is the app -> server -> app round trip, and it also populates the panel when it is opened directly.
There are no inputs, no submit, no booking. Changing the date or sport happens by calling the tool with different arguments (from the agent or the test host), not from a form.
Related MCP server: vscode-notebook-mcp
Layout
booking-mcp-app/
server.ts MCP server: registers the tool + the ui:// resource, served over HTTP
availability.ts the booking domain (sports, courts, slots) + deterministic mock data
mcp-app.html UI entry point
src/
mcp-app.ts the view: App client, ontoolresult + callServerTool, renders the grid
mcp-app.css panel styling (single light theme)
vite.config.ts bundles the UI into one self-contained HTML (vite-plugin-singlefile)
dist/mcp-app.html the built UI, read by the server and served as the resourceReuses the booking domain from generative-ui (Tennis / Football / Basketball / Padel, courts and
time slots). Availability is deterministic per query, so the same date + sport always renders the
same grid.
Run
Requires Node 18+ (developed on Node 24).
npm install
npm run build # typecheck + bundle the UI to dist/mcp-app.html
npm run serve # start the MCP server on http://localhost:3001/mcpnpm start does the build and serve in one step. Rerun npm run build after any UI change; the
server reads dist/mcp-app.html fresh on each resource request.
npm run checktypechecks only (tsc --noEmit).PORT=4000 npm run servechanges the port.
See the panel in a host
Free: the local test host
The ext-apps repo ships a local host that renders MCP Apps with no account needed.
# 1) in this project, with the server already running (npm run serve)
# 2) in a separate clone of the ext-apps repo:
git clone https://github.com/modelcontextprotocol/ext-apps.git
cd ext-apps/examples/basic-host
npm install
SERVERS='["http://localhost:3001/mcp"]' npm startOpen http://localhost:8080, call get_court_availability (try { "sport": "Padel", "date": "2026-08-21" }), and the availability grid renders in the iframe. Call it again with a different
sport to see the panel update.
Claude Desktop (paid plan)
Expose the local server with a tunnel and add it as a custom connector:
npx cloudflared tunnel --url http://localhost:3001In Claude, go to Settings -> Connectors -> Add custom connector, paste the
https://<something>.trycloudflare.com/mcp URL, then ask Claude to show court availability.
References
MCP Apps overview — https://modelcontextprotocol.io/extensions/apps/overview
Build guide — https://modelcontextprotocol.io/extensions/apps/build
Spec (2026-01-26) — https://github.com/modelcontextprotocol/ext-apps/blob/main/specification/2026-01-26/apps.mdx
Examples — https://github.com/modelcontextprotocol/ext-apps/tree/main/examples
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Resource Guru MCP server for ChatGPT, Claude and any AI agent: list bookings, create booking, confirm tentative booking, approve or decline booking, add time off and create project in your own Resource Guru account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Resource Guru yourself; Cotlet does not store your password and you need no Resource Guru API key. About the official Resource Guru API: Resource Guru has a public REST API with OAuth 2 that reads and writes bookings, projects, clients, resources and time off, and an official MCP server that only reads (checked 23 Oct 2026). The MCP server shows schedules, availability, utilization, project budgets and time off, and cannot change any of it. Setup and FAQ: https://cotlet.dev/integrations/resource-guru-api-mcp-server
SimplePractice MCP server for ChatGPT, Claude and any AI agent: list appointments, accept appointment request, share intake documents, list outstanding balances, list claims, set appointment status and send secure message in your own SimplePractice account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to SimplePractice yourself; Cotlet does not store your password and you need no SimplePractice API key. About the official SimplePractice API: SimplePractice has no public API for practices (checked 27 Oct 2026). Its help center says it does not offer a public-facing API, and the only API, SimpleConnect, lets health plans and employee assistance programs request appointments with in-network clinicians. Setup and FAQ: https://cotlet.dev/integrations/simplepractice-api-mcp-server
Clio MCP server for ChatGPT, Claude and any AI agent: search matters, log time entry, create task, add matter note, create calendar entry and list bills in your own Clio account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Clio yourself; Cotlet does not store your password and you need no Clio API key. About the official Clio API: Yes. Clio has a REST API, the Clio Manage API v4, with OAuth 2.0 (checked 6 Nov 2026). Setup and FAQ: https://cotlet.dev/integrations/clio-api-mcp-server
Acuity Scheduling MCP server for ChatGPT, Claude and any AI agent: list appointments, check availability, book appointment, reschedule appointment, cancel appointment and block off time in your own Acuity Scheduling account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Acuity Scheduling yourself; Cotlet does not store your password and you need no Acuity Scheduling API key. About the official Acuity Scheduling API: Acuity Scheduling has a full REST API but no official MCP server (checked 17 Oct 2026). The API uses HTTP Basic auth with your user ID and API key, and Acuity says API access is available on the Premium plan (formerly Powerhouse), so Starter and Standard accounts have no key to give an agent. Setup and FAQ: https://cotlet.dev/integrations/acuity-scheduling-api-mcp-server
Related MCP Servers
- AlicenseCqualityFmaintenanceEnables AI agents and assistants like Goose or Claude to interact with VS Code through the Model Context Protocol.7622 npm75Apache 2.0
- AlicenseNot gradedqualityDmaintenanceExposes VSCode Jupyter notebooks to MCP-compatible AI agents, enabling them to read, edit, and run cells against the same kernel.MIT
- FlicenseNot gradedqualityDmaintenanceExposes VS Code's integrated browser to external agents (Claude Code, scripts, curl) via a local HTTP API and MCP server.1-
- AlicenseAqualityDmaintenanceExposes the active file and selection(s) from VS Code to MCP clients, enabling CLI coding agents to access current editor context.1MIT