Skip to main content
Glama
markswendsen-code

Teladoc MCP Server

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Teladoc MCP Server

No user-submitted related servers found.

    Related Servers

    • vClinic MCP Server by v-clinic

      vClinic MCP Serverofficial

      v-clinic
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage virtual clinic data including patients, visits, diagnoses, treatments, lab/radiology orders, and search medical literature and internal knowledge base.
      -
    • Appendix by appendixhealth

      Appendixofficial

      appendixhealth
      F
      license
      Not graded
      quality
      C
      maintenance
      Appendix turns any AI health conversation into a board-certified physician's opinion — with a real prescription when clinically appropriate. Search medical literature and submit a clinical encounter for review, all from your agent.
      2
      -

    • MCP Cliniko Server

      BoabAI
      F
      license
      B
      quality
      D
      maintenance
      Provides comprehensive integration with the Cliniko API for healthcare practice management, including patient, appointment, and invoice administration. It enables tools for complex clinical workflows and direct access to practice resources through the Model Context Protocol.
      27
      2
      -
    • ClawCall MCP Server by ClawCall-Dev

      ClawCall MCP Serverofficial

      ClawCall-Dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to make real outbound phone calls to US/Canada numbers, handle conversations, and return transcripts and recordings via the Model Context Protocol.
      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

    B3.3/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: booking vs. canceling appointments, listing vs. getting details, searching vs. messaging providers, and accessing prescriptions vs. visit history. The descriptions make it easy for an agent to differentiate between them.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., book_appointment, cancel_appointment, get_prescriptions), with clear and predictable naming conventions throughout the set. There are no deviations or mixed styles.

    Tool Count5/5

    With 8 tools, this server is well-scoped for a Teladoc healthcare domain, covering core functionalities like appointment management, provider interaction, and record access without being overly sparse or bloated.

    Completeness4/5

    The toolset provides strong coverage for key workflows (appointments, providers, records, messaging), but minor gaps exist, such as no tool for updating appointments or handling prescription refills, which agents might need to work around.

    Resources