Keka MCP Server Abstraction Layer

This specialized Model Context Protocol (MCP) server acts as a standardized gateway for interfacing with the proprietary Keka Human Capital Management system. It transforms Keka's various application programming interfaces (APIs) for staff administration, time tracking, leave management, financial statement generation, and public holiday data into callable MCP operations. It mandates robust OAuth2 credential exchange for access control and utilizes a component-based design for enhanced adaptability.

---

Core Capabilities

• Secured Access Protocol: Leverages OAuth2 flows for authenticated connectivity to the Keka ecosystem.
• Operation Abstraction: Exposes native Keka services as discrete, easily consumable MCP operations.
• Design Philosophy: Built upon a clean, TypeScript foundation promoting scalability and adherence to established coding conventions.
• Deployment Readiness: Includes necessary configuration (Dockerfile) for streamlined containerized deployment.

---

Configuration Requirements (Environment Variables)

Define a .env file in the project root directory containing necessary secrets:

KEKA_CLIENT_ID=your_keka_client_id_here KEKA_CLIENT_SECRET=your_keka_client_secret_here KEKA_REFRESH_TOKEN=your_keka_refresh_token_here

Optional Endpoint Override:

KEKA_API_BASE_URL=https://master.kekademo.com/api/v1

---

Exposed MCP Operations

1. keka_get_employee_profile

Retrieves comprehensive biographical and employment data for a designated staff member. - Parameters: - employee_id (Text, Mandatory): Unique identifier (UUID) for the personnel record. - Invocation Example:

{ "employee_id": "EMP123456" }

---

2. keka_get_attendance

Fetches the time-clock records for an individual across a specified temporal span. - Parameters: - employee_id (Text, Mandatory) - start_date (Text, Mandatory, Format: YYYY-MM-DD) - end_date (Text, Mandatory, Format: YYYY-MM-DD) - page (Integer, Optional, Default: 1) - page_size (Integer, Optional, Default: 100) - Invocation Example:

{ "employee_id": "EMP123456", "start_date": "2024-01-01", "end_date": "2024-01-31", "page": 1, "page_size": 50 }

---

3. keka_apply_leave

Submits a formal request for time off on behalf of an employee. - Parameters: - employee_id (Text, Mandatory) - start_date (Text, Mandatory) - end_date (Text, Mandatory) - leave_type (Text, Mandatory, Corresponds to leave type UUID) - reason (Text, Mandatory) - Invocation Example:

{ "employee_id": "EMP123456", "start_date": "2024-04-10", "end_date": "2024-04-12", "leave_type": "ANNUAL", "reason": "Family function" }

---

4. keka_get_leave_balances

Retrieves a complete summary of accrued and available leave entitlements for personnel. - Parameters: - employee_id (Text, Mandatory) - Invocation Example:

{ "employee_id": "EMP123456" }

---

5. keka_get_payslip

Fetches the official salary statement document for a specified month and fiscal year. - Parameters: - employee_id (Text, Mandatory) - month (Text, Mandatory, Numeric representation, e.g., "4" for April) - year (Text, Mandatory, e.g., "2024") - Invocation Example:

{ "employee_id": "EMP123456", "month": "4", "year": "2024" }

---

6. keka_get_upcoming_holidays

Queries the system for the schedule of forthcoming organizational non-working days. - Parameters: None. - Invocation Example:

{}

---

7. keka_view_leave_history

Displays a chronological log of all past leave applications and their disposition. - Parameters: - employee_id (Text, Mandatory) - start_date (Text, Optional) - end_date (Text, Optional) - status (Text, Optional, e.g., "APPROVED") - page (Integer, Optional, Default: 1) - page_size (Integer, Optional, Default: 100) - Invocation Example:

{ "employee_id": "EMP123456", "start_date": "2024-01-01", "end_date": "2024-04-01", "status": "APPROVED", "page": 1, "page_size": 20 }

---

8. keka_get_leave_types

Retrieves a catalogue of all defined categories of permissible leave. - Parameters: None. - Invocation Example:

{}

---

Operational Guidance

Local Execution (Node.js Environment)

1. Dependency Installation: sh npm install

2. Compilation Step: sh npm run build

3. Server Initialization: sh node build/index.js

Containerized Deployment (Docker)

1. Image Construction: sh docker build -t keka-mcp .

2. Runtime Execution (Mapping environment variables): sh docker run --env-file .env keka-mcp

---

Component Map

• src/index.ts — Central execution manifest, defining the MCP interface and underlying Keka adaptor logic.
• .env — Configuration file storing sensitive authorization tokens.
• Dockerfile — Blueprint for creating the deployment artifact.
• package.json — Manifest detailing project dependencies and executable scripts.

---

Collaboration Guidelines

We encourage contributions! When submitting modifications, ensure new functions adhere to the existing handler module pattern and incorporate comprehensive failure remediation mechanisms.

---

Licensing Status

This software is distributed under the MIT License.

---

Informational Links

• Keka Developer Resource Portal
• Model Context Protocol (MCP) Specification

---

This integration service is architected following industry-leading standards for MCP connectivity.

WIKIPEDIA: Business management systems encompass the methodologies, applications, controls, and computational frameworks utilized by organizations to navigate market volatility, maintain a competitive edge, and enhance overall operational efficacy. These systems can be segmented by functional area, such as strategic planning, process control, record keeping, human resource coordination, or analytical decision support.

== Strategic Context == Modern enterprise tools have undergone radical transformation due to rapid technological advancements, creating a challenge in selecting optimal solutions for diverse corporate needs. This complexity is driven by continuous pressure to reduce expenditures, maximize revenue streams, deeply understand client requirements, and flawlessly deliver conforming products. Consequently, leadership must adopt a high-level, strategic approach to technology acquisition, prioritizing tools that integrate with organizational requirements over merely adopting the newest trending software.

== Prominent Enterprise Tools (2013 Survey Context) == Data from a 2013 Bain & Company analysis highlighted frequently employed management instruments globally, reflecting regional operational imperatives:

• Strategic Roadmap Development
• Client Relationship Management (CRM)
• Personnel Satisfaction Measurement
• Competitive Analysis (Benchmarking)
• Performance Measurement Frameworks (Balanced Scorecard)
• Core Competency Identification
• Business Function Outsourcing
• Organizational Transformation Programs
• Logistics Network Orchestration
• Defining Corporate Purpose (Mission/Vision)
• Market Categorization
• Comprehensive Quality Assurance (TQM)

== Software Application Evolution == Business software, or operational applications, are collections of programs designed to execute specific enterprise tasks, aiming to elevate productivity and ensure precise execution of functions. The progression moved from foundational Management Information Systems (MIS) to extensive Enterprise Resource Planning (ERP) suites, subsequently incorporating CRM capabilities, culminating in today's cloud-native business management platforms. While the connection between IT investment and organizational output is proven, value realization hinges critically upon effective implementation strategies and discerning tool selection.

== Focus on Small and Medium Enterprises (SMEs) == Tools tailored for SMEs are vital as they provide mechanisms to conserve limited resources...