Chamelix

The operating system for local organizations — bookings, members, documents and reminders in one place.

Via Padova 20, 36010 Zanè (VI), Italia

app@chamelix.it

VAT: 04578500243

© 2025-2026. All rights reserved

Beta

Your customers can book from Claude or ChatGPT

Your customers can book from Claude or ChatGPT

Chamelix publishes an MCP (Model Context Protocol) server: the customer's AI assistant connects to their Chamelix account and can search open courts, hold a slot and confirm the booking. You install and configure nothing: the slots, rules and prices already in Chamelix are the ones it uses.

Not public yet

The MCP server is built and tested but not open to the public yet: the global switch is off, so the endpoint and the OAuth flow behave as if they did not exist. Write to us if you want to join the trial group.

If you run a club or a venue

If you run a club or a venue

The AI channel is not another calendar to keep in sync: it is the same calendar, seen through another door.

You do nothing

The slots you publish in Chamelix are exactly what the assistant sees. No price list to rewrite, no integration to buy, no new panel to learn.

Your rules stay your rules

Membership, medical certificate, required documents, minimum players, cancellation window: the assistant goes through the same checks as the app. If someone cannot book in the app, they cannot book from there either.

A person books, not a robot

Every action is tied to a real Chamelix account that logged in and authorised the connection. In your calendar you see a name and a booking as always — not an anonymous contact.

Everything is logged

Every assistant call — successful or refused — lands in a technical log with the user, the connected application and the outcome. If something goes wrong, it is knowable.

How it works for the customer

  1. In their assistant they add Chamelix as a connector by pasting the server address.
  2. The Chamelix login opens: they sign in with their account and see exactly which permissions they are granting.
  3. From then on they can ask in plain language: "find me a padel court in Bologna tomorrow evening".
  4. The assistant searches open slots, holds one for a few minutes and confirms only after the person approves.

If you are connecting an assistant

If you are connecting an assistant

Remote MCP server, streamable HTTP transport, OAuth 2.1 authorisation with PKCE. No API key to request: client registration is dynamic.

MCP endpoint

Paste it into your assistant's connector settings. The rest of the flow (login, consent, tokens) is handled by the server.
https://chamelix.it/api/mcp

Scopes

bookings:read

Search venues and availability, and read your own bookings.

bookings:write

Hold a slot, confirm and cancel your own bookings.

Available tools

search_venuesbookings:read

Search venues by city, coordinates or activity type.

get_venue_detailsbookings:read

Details of one venue: services, timezone, cancellation window, your membership status.

What this channel does not do

  • It does not expose a venue's customers, their contacts or their documents: the assistant sees public data and the bookings of whoever authorised it.
  • It does no management: no changes to the calendar, members, roles or venue settings.
  • It does not handle orders or menus yet: today's tools cover slot bookings.
  • The connection is revoked by removing the access from the assistant; revocation on the Chamelix side is in progress.

Want to try it on your club?

The connector is in closed beta. Write to us: we enable access and walk through the first assistant-made booking together.

search_availabilitybookings:read

Open slots over a date range (14 days max), with the id to use for booking.

create_booking_holdbookings:write

Hold a slot for a few minutes while the person decides.

confirm_bookingbookings:write

Confirm the booking for the connected user. Idempotent: requires a client-supplied key.

list_my_bookingsbookings:read

The connected user's bookings: upcoming, past or cancelled.

cancel_bookingbookings:write

Cancel one of the connected user's bookings, if the cancellation window allows it.

Discovery metadata

RFC 9728 for the protected resource and RFC 8414 for the authorization server. Conformant MCP clients find them on their own starting from the 401 response.
https://chamelix.it/.well-known/oauth-protected-resource/api/mcphttps://chamelix.it/.well-known/oauth-authorization-server

Things to know

  • Failures are typed and model-readable ({ ok: false, code, message }), not transport errors: the client can correct and retry.
  • confirm_booking requires an idempotencyKey: a second attempt with the same key returns the original booking instead of creating two.
  • Tools act only for the connected user. There is no way to read or change anyone else's bookings.
  • No payment goes through here: per-booking payment does not exist in Chamelix today.
  • Consent is requested on every authorisation, with the permission list spelled out.