Skip to main content
Glama
sanjibani

open-dental-mcp

by sanjibani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to open-dental-mcp

No user-submitted related servers found.

    Related Servers

    • Carebit MCP server

      dragosh29
      A
      license
      B
      quality
      C
      maintenance
      Enables Claude, ChatGPT and other MCP clients to read practice-management data including organization, clinicians, diaries, availability, bookings, patients, invoices, payments, staff tasks, services, and locations, and optionally create staff tasks, create bookings, and cancel bookings.
      15
      MIT

    • clinica-mcp-server

      dylanbc1
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables dental clinic staff to manage appointments, verify patient affiliation, and track accounts receivable through MCP tools, with OAuth 2.1, per-tool scopes, and human approval required for every mutation.
      MIT

    • Cliniko MCP Server

      yasboop
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables integration with the Cliniko practice management system through MCP tools and resources. Supports patient management, appointment scheduling, and practice data access through natural language interactions.
      -

    • CharmHealth MCP Server

      Talha-2
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs and MCP clients to interact with patient records, encounters, and practice information through tools for clinical, scheduling, messaging, and administrative workflows.
      MIT

    • Conselho Regional de

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying the Regional Dental Council of Rio Grande do Sul (Brazil) professional registration database through a read-only MCP tool. Works with any MCP client via HTTP with prepaid credits.
      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.6/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a clear and distinct purpose, targeting different entities (appointments, patients, procedures, recalls, clinics, etc.) with no overlap or ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using lowercase with underscores (e.g., create_appointment, list_providers), making them predictable and easy to understand.

    Tool Count5/5

    With 14 tools covering core dental practice operations, the count is well-scoped and appropriate for the domain, avoiding bloat or insufficiency.

    Completeness2/5

    The tool set is predominantly read-focused, missing critical write operations such as creating patients or updating/deleting appointments, which limits agent autonomy and may cause failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources