io.usefulapi/progenda · v1.0.0 · health-and-science
Progenda MCP by usefulapi is healthy: it completed an MCP handshake in 475 ms and exposes 12 tools.
Read patients, calendars, appointments and open slots; book and move appointments in Progenda.
Endpoint: https://progenda.usefulapi.io/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 12 |
| Latency | 475 ms |
| Last checked (UTC) | 2026-11-01T19:50:23.845Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-11-01T19:50:23.845Z | Healthy | 475 |
progenda_list_centers | List the centers (practices) your Progenda user can access. Start here: the center id is needed by the patient tools. Progenda API: GET /api/v2/centers. |
progenda_list_calendars | List the calendars (one agenda per practitioner) your Progenda user can access. The calendar id is needed by the appointment and service tools. Progenda API: GET /api/v2/calendars. |
progenda_list_patients | List the patients of a center, 1000 per page. Contains personal and health-adjacent data: fetch only what the user asks for. Progenda API: GET /api/v2/centers/{center_id}/patients. |
progenda_get_patient | Get one patient by your own remote_id. Progenda API: GET /api/v2/centers/{center_id}/patients/remote_id:{remote_id}. |
progenda_list_appointments | List the appointments of one calendar, optionally between two Unix times (start, stop) or updated since a time. Progenda API: GET /api/v2/calendars/{calendar_id}/appointments. |
progenda_get_appointment | Get one appointment by your own remote_id. Progenda API: GET /api/v2/calendars/{calendar_id}/appointments/remote_id:{remote_id}. |
progenda_list_services | List the services (appointment types) of one calendar. The service remote_id is used when you create an appointment. Progenda API: GET /api/v2/calendars/{calendar_id}/services. |
progenda_get_suggestions | Compute suggested free slots in one calendar for one service. Live route: GET /api/v2/calendars/{calendar_id}/suggestions?service_id= (the route named in the docs answers 404). |
progenda_create_patient | Create a patient in a center under your own remote_id. Creates a new record each time it runs with a new remote_id; use progenda_update_patient to change an existing one. Progenda API: POST /api/v2/centers/{center_id}/patients. |
progenda_update_patient | Update a patient found by your own remote_id. The four contact fields are required by the API: send the current values for the ones you do not change. Progenda API: PUT /api/v2/centers/{center_id}/patients/remote_id:{remote_id}. |
progenda_create_appointment | Create an appointment in a calendar under your own remote_id, for a patient remote_id and a service remote_id. Each run creates a new appointment. Progenda API: POST /api/v2/calendars/{calendar_id}/appointments. |
progenda_update_appointment | Change an appointment found by your remote_id: time, status (booked, cancelled, noshow), arrival or no-show. Send only the fields to change. Progenda API: PUT /api/v2/calendars/{calendar_id}/appointments/remote_id:{remote_id}. |