Developers

Umovi integration platform

Umovi MCP server

Discovery, availability and booking tools for ChatGPT, Claude and other MCP clients.

The Umovi MCP server exposes a narrow, audited booking interface for AI clients. It does not expose the provider workspace or internal backend endpoints.

MCP endpoint: https://u-agent.m-cloud.pl/mcp
Transport:    Streamable HTTP
Protocol:     2025-06-18

Public discovery

Before account linking, an AI client can:

  • search places and matching services using natural language;
  • use optional city, date, time window, employee and distance hints;
  • read a public place profile;
  • check availability or find the next available slot;
  • render structured booking options and place previews in supported hosts.

Location-aware discovery can use host-provided approximate user location. Public search_providers does not accept raw latitude and longitude as model-facing inputs. The protected get_my_places tool separately accepts coordinates for sorting saved places.

Client compatibility

Tool data and structuredContent work in any compatible MCP client. Interactive cards use the MCP Apps bridge first; ChatGPT-specific openai/* fields are compatibility aliases that other clients may ignore. Hosts without MCP Apps UI support can use the same discovery and booking tools without calling the render tools.

Linked-account actions

With delegated OAuth, an AI client can:

  • book a selected time or the first available appointment;
  • complete a first booking after the user actively acknowledges the provider data-sharing notice;
  • list, inspect, repeat, reschedule and cancel the user's bookings;
  • read and send messages inside an existing booking conversation;
  • list, save and remove saved places.

Messages are booking-scoped. MCP does not provide a generic channel for contacting any provider without an existing booking.

Safety and data-sharing acknowledgement

Booking tools resolve service, employee, place and time but never infer acknowledgement of the provider data-sharing notice. When Umovi returns NEEDS_DATA_DISCLOSURE_ACKNOWLEDGEMENT, the client must show that the user's contact and booking details will be shared with the selected provider, and call confirm_booking with providerDataDisclosureAcknowledged=true only after the user actively acknowledges it. This records delivery of the notice; it is not GDPR/RODO or marketing consent.

Destructive or externally visible actions expose MCP annotations and stable machine states. Backend services remain authoritative for tenant isolation, slot conflicts, required acknowledgements, idempotency and audit logs.

Booking intent and dates

A clear request to book one unambiguous place, service and slot is sufficient intent; avoid a redundant confirmation question. A direct booking request without a date uses first availability. If the place was not specified and location was used to select one, present the selected place and slot for confirmation first. The data-sharing acknowledgement remains a separate explicit step whenever requested by Umovi.

MCP availability searches default to a seven-day horizon. Use date for one exact day and inclusive fromDate/toDate for ranges. Convert strictly “after” or “before” a date to the first or last permitted date. after and before tool fields represent time-of-day windows, not date bounds. For the first or last slot on one day, use slotPreference: "earliest" or "latest".

Languages

Tool presentation supports pl-PL, en-GB, de-DE, es-ES and cs-CZ. Provider communication language is resolved separately so a message can be composed or translated for the receiving place without changing the user's UI locale.

See the generated tools reference for the current 21 tool descriptors.

Hidden public profiles

Providers can hide their public profile. Such providers are omitted from public search and return not-found responses when accessed directly. New bookings cannot be confirmed, including drafts prepared before the profile was hidden. Existing bookings remain accessible to their authorised client under the usual policies. REST OAuth integrations acting for the provider are independent of this setting.