clinic-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PROFILE | No | The access profile: readonly, booking, or full. | readonly |
| SUT_BASE_URL | No | Base URL of the clinic booking API. | http://127.0.0.1:3000 |
| MCP_SESSION_ROLE | No | Role for the MCP session: patient, doctor, or none. | patient |
| SUT_ACCESS_TOKEN | No | The caller's access token. No default, deliberately. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_specialtiesA | List the medical specialties this clinic staffs. Returns specialty names only. Takes no arguments. |
| list_doctorsA | List doctors, optionally narrowed to one specialty. Returns each doctor's id, name, specialty and clinic address. |
| list_my_appointmentsA | List the appointments belonging to the authenticated patient. Returns id, status, doctor and slot time for each. |
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 3 tools
Each tool addresses a distinct resource: specialties, doctors, and appointments. There is no overlap or ambiguity between the three operations.
All tool names follow a consistent 'list_' + noun pattern. The 'my' in list_my_appointments is a minor modifier but does not break the naming convention.
Three tools is a small but reasonable set for a read-only clinic lookup server. While the scope is narrow, each tool serves a clear purpose and the count is not deficient enough to score lower.
The server only provides list/read operations. There are no tools to create, update, or cancel appointments, which are core actions for a clinic appointment system. This creates significant gaps for agents needing to manage appointments.