AlayaCare MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | Port for SSE transport | 3000 |
| MCP_TRANSPORT | No | Transport mode: stdio or sse | stdio |
| ALAYACARE_BASE_URL | Yes | Your AlayaCare instance URL | |
| ALAYACARE_PASSWORD | Yes | Basic auth password for AlayaCare API | |
| ALAYACARE_USERNAME | Yes | Basic auth username for AlayaCare API |
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_pswsA | List all Personal Support Workers (PSWs / employees) with their home addresses and status. Use this to understand who is on the team and where they live. |
| get_pswA | Get detailed information about a single PSW / employee by their ID. |
| list_clientsA | List all clients (patients) receiving care, including their service addresses. Use this to understand where visits take place geographically. |
| get_clientA | Get detailed information about a single client / patient by their ID. |
| get_visitsB | Retrieve scheduled visits within a date range, optionally filtered by PSW or client. Returns each visit's timing, status, assigned PSW, and client. |
| get_psw_scheduleA | Get the full visit schedule for a specific PSW within a date range. Shows all their assigned clients, times, and locations. |
| get_psw_utilizationA | Calculate utilization rates for PSWs — how many hours they are scheduled versus how many hours they are available. Identifies under- or over-utilized workers. |
| find_nearest_clientsA | Given a PSW, rank all active clients by distance from the PSW's home address. Useful for identifying which clients are geographically closest and reducing travel time. |
| find_nearest_psw_for_clientA | Given a client, rank all active PSWs by how close their home is to the client's service address. Useful for finding the most travel-efficient PSW assignment. |
| analyze_schedule_travelA | Analyze a PSW's day schedule: visit order, gaps between visits, travel distances between consecutive stops, and total care hours. Identifies inefficient routing. |
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 10 tools
Each tool targets a distinct resource and action: PSW management, client management, visit retrieval, schedule analysis, utilization, and distance-based matching. Even similar tools like get_visits and get_psw_schedule differ by scope and filter, causing no real ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_psws, get_client, find_nearest_clients). The naming is predictable and clearly indicates the operation and target resource.
Ten tools is well-scoped for a home-care scheduling domain. Each tool serves a clear purpose without redundancy, covering list/get, scheduling, analysis, and optimization in a balanced way.
The server covers the read and analysis side thoroughly: PSW/client info, visit retrieval, schedule analysis, and travel optimization. Missing write operations (create/update/delete) might be intentional for an analytics tool, but there is no direct way to modify schedules or assignments, which is a minor gap.