athenahealth MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Environment | development |
| LOG_LEVEL | No | Log Level | info |
| ATHENA_VERSION | No | API Version | v1 |
| ATHENA_BASE_URL | Yes | athenahealth API Base URL | |
| ATHENA_CLIENT_ID | Yes | athenahealth API Client ID | |
| ATHENA_PRACTICE_ID | Yes | Practice ID | |
| ATHENA_CLIENT_SECRET | Yes | athenahealth API Client Secret |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_patientsB | Search for patients by name, DOB, phone, or email |
| check_drug_interactionsC | Check for drug interactions for a patient |
| create_prescriptionC | Create a new prescription for a patient |
| create_appointmentC | Create a new appointment for a patient |
| acknowledge_alertC | Acknowledge a clinical alert |
| get_clinical_summaryC | Get a comprehensive clinical summary for a patient |
| list_departmentsB | List all departments in the practice |
| list_providersC | List all healthcare providers in the practice |
| check_appointment_availabilityB | Check available appointment slots for a department and date range |
| create_patientC | Register a new patient in the system |
| get_patient_encountersC | Get all encounters for a patient |
| get_encounterC | Get details of a specific encounter |
| create_encounterC | Create a new encounter for a patient |
| update_encounterC | Update an existing encounter |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| clinical_assessment | Generate a clinical assessment prompt for a patient |
| medication_review | Generate a medication review prompt |
| care_plan | Generate a care plan prompt |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Patient Search | Search for patients by name, DOB, or other identifiers |
| Patient Details | Get detailed information about a specific patient |
| Patient Allergies | Get patient allergy information |
| Patient Problems | Get patient problem list |
| Patient Prescriptions | Get patient prescription history |
| Patient Vital Signs | Get patient vital signs history |
| Patient Lab Results | Get patient laboratory results |
| Clinical Alerts | Get clinical decision support alerts for patient |
| Provider Directory | List healthcare providers in the practice |
| Provider Details | Get detailed information about a specific provider |
| Department Directory | List departments in the practice |
TDQS
Scored across 14 tools
Each tool has a clearly distinct purpose targeting specific resources and actions in the healthcare domain, such as patient management, appointments, clinical alerts, and prescriptions. There is no significant overlap; for example, create_appointment and check_appointment_availability serve different functions, and get_encounter vs. get_patient_encounters are clearly differentiated by scope.
All tool names follow a consistent verb_noun pattern using snake_case, such as acknowledge_alert, create_appointment, and list_departments. This uniformity makes the tool set predictable and easy for an agent to navigate without confusion from mixed naming conventions.
With 14 tools, the server is well-scoped for a healthcare practice management system, covering essential operations like patient registration, appointment scheduling, clinical workflows, and data retrieval. Each tool appears necessary for the domain, avoiding bloat or thin coverage.
The tool set provides strong coverage for core healthcare workflows, including patient CRUD (create, search), appointment management, clinical encounters, and prescriptions. A minor gap exists in update/delete operations for resources like patients or prescriptions, but agents can likely work around this with the available tools.