Skip to main content
Glama
Sign In
Open Dental MCP

Open Dental MCP

by MaxilloCA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Open Dental MCP

No user-submitted related servers found.

    Related Servers

    • appd-mcp

      jagalliers
      A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server for AppDynamics that exposes 12 task-oriented tools to query applications, topology, metrics, snapshots, health rules, anomalies, events, alerting config, analytics events, and dependency maps via OAuth API-client credentials.
      12
      1
      MIT

    • dms-mcp-server

      mergi72
      A
      license
      A
      quality
      B
      maintenance
      Read-only MCP server that lets AI clients query DMS repositories through a local bridge, supporting tools for health checks, listing connections and items, retrieving item info, and reading documents. Credentials are handled securely via a separate broker.
      7
      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
      7
      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.7/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool maps to a distinct resource/action: exact-ID get_* fetches, plural find_* searches, list_* reference data, and health_check. The clinical history tools (commlogs, recalls, procedurelogs) are clearly separated by domain, so misselection is unlikely.

    Naming Consistency4/5

    Names are consistently snake_case with a verb_noun pattern such as get_patient, find_appointments, and list_providers. health_check is a minor deviation, but otherwise the get/find/list verbs are used coherently.

    Tool Count5/5

    The 12 tools form a well-scoped read-oriented surface for patients, appointments, recalls, notes, procedures, and reference data. There is little redundancy and no obvious padding.

    Completeness3/5

    Core read lookups are covered, but the surface is entirely read-only: there are no create/update/cancel operations for appointments or patient records, and broader dental entities such as treatment plans, insurance/claims, and payments are absent. These are notable gaps if the agent is expected to manage the practice rather than just query it.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources