Progenda MCP by usefulapi

by FastDrop

MCP MCP VERIFIED Verified 2 hours ago Registry import free

Read patients, calendars, appointments and open slots; book and move appointments in Progenda.

Read patients, calendars, appointments and open slots; book and move appointments in Progenda. Official MCP Registry: io.usefulapi/progenda@1.0.0. Remote endpoint: https://progenda.usefulapi.io/mcp

Problem it solves

Discoverable MCP server listed in the official MCP Registry.

How it's different

Remote MCP endpoint ingested from the official registry and probed by FastDrop.

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.usefulapi/progenda and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Claim this listing

Tools this endpoint exposes

Read directly from the endpoint on 1 Nov 2026. Not supplied by the maker.

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).