personaleasy-mcp-server
Related Servers
Alternatives to personaleasy-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceA read-only server that lets MCP clients look up appointments, patients, procedure logs, communication history, recalls, and reference data (providers, clinics, operatories, appointment types) through the Open Dental REST API. It can connect to the Remote API, a workstation's local Open Dental instance, or a loopback API Service, exposing 12 read-only tools with an enforced GET-only allowlist.12MIT
- AlicenseAqualityCmaintenanceRead-only MCP server for licensed Healthpoint HL7 FHIR API access.101Apache 2.0
- AlicenseNot gradedqualityCmaintenanceThis MCP server enables secure, read-only access to synthetic preventive-care patient records and bounded IRIS namespace health metrics through a small set of allowlisted, parameterized tools.1MIT
- AlicenseAqualityDmaintenanceMCP server for interacting with Realm MinistryPlatform data, enabling queries, record creation, and updates from any MCP client.1MIT
- AlicenseBqualityCmaintenanceMCP server for the DataGate billing platform API, providing read-only tools to manage customers, invoices, products, agreements, sites, and payments.1324 PyPIMIT
- AlicenseAqualityDmaintenanceEnables interaction with Open Dental practice management software, allowing reading of patients, appointments, providers, procedures, and recalls, as well as writing communications back to patient charts via MCP clients.147MIT
TDQS
Scored across 4 tools
Each tool targets a distinct resource: appointments (agendamentos), production KPIs, provider lookup by CPF, and units. There is no overlap in purpose, and the descriptions clearly differentiate them.
All tools follow the pattern `personaleasy_get_<resource>`, using the same prefix and verb. The resource names are in Portuguese, which is consistent with the domain, though the prefix adds redundancy.
Four tools is appropriate for a focused server that provides read-only access to core entities (appointments, KPIs, providers, units). It is not too few for the apparent scope, and each tool serves a clear purpose.
The tool set covers reading key entities, but there are obvious gaps: no filtering by provider for appointments, no tool for patients or procedures, and only a CPF-based lookup for providers. Write operations (create, update, delete) are absent, limiting the surface to querying.