Skip to main content
Glama
UKG Ready MCP

UKG Ready MCP

UKG Ready MCP

MCP server for UKG Ready REST endpoints, including employees, timecards, exceptions, compensation, saved reports, and a generic authenticated endpoint tool.

Configuration

Copy .env.example to a local environment configuration and set:

  • UKG_BASE_URL: UKG tenant base URL, defaulting to https://secure.entertimeonline.com.

  • UKG_API_KEY, UKG_USERNAME, UKG_PASSWORD, UKG_COMPANY.

  • UKG_DEFAULT_REPORT_ID: optional saved report ID.

Never commit real credentials or place them in source files.

Related MCP server: woffu-mcp

Run

npm install
npm run build
npm start

The server communicates over MCP stdio. Available tools:

  • get_ukg_saved_report_csv

  • list_ukg_employees

  • get_ukg_employee

  • get_ukg_timecards

  • list_ukg_exceptions

  • get_ukg_compensation

  • call_ukg_endpoint

The workforce tools use documented-style defaults and expose an optional path override because UKG Ready endpoint availability varies by tenant and enabled module. The generic tool accepts any API path, so credentials remain inside the server configuration. Add write tools only after the tenant's endpoint contract and permissions are confirmed.

UKG employee and Command Cloud driver mapping

The intended integration is that a UKG employee corresponds to a driver in Command Cloud. This mapping is a planned cross-system relationship, not an automatic assumption yet.

When implementing it, reconcile records using stable identifiers where available, then validate with supporting fields such as employee/driver name, employee number, phone, email, and active status. Keep an explicit mapping of the UKG employee ID to the Command Cloud driver ID; do not rely on names alone because names can change or be duplicated.

The mapping will support future workflows such as comparing UKG timecards or clock status with Command Cloud driver, dispatch, and ticket activity. The actual matching rules and source-of-truth decisions still need to be confirmed before writing synchronization tools.

Available Tools

7 tools
call_ukg_endpointB

Call a UKG Ready REST endpoint with the configured credentials. Use this to explore tenant-enabled endpoints.

Inputs: path (required), body, query, accept, +1 more.

get_ukg_compensationA

Retrieve compensation data for an employee or the tenant's compensation collection.

Inputs: path, query, employeeId.

get_ukg_employeeA

Get one UKG Ready employee by ID.

Inputs: employeeId (required), path, query.

get_ukg_saved_report_csvA

Download a UKG Ready saved report as CSV. The report must be shared with the configured API user.

Inputs: reportId.

get_ukg_timecardsB

Retrieve timecards for an employee, optionally constrained by a date range.

Inputs: employeeId (required), path, query, endDate, +1 more.

list_ukg_employeesA

List employees visible to the configured UKG Ready API user.

Inputs: path, query.

list_ukg_exceptionsA

List timekeeping exceptions visible to the configured UKG Ready API user.

Inputs: path, query, endDate, startDate, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a distinct purpose: report download, generic endpoint call, employee listing/retrieval, timecards, exceptions, and compensation. There is no ambiguity between them, and the generic call_ukg_endpoint does not overlap with specific operations because it is meant for exploration.

    Naming Consistency5/5

    All tools follow a consistent pattern: <verb>_ukg_<noun>, with verbs like get_ for single resources, list_ for collections, and call_ for the generic endpoint. The naming is uniform and predictable.

    Tool Count5/5

    Seven tools is well within the typical range for a focused HCM integration. Each tool serves a clear purpose, and the count feels neither sparse nor overwhelming.

    Completeness4/5

    The toolset covers core read operations for employees, time, compensation, and reports, but lacks write capabilities (create/update/delete) and other HCM modules. The generic call_ukg_endpoint partly offsets this by enabling direct API access, so the gaps are minor and workaroundable.

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Insperity's REST API to access employee data, including employee lists, check details, and profile information for HR management tasks.
      -
    • A
      license
      B
      quality
      D
      maintenance
      Exposes the Wealthbox CRM API to MCP-enabled clients, enabling operations on contacts, tasks, events, notes, opportunities, projects, workflows, and more.
      51
      32 npm
      4
      MIT