Skip to main content
Glama
rajuprasad-dev

Keka employee MCP

by rajuprasad-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Keka employee MCP

No user-submitted related servers found.

    Related Servers

    • keka-mcp

      technogise
      F
      license
      A
      quality
      C
      maintenance
      Enables read-only access to Keka HR timesheet and HRIS data, including employees, projects, clients, leaves, and holidays, through natural-language MCP clients.
      7
      -

    • workday-mcp

      chrischall
      A
      license
      A
      quality
      A
      maintenance
      Read-only MCP server for Workday that fetches your tasks and data cards (pay, benefits, compensation) via your existing browser session, returning structured JSON.
      10
      805 npm
      1
      MIT

    • jisr-mcp

      Gamaleldientarek
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP clients to securely access Jisr's documented HR Open API read-only operations, including employees, attendance, leave, payroll, finance, and discovery tools, with role-based field policies and dual protocol support.
      11
      MIT

    • Workday MCP Server

      pranjalkumar-evonence
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only access to Workday HCM data such as workers, organizations, locations, job profiles, and cost centers through MCP tools an LLM can call.
      -

    • benepass-mcp

      brian7989
      A
      license
      A
      quality
      B
      maintenance
      Enables read-only access to Benepass employee-web API, allowing users to view HSA accounts, investments, transactions, documents, and benefits without write operations.
      13
      7 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.7/5.0

    Scored across 43 tools

    Disambiguation3/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources