Teladoc MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELADOC_EMAIL | Yes | Your Teladoc email address | |
| TELADOC_HEADLESS | No | Whether to run in headless mode. Optional, defaults to true. | true |
| TELADOC_PASSWORD | Yes | Your Teladoc password |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_providersC | Search Teladoc providers by specialty, condition, gender, or language |
| get_provider_detailsC | Get detailed info about a specific Teladoc provider |
| list_appointmentsB | List upcoming and past Teladoc appointments |
| book_appointmentC | Book a Teladoc virtual appointment |
| cancel_appointmentC | Cancel a Teladoc appointment |
| get_prescriptionsB | Get prescription history from Teladoc |
| send_messageC | Send a message to a Teladoc provider |
| get_visit_historyC | Get past visit history and summaries |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
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.
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.
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.
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.