Umovi

Book services and manage times

Find service providers on Umovi, compare service prices and available times, and create, reschedule or cancel your bookings. Read and send messages about an existing booking and manage your saved places.

What you can ask

Find a hair salon in Warszawa with available times tomorrow.
Example path →

MCP connector

Server URL: https://agent.umovi.app/mcp
Login: OAuth
Protocol: MCP 2025-11-25
Instructions: Use Umovi tools for discovery, availability, booking, booking-scoped messages, saved places, and client bookings. Keep machine codes unchanged and answer the user in their conversation language. Technical UUIDs (bookingId, providerId, serviceId and draftId) are for tool calls only; never display them as booking references. Show only the returned bookingRef to the user. If bookingRef is absent or expired, identify the booking by place, service and time instead; do not invent a code or substitute a UUID. After rendering an Umovi widget, let it present the options and actions. Keep surrounding text brief; do not recreate the same cards, tables or slot lists outside the widget unless the user explicitly asks for a text alternative. When agentAction is INFORM_USER_AND_OFFER_ALTERNATIVE_PROVIDER, explain that this provider does not accept bookings through AI agents, offer to find another provider, and do not retry the operation for the same provider. Render UI only for explicit option comparison, place preview, or booking conversation requests. Clear intent to book one unambiguous option or send one unambiguous booking message is sufficient; do not ask for duplicate confirmation. Use for a clear 'move to the first free time' request and for a clear repeat request. Messages require an existing booking and the place is resolved from it. Always set bodyLanguage to the language actually used in body. For composed intent such as 'tell them I will be late', write only the provider-facing message in providerCommunicationLanguage and use COMPOSED_IN_TARGET_LANGUAGE. When the user supplies exact final wording in another language, preserve it byte-for-byte as originalBody, put the automatic translation in body, and use AI_TRANSLATED_WITH_ORIGINAL. Use ORIGINAL_ONLY when the exact text already matches the target language. Set translationDeclinedByUser=true only when the user explicitly requests sending foreign-language wording without translation. Never expose an instruction such as 'write that...' as originalBody. For availability without a horizon, search the next 7 days.

Tools

Reads data11

Changes data1

Deletes or can't be undone9

Skills

None in the store listings or on the server

MCP connector

Server URL

https://agent.umovi.app/mcp

OAuth

Protocol

MCP 2025-11-25

Instructions

Use Umovi tools for discovery, availability, booking, booking-scoped messages, saved places, and client bookings. Keep machine codes unchanged and answer the user in their conversation language. Technical UUIDs (bookingId, providerId, serviceId and draftId) are for tool calls only; never display them as booking references. Show only the returned bookingRef to the user. If bookingRef is absent or expired, identify the booking by place, service and time instead; do not invent a code or substitute a UUID. After rendering an Umovi widget, let it present the options and actions. Keep surrounding text brief; do not recreate the same cards, tables or slot lists outside the widget unless the user explicitly asks for a text alternative. When agentAction is INFORM_USER_AND_OFFER_ALTERNATIVE_PROVIDER, explain that this provider does not accept bookings through AI agents, offer to find another provider, and do not retry the operation for the same provider. Render UI only for explicit option comparison, place preview, or booking conversation requests. Clear intent to book one unambiguous option or send one unambiguous booking message is sufficient; do not ask for duplicate confirmation. Use for a clear 'move to the first free time' request and for a clear repeat request. Messages require an existing booking and the place is resolved from it. Always set bodyLanguage to the language actually used in body. For composed intent such as 'tell them I will be late', write only the provider-facing message in providerCommunicationLanguage and use COMPOSED_IN_TARGET_LANGUAGE. When the user supplies exact final wording in another language, preserve it byte-for-byte as originalBody, put the automatic translation in body, and use AI_TRANSLATED_WITH_ORIGINAL. Use ORIGINAL_ONLY when the exact text already matches the target language. Set translationDeclinedByUser=true only when the user explicitly requests sending foreign-language wording without translation. Never expose an instruction such as 'write that...' as originalBody. For availability without a horizon, search the next 7 days.

Tools