Which integrations are available for this server?

Provides medical appointment scheduling capabilities within VS Code's Copilot Chat, enabling AI agents to search doctors, check availability, book/cancel appointments, list appointments, recommend specialists, and access patient history through MCP tools and prompts. Integrates with a Hono REST API backend that provides the underlying data store and business logic for medical appointment operations, with the MCP server acting as a protocol layer that exposes the API's functionality through MCP primitives. Runs on Node.js as the JavaScript runtime environment for both the MCP server process and the Hono REST API service that powers the medical appointment scheduling backend. Uses npm as the package manager for dependencies and scripts to build, run, and develop the MCP server and its associated REST API service for medical appointment management. Built with TypeScript as the primary implementation language for both the MCP server and the underlying REST API service, providing type safety and developer tooling for the medical appointment scheduling system. Uses Zod for runtime type validation and schema definition throughout the MCP server and REST API, ensuring data integrity and proper validation of medical appointment data structures.

How do I use MCP Medical Appointments Demo?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP Medical Appointments Demo Find a cardiologist and check their available slots for next Monday." That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

de en es ja ko ru zh

MCP Medical Appointments Demo

by bicatu

Overview Schema Related Servers Score Discussions

TypeScript

Local

MCP Medical Appointments Demo

A working reference for the Model Context Protocol — tools, resources, prompts, elicitation, sampling, and completion — built around a medical appointment scheduling domain.

Built with TypeScript, Hono, MCP SDK, and Zod.

Features

MCP Server Primitives

Primitive	Name	Description
Tool	`search_doctors`	Search doctors by name or specialty
Tool	`get_available_slots`	Get available time slots for a doctor on a date
Tool	`book_appointment`	Book an appointment (uses elicitation for confirmation)
Tool	`cancel_appointment`	Cancel an appointment (uses elicitation for confirmation)
Tool	`list_appointments`	List appointments with filters
Tool	`recommend_specialist`	Symptom-based specialist recommendation (uses sampling)
Resource	`specialties://list`	Static list of all medical specialties
Resource	`doctor://{doctorId}/profile`	Dynamic doctor profile with template
Resource	`patient://{patientId}/summary`	Patient info + appointment history
Resource	`appointment://{appointmentId}`	Full appointment details
Prompt	`schedule-appointment`	Guided appointment scheduling workflow (with completion)
Prompt	`patient-history`	Patient history review (with completion)
Prompt	`triage-symptoms`	Symptom triage and specialist recommendation

MCP Client Features

Feature	How It's Used
Elicitation	`book_appointment` and `cancel_appointment` ask the user to confirm before proceeding
Sampling	`recommend_specialist` uses LLM sampling to match symptoms to specialties
Roots	Server registers a root for the medical appointments workspace
Completion	Prompts use `completable()` for auto-completing specialty names and patient IDs

Agent Skill

A SKILL.md for this domain is provided at .github/skills/medical-appointments/SKILL.md. It mirrors the capabilities of the MCP server without requiring the MCP protocol — any compatible agent (GitHub Copilot, Claude Code, etc.) can load it on demand.

What the Skill Covers

Skill Workflow	Equivalent MCP Primitive
Find Doctors	`search_doctors` tool
Check Available Slots	`get_available_slots` tool
Book Appointment	`book_appointment` tool
Cancel Appointment	`cancel_appointment` tool
List Appointments	`list_appointments` tool
Recommend Specialist	`recommend_specialist` tool
Schedule Appointment	`schedule-appointment` prompt
Patient History	`patient-history` prompt
Triage Symptoms	`triage-symptoms` prompt

The skill interacts with the REST service directly over HTTP using the agent's native tool access.

Skill Limitations

The following MCP server features have no equivalent in the agentskills.io specification and are therefore not replicated:

MCP Feature	Limitation
Elicitation	`book_appointment` and `cancel_appointment` use a native UI confirmation dialog in the MCP server. Skills have no equivalent; the agent requests confirmation through conversation instead.
Sampling	`recommend_specialist` calls a sub-LLM via MCP sampling to match symptoms to specialties. The skill uses the agent's own reasoning directly (functionally equivalent).
Argument completion	MCP prompts use `completable()` to auto-suggest specialty names and patient IDs in the client UI. Skills provide no interactive completion.
Roots	The MCP server registers a workspace root (`roots/list`). This is an MCP transport concept with no skill equivalent.
VS Code-specific skill fields	Fields such as `argument-hint`, `user-invocable`, and `disable-model-invocation` are VS Code Copilot extensions to the SKILL.md format. They are not part of the agentskills.io spec and are omitted to keep the skill portable.

Quick Start

Prerequisites

Node.js >= 22.0.0
VS Code with GitHub Copilot (for MCP integration)

1. Install and start the REST API

npm install
npm run dev:service

You should see:

Bootstrapped: 8 specialties, 12 doctors, 5 patients
Medical Appointment Service running on http://localhost:3000

2. Connect the MCP Server in VS Code

The .vscode/mcp.json file is already configured. VS Code will automatically detect and offer to start the MCP server. Alternatively, run it manually:

npm run dev:mcp

3. Try it out

In VS Code's Copilot Chat (Agent mode), try:

"Search for cardiologists"
"What slots does Dr. Sarah Chen have available next Monday?"
"Book an appointment with doc-3 for patient pat-1"
"Show me Alice Johnson's appointment history"
"I've been having severe headaches and dizziness — what specialist should I see?"

Or use the prompts from the prompt picker:

Schedule Appointment — guided scheduling workflow
Patient History — review a patient's visits
Triage Symptoms — symptom-based specialist matching

Architecture

┌─────────────────┐     stdio      ┌───────────────────┐     HTTP     ┌──────────────────┐
│   VS Code /     │◄──────────────►│   MCP Server      │─────────────►│  Hono REST API   │
│   MCP Client    │                │   (TypeScript)    │  localhost   │  (localhost:3000)│
└─────────────────┘                └───────────────────┘              └──────────────────┘
                                     Tools, Resources,                  In-memory store
                                     Prompts                            + JSON bootstrap

The project uses a two-process design:

Hono REST API — HTTP service with an in-memory data store, bootstrapped from JSON seed files in data/.
MCP Server — Connects via stdio and exposes the REST API through MCP primitives (tools, resources, prompts).

The MCP server never touches the data store directly — it calls the REST API through an HTTP client, keeping the two layers cleanly separated.

REST API Endpoints

Method	Endpoint	Description
`GET`	`/api/specialties`	List all specialties
`GET`	`/api/specialties/:id`	Get specialty by ID
`GET`	`/api/doctors`	List doctors (filters: `?specialtyId=`, `?name=`)
`GET`	`/api/doctors/:id`	Get doctor by ID
`GET`	`/api/doctors/:id/slots?date=YYYY-MM-DD`	Get available slots
`GET`	`/api/patients`	List all patients
`GET`	`/api/patients/:id`	Get patient by ID
`POST`	`/api/patients`	Create a patient
`GET`	`/api/appointments`	List appointments (filters: `?patientId=`, `?doctorId=`, `?status=`, `?date=`)
`GET`	`/api/appointments/:id`	Get appointment by ID
`POST`	`/api/appointments`	Book an appointment
`PATCH`	`/api/appointments/:id/cancel`	Cancel an appointment
`PATCH`	`/api/appointments/:id/complete`	Complete an appointment

Project Structure

mcp-demo/
├── data/
│   ├── specialties.json      # 8 medical specialties
│   ├── doctors.json           # 12 doctors across specialties
│   └── patients.json          # 5 sample patients
├── src/
│   ├── types.ts               # Shared domain types
│   ├── service/
│   │   ├── store.ts           # In-memory data store
│   │   ├── app.ts             # Hono app composition
│   │   ├── main.ts            # Service entry point
│   │   └── routes/            # REST route handlers
│   └── mcp/
│       ├── api-client.ts      # HTTP client for the REST API
│       ├── tools.ts           # MCP tool registrations
│       ├── resources.ts       # MCP resource registrations
│       ├── prompts.ts         # MCP prompt registrations
│       └── server.ts          # MCP server entry point
├── .vscode/
│   └── mcp.json               # VS Code MCP server config
├── package.json
└── tsconfig.json

Scripts

Command	Description
`npm run dev:service`	Start the Hono REST API with hot reload
`npm run dev:mcp`	Start MCP server in stdio mode
`npm run build`	Compile TypeScript to `dist/`
`npm run typecheck`	Type-check without emitting files

Domain Model

Entity	Description
Specialty	Medical specialty (Cardiology, Dermatology, etc.)
Doctor	Has a specialty, available days, working hours, and slot duration
Patient	Name, email, phone, date of birth
Appointment	Links a patient to a doctor at a specific date/time with a reason and status
TimeSlot	Available or booked time window for a doctor on a given day

Configuration

The REST API listens on port 3000 by default. The MCP server communicates with the API over http://localhost:3000 and connects to VS Code via stdio.

Seed data (specialties, doctors, patients) is loaded from the data/ directory on startup. Edit those JSON files to customize the demo dataset.

Contributing

Contributions are welcome. Fork the repo, create a feature branch, and open a pull request.

License

MIT

This server cannot be installed

security - not tested

license - not found

quality - not tested

How are these scores calculated?

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security
Open Source Has a Bot Problem
By punkpeye on March 19, 2026.
open source

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bicatu/mcp-skills-demo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

MCP Medical Appointments Demo

Table of Contents

Features

MCP Server Primitives

MCP Client Features

Agent Skill

What the Skill Covers

Skill Limitations

Quick Start

Prerequisites

1. Install and start the REST API

2. Connect the MCP Server in VS Code

3. Try it out

Architecture

REST API Endpoints

Project Structure

Scripts

Domain Model

Configuration

Contributing

License

Resources

Looking for Admin?

Latest Blog Posts

MCP directory API