Keka employee MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KEKA_CURL | No | The full curl command copied from a Keka dashboard request (DevTools > Network > Fetch/XHR > right-click a request whose path starts with /k/default/api/me/ > Copy as cURL). The company comes from the URL and the access token comes from the Authorization header. | |
| KEKA_TOKEN | No | The value after 'Authorization: Bearer' from the same Keka dashboard request. Required together with KEKA_COMPANY. KEKA_BEARER is accepted as another name for this variable. | |
| KEKA_BEARER | No | Accepted as another name for KEKA_TOKEN: the value after 'Authorization: Bearer'. | |
| KEKA_COOKIE | No | Optional. The Cookie header from the same Keka dashboard request. | |
| KEKA_COMPANY | No | The label in https://company.keka.com. Required together with KEKA_TOKEN. KEKA_SUBDOMAIN is accepted as another name for this variable. | |
| KEKA_SUBDOMAIN | No | Accepted as another name for KEKA_COMPANY: the label in https://company.keka.com. |
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 |
|---|---|
| get_profile_infoC | Signed-in employee's profile header. |
| get_profile_completionB | Whether the signed-in employee has completed their profile. |
| get_id_cardB | Signed-in employee's ID card details. |
| get_timelineC | Signed-in employee's timeline events. |
| get_preferencesC | Signed-in employee's Keka preferences. |
| get_probation_policyB | Signed-in employee's probation policy. |
| get_exit_statusA | Signed-in employee's resignation and exit details, when the module is enabled. |
| get_leave_balanceC | Remaining time-off summary for the signed-in employee. |
| get_leave_requestsC | Leave requests for the signed-in employee on one date. |
| get_leave_transactionsC | Leave transactions for the signed-in employee. |
| get_leave_statsB | Leave stats for the signed-in employee on one date. |
| get_holidaysB | Holiday list from the signed-in employee's leave plan. |
| get_weekly_off_policyC | Weekly off policy for the signed-in employee. |
| get_leave_plan_statusB | Whether a leave plan is assigned to the signed-in employee. |
| get_pending_leave_encashmentA | Pending leave encashment requests for the signed-in employee. |
| get_attendance_statusC | Today's punch, current shift clock-in, and attendance summaries for the signed-in employee. |
| get_attendance_calendarC | Attendance calendar for the signed-in employee. |
| get_attendance_summaryC | Current attendance summary for the signed-in employee. |
| get_shift_detailsB | Shift and weekly-off details for the signed-in employee. |
| get_shift_policyC | Shift policy for the signed-in employee. |
| get_last_week_attendanceB | Last week's attendance stats for the signed-in employee. |
| get_attendance_requestsB | Attendance regularization requests for the signed-in employee. |
| get_adjustment_requestsC | Attendance adjustment requests for the signed-in employee. |
| get_partial_day_requestsC | Partial-day requests for the signed-in employee. |
| get_remote_work_requestsC | Remote clock-in and working-remotely requests for the signed-in employee. |
| get_attendance_policyC | Attendance capture scheme and tracking policy for the signed-in employee. |
| get_pending_attendance_countB | Count of the signed-in employee's pending attendance requests. |
| get_current_shiftsB | Current shift schedules for the signed-in employee. |
| get_expense_policyB | Expense policy for the signed-in employee. |
| get_pending_expensesB | Pending expense bills for the signed-in employee. |
| get_expense_claimsC | Pending and past expense claims for the signed-in employee. |
| get_advance_requestsB | Pending and unclaimed advance requests for the signed-in employee. |
| get_timesheet_profileC | Timesheet profile for the signed-in employee. |
| get_timesheetsC | Timesheet summary for the signed-in employee. |
| get_timesheets_dueC | Timesheets due for the signed-in employee. |
| get_rejected_timesheetsB | Rejected timesheets for the signed-in employee. |
| get_timesheet_policyC | Timesheet policy for the signed-in employee. |
| get_my_assetsC | Assets assigned to the signed-in employee. |
| get_asset_requestsC | Asset requests made by the signed-in employee. |
| get_payroll_preferencesC | Payroll preferences for the signed-in employee. |
| get_pending_approvalsB | Count of inbox items waiting on the signed-in employee. |
| get_feedback_settingsC | Feedback settings visible to the signed-in employee. |
| get_praise_badgesC | Praise badges available to the signed-in employee. |
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 43 tools
Many tools cluster around attendance and leave with subtle distinctions (e.g., get_attendance_status vs get_attendance_summary vs get_last_week_attendance; get_attendance_requests vs get_adjustment_requests vs get_partial_day_requests). Descriptions help but overlap remains, making misselection likely for similar queries. Other areas like profile, assets, and expenses are clearer and distinct.
All 43 tools follow a consistent get_<snake_case_noun_phrase> pattern with no deviations or mixed conventions. The naming is predictable and readable throughout the entire set.
43 tools is excessive for a single-employee self-service surface, effectively exposing one endpoint per granular data point. Many could be consolidated into parameterized or grouped queries, and the count is well beyond the typical 3-15 range for a well-scoped server.
The surface is entirely read-only; there are no tools to clock in/out, apply for leave, submit timesheets, file expense claims, request assets, or perform approvals despite pending approval counts being exposed. Core employee self-service actions are missing, making the toolset incomplete for its domain.