clinic-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLINIC_TZ | No | Timezone for date windows / naive datetimes | America/Los_Angeles |
| DATABASE_URL | No | Shared Postgres (same as RAG app) | postgresql://rag:rag@localhost:5432/rag |
| SIMILARITY_FLOOR | No | Dense cosine gate for doc search | 0.35 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_clinic_docsA | Hybrid-search the clinic knowledge base (pgvector + full-text, RRF-fused). |
| get_patient_recordA | Look up a patient by id: name, insurance, last visit, and next confirmed appointment. |
| list_appointmentsA | List confirmed appointments between date_from and date_to (inclusive). |
| create_appointmentA | Propose a new appointment — does NOT confirm it. |
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 4 tools
Each tool addresses a distinct task: searching knowledge base, retrieving patient record, listing appointments, and creating appointment requests. No functional overlap exists.
All tools follow a consistent verb_noun snake_case pattern (search_clinic_docs, get_patient_record, list_appointments, create_appointment).
4 tools are well-scoped for a clinic management server, covering search, patient lookup, appointment listing, and appointment creation. Neither too few nor too many.
The set covers basic read and create operations, but lacks tools for updating patient records, confirming/cancelling appointments, or deleting requests, which are notable gaps for a full appointment management workflow.