A
licenseB
qualityF
maintenanceEnables natural language interaction with Unanet GovCon ERP for project management, time tracking, financial reporting, and contact management, turning complex navigation into simple questions.
15
3
MIT
ukg_pro_wfm_mcp_server
by fvmuzik00
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ukg_pro_wfm_mcp_serverShow me the full schedule for the customer support team next week."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
What This Is
This is not a thin OpenAPI wrapper.
This server is designed to behave like a UKG Pro WFM reasoning layer. It accepts natural language, determines what the user is really asking, resolves missing inputs, discovers the correct API path, hydrates partial objects, traverses references, validates completeness, scores confidence, and returns full operational answers.
Related MCP server: Dialpad Universal MCP Server
Core Rule
Search and list endpoints are discovery only. They are not final truth.
If an API response contains IDs, references, partial objects, child references, parent references, profile references, or linked configuration, the server must hydrate those objects before answering.
Execution Model
Capabilities
Capability | Purpose |
Natural language routing | Understands operational questions without requiring endpoint knowledge |
Missing input resolution | Finds IDs, refs, dates, employees, groups, profiles, and related objects |
Discovery-only enforcement | Prevents list/search responses from being treated as final truth |
Universal hydration | Pulls full detail for every reachable partial object |
Object graph traversal | Follows parent, child, profile, group, org, and setup references |
Completeness validation | Calculates whether the answer is complete enough to return |
Confidence scoring | Classifies answers as CERTAIN, HIGH, MEDIUM, LOW, or BLOCKED |
Write safety | Requires hydration, dry-run, explicit confirmation, and re-read after writes |
Audit logging | Records source chain, duration, confidence, and affected objects |
Supported Domains
Domain | Coverage Intent |
Attendance | Events, patterns, and attendance-related operational context |
Common Resources | Shared objects, lookup values, Hyperfinds, and common references |
Employee Self Service | Employee-facing objects and request flows |
Forecasting | Forecast-related workforce planning data |
Healthcare Productivity | Productivity and staffing context |
HCM | HCM-connected workforce data |
Leave | Leave cases, requests, balances, and related context |
People | Person, employee, manager, job, and org details |
Person Assignments | Assignments, roles, and workforce relationships |
Platform | Tenant, metadata, and platform-level capabilities |
Scheduling | Schedules, shifts, coverage, and schedule analysis |
Scheduling Setup | Scheduling configuration and setup references |
Timekeeping | Timekeeping objects and operational time data |
Timekeeping Setup | Pay rules, work rules, pay codes, and setup metadata |
Timekeeping Timecards | Timecards, punches, exceptions, totals, approvals |
Timekeeping Bulk Operations | Controlled bulk workflows with guardrails |
Universal Device Manager | Device and clock-related operational context |
Webhook Events | Event subscriptions and event payload normalization |
Hydration Behavior
Traditional API result:
Server behavior:
This applies to every object type, not just Known Places.
Confidence Levels
Level | Meaning |
CERTAIN | Unique immutable identifier, full hydration, no unresolved dependencies, no conflicts |
HIGH | Strong candidate, full target detail, minor non-critical references unavailable |
MEDIUM | Likely answer, but some relevant references remain unresolved |
LOW | Ambiguous or incomplete |
BLOCKED | Cannot proceed safely because required data, access, or endpoint is unavailable |
Architecture
Execution Pipeline
Primary Tool
ukg_wfm_ask
Use this for natural language requests.
Examples:
Write Safety
Every write operation follows the same lifecycle:
Write, delete, and bulk operations cannot execute from:
name-only matches
search results
partial objects
inferred identities
ambiguous references
Only fully hydrated targets are eligible for mutation.
Installation
Clone the repository:
Install dependencies:
Configure environment:
Required environment variables:
Start development server:
Build production:
Run tests:
Scorecard
Generate endpoint intelligence and risk outputs:
Outputs:
docs/endpoint-scorecard.json
docs/tool-risk-matrix.json
Project Goals
This project exists to eliminate three common problems in workforce management integrations:
Partial answers
Manual endpoint selection
Missing relationship awareness
The server's responsibility is not merely to call APIs.
Its responsibility is to understand the request, discover what information is missing, retrieve that information, validate it, and return the most complete answer possible from the available system of record.
Available Tools
1 toolukg_wfm_askD
Universal natural language entry point with full hydration
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| inputs | No | Optional structured inputs such as employeeId, personId, dateRange, knownPlaceId, or groupId. | |
| question | Yes | Natural language UKG Pro WFM question or request. |
TDQS
D1.9/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure, but it discloses nothing about side effects, permissions, rate limits, or response behavior. It only mentions 'hydration' without explanation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short but under-specified, not concise. It omits essential information and does not earn its place by adding value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is inadequate for a tool with no output schema, no annotations, and no sibling context. It fails to explain the tool's purpose, usage scenarios, or expected behavior, leaving the agent with only the schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema provides 100% coverage for both parameters (question and inputs) with descriptions, so the baseline is 3. The description adds no extra meaning to the parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Universal natural language entry point with full hydration' is vague—it does not specify a concrete action or resource, and 'full hydration' is ambiguous jargon. It fails to clearly state what the tool does beyond being an entry point.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool or any alternatives. The description offers no context for appropriate usage scenarios or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v1.0.0- First observed
ukg_wfm_ask
TDQS
C2.6/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of confusion between tools. The single tool is uniquely identifiable.
Naming Consistency5/5
The single tool name follows a clear pattern: 'ukg_wfm' prefix plus an action verb 'ask'. Since there is only one name, consistency is trivially maintained.
Tool Count3/5
A single tool for a broad domain like workforce management feels thin, even if it is designed as a universal entry point. It is borderline: lightweight but potentially intentional for a natural-language interface.
Completeness4/5
The tool is described as a 'universal natural language entry point with full hydration', suggesting it can handle a wide range of WFM requests. However, without explicit confirmation of specific operations, there is a minor uncertainty about coverage.
Maintenance
ActivityStale
ResponsivenessNo issues
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Manage projects, tasks, time tracking, and team collaboration through natural language.
An AI concierge that turns static forms into adaptive AI conversations. From any MCP client.
Field workforce scheduling for AI agents. GPS punches, forms, timesheets. No dashboard.
Ask questions in plain language, get answers from your business database. No SQL required.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Dialpad's tools and services through a unified API, allowing users to manage communications via natural language.MIT
- FlicenseBqualityCmaintenanceEnables interaction with the Sling scheduling and workforce management platform, allowing users to manage shifts, users, calendars, and reports through natural language.162-
- FlicenseNot gradedqualityBmaintenanceEnables querying HR data like recent hires, employee details, departments, and PTO balances through natural language in an MCP client.-