Skip to main content
Glama
marqprochat

personaleasy-mcp-server

by marqprochat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to personaleasy-mcp-server

No user-submitted related servers found.

    Related Servers

    • health-example

      pietrodileo
      A
      license
      Not graded
      quality
      B
      maintenance
      This 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.
      1
      MIT

    • datagate-mcp

      hyamie
      A
      license
      B
      quality
      C
      maintenance
      MCP server for the DataGate billing platform API, providing read-only tools to manage customers, invoices, products, agreements, sites, and payments.
      13
      MIT

    • open-dental-mcp

      sanjibani
      A
      license
      A
      quality
      D
      maintenance
      Enables 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.
      14
      5
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources