AgendaPro MCP by usefulapi
MCP server · agendapro.usefulapi.io · found in a public list · checked since 2026-10-25
Live, handshake completed · latest check
Reads and writes AgendaPro bookings, slots, clients and services.
Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/6). What this means
Placed in Service business management: Clients, jobs, scheduling, estimates and invoices for trades, studios, coaches and other service firms.
https://agendapro.usefulapi.io/mcp MCP endpoint (Streamable HTTP)The name is the registry's label, not ours. Not reviewed by a person. See 414 endpoints from usefulapi.io.
Our checks
An unpaid request daily, from eastern North AmericaLast 2 checks, oldest to newest; room for 28 more
2 passed, 0 failed, 28 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hours | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-10-25 | 2 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-10-25 | 2 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Tools listed by the server
agendapro_cancel_bookingagendapro_create_bookingagendapro_create_clientagendapro_get_bookingagendapro_get_clientagendapro_get_locationagendapro_get_productagendapro_get_provideragendapro_get_saleagendapro_get_serviceagendapro_list_available_slotsagendapro_list_bookingsagendapro_list_client_custom_attributesagendapro_list_clientsagendapro_list_custom_attributesagendapro_list_locationsagendapro_list_productsagendapro_list_providersagendapro_list_salesagendapro_list_service_categoriesagendapro_list_servicesagendapro_search_clientsagendapro_update_bookingagendapro_update_client
- Tools
- 24
- This list since
- 2026-10-25
- First listed to us
- 2026-10-25
- List changes, 90 days
- 0
Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Interface it declares
- Protocol
- MCP 2025-06-18
- Capabilities
- promptstools
- Transports
- streamable-http
As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions
Calls it declares
agendapro_list_locations active page per_pageagendapro_get_location location_id*agendapro_list_services provider_id page per_pageagendapro_get_service service_id*agendapro_list_service_categories page per_pageagendapro_list_providers location_ids service_ids public_name active sort_by order_by page per_pageagendapro_get_provider provider_id*agendapro_list_bookings client_id location_id service_id service_provider_id scheduled status_id start_date end_date page per_pageagendapro_get_booking booking_id*agendapro_list_available_slots location_id* start_date* service_id provider_idagendapro_create_booking start_time* end_time service_id* provider_id* client_id* location_id* status_id* price notes time_resource_idagendapro_update_booking booking_id* start_time end_time service_id provider_id client_id location_id status_id price notes time_resource_id
From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Listing
In the capability tree: Business and productivity / Customer records / Service business management (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-25. Wrong place? Tell us.
In the directory: meets our listing criteria (listing-criteria/6): ✓ says what it does; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:MIA |
Live, handshake completed HTTP 200 | 1640 ms |
cloudflare:EWR |
Live, handshake completed HTTP 200 | 184 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
- Limited evidence: monitored for 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_541b03eec6a750f8