Skip to main content
Glama
README.md
# @striderlabs/mcp-teladoc

[![MCP](https://img.shields.io/badge/MCP-Compatible-green)](https://modelcontextprotocol.io)
[![npm](https://img.shields.io/npm/v/@striderlabs/mcp-teladoc)](https://www.npmjs.com/package/@striderlabs/mcp-teladoc)

MCP server connector for Teladoc telehealth platform. Enable AI agents to search providers, book virtual appointments, manage prescriptions, and message healthcare providers.

## Installation

```bash
npx @striderlabs/mcp-teladoc
```

Or install globally:

```bash
npm install -g @striderlabs/mcp-teladoc
```

## Configuration

Set environment variables:

```bash
export TELADOC_EMAIL="your-email@example.com"
export TELADOC_PASSWORD="your-password"
export TELADOC_HEADLESS="true"  # optional, defaults to true
```

## Tools

| Tool | Description |
|------|-------------|
| `search_providers` | Search Teladoc providers by specialty, condition, gender, or language |
| `get_provider_details` | Get detailed information about a specific provider |
| `list_appointments` | List upcoming and past appointments |
| `book_appointment` | Book a new virtual appointment |
| `cancel_appointment` | Cancel an existing appointment |
| `get_prescriptions` | View prescription history |
| `send_message` | Send secure message to your provider |
| `get_visit_history` | Get past visit summaries |

## Usage with Claude Desktop

Add to your `claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "teladoc": {
      "command": "npx",
      "args": ["@striderlabs/mcp-teladoc"],
      "env": {
        "TELADOC_EMAIL": "your-email@example.com",
        "TELADOC_PASSWORD": "your-password"
      }
    }
  }
}
```

## License

MIT

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.