AgendaPro MCP by usefulapi

io.usefulapi/agendapro · v1.0.0 · communication

AgendaPro MCP by usefulapi is healthy: it completed an MCP handshake in 896 ms and exposes 24 tools.

Read AgendaPro bookings, slots, clients, services and sales; create, update and cancel bookings.

Endpoint: https://agendapro.usefulapi.io/mcp (streamable-http)

Repository · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count24
Latency896 ms
Last checked (UTC)2026-10-24T11:30:15.236Z

Health history

Checked (UTC)StatusLatencyError
2026-10-24T11:30:15.236ZHealthy896

Tools (24)

agendapro_list_locationsList the business's locations (sucursales / locales): id, name, address, phone, email, timezone, opening hours and country. Location ids are needed for bookings, slots and sales filters. GET /v3/locations.
agendapro_get_locationOne location by id, with address, coordinates, timezone and weekly opening hours. GET /v3/locations/{id}.
agendapro_list_servicesList the services (treatments, classes, sessions) the business offers: id, name, price, duration, type, category, whether online booking/payment is on, and the location. Service ids are needed to book. GET /v3/services.
agendapro_get_serviceOne service by id, including its category, images and the providers who perform it. GET /v3/services/{id}.
agendapro_list_service_categoriesList service categories, ordered as the business arranges them. GET /v3/categories.
agendapro_list_providersList service providers (the staff who take bookings): id, public name, location, active flag, online-booking flag and working hours. Provider ids are needed to book. GET /v3/providers.
agendapro_get_providerOne service provider by id, with biography, images and working hours including breaks. GET /v3/providers/{id}.
agendapro_list_bookingsList bookings (reservas / appointments) with time, status, service, provider, client id, location, price and the linked sale. AgendaPro requires at least ONE of client_id, location_id, service_id or service_provider_id; dates only narrow the result. A sale may be a membership covering several bookin
agendapro_get_bookingOne booking by id with status, service, provider, client id, location, prices, notes and the linked sale. GET /v3/bookings/{id}.
agendapro_list_available_slotsFree booking time windows at a location on one date (optionally for one service and/or provider): start/end time, provider, plus a metadata summary (service duration, slot count). Use before creating a booking. GET /v3/available_slots.
agendapro_create_bookingWRITE: create a booking for an existing client, service, provider and location. Check agendapro_list_available_slots first. status_id must be a non-cancelled status: copy the status.id of an existing booking (agendapro_list_bookings). AgendaPro does NOT send email/SMS/WhatsApp notifications for book
agendapro_update_bookingWRITE: change an existing booking (partial update: only the fields you pass change): move it, switch service/provider/location, change status, price or notes. The merchant's customer policy applies: a change too close to the start time, or past the maximum number of changes, is refused with HTTP 422
agendapro_cancel_bookingWRITE: cancel a booking. This cannot be undone through the API. The merchant's customer policy applies: a cancellation that is disabled, too close to the start time or past the maximum number of changes is refused with HTTP 422 (tell the user the merchant does not allow it; do not retry). Confirm wi
agendapro_list_clientsList the business's clients (customers) page by page: name, email, phone, identification number, address, birth date, record number, active flag. Personal data: only use it for the task at hand. To find one person use agendapro_search_clients. GET /v3/clients.
agendapro_search_clientsFind clients by free text (name, email, phone, identification number or record number): a short ranked list with id, full name, email, phone. The fastest way to get a client_id. GET /v3/clients/quick-search.
agendapro_get_clientOne client by id with contact details, address, birth date, record number and active flag. GET /v3/clients/{id}.
agendapro_list_client_custom_attributesThe custom attribute values stored for one client (id, name, datatype, value). GET /v3/clients/{id}/custom_attributes.
agendapro_list_custom_attributesThe custom client fields the business defined (id, name, datatype, mandatory, group, choices). Use the template ids when setting custom_attributes on a client. GET /v3/custom_attributes.
agendapro_create_clientWRITE: create a new client. first_name is required and at least one of last_name, email or phone must also be given (AgendaPro's rule). Search first (agendapro_search_clients) to avoid duplicates; not idempotent. No message is sent to the client. POST /v3/clients.
agendapro_update_clientWRITE: change an existing client (partial update: only the fields you pass change; it overwrites the stored value). PATCH /v3/clients/{id}.
agendapro_list_salesList sales (ventas): status (partially_paid, paid, canceled, refunded), paid and pending amounts, paid-at time, location, client id and the payment transactions. Filter by paid date range, location or client. GET /v3/sales.
agendapro_get_saleOne sale by id with amounts, status, location and its payment transactions (amount, paid-at, payment method). GET /v3/sales/{id}.
agendapro_list_productsList retail products in the catalog: name, SKU, price, active flag, category, brand and display. GET /v3/products.
agendapro_get_productOne catalog product by id with description, SKU, price, category, brand and display. GET /v3/products/{id}.