Senzii MCP Serverofficial
A
licenseNot graded
qualityB
maintenanceEnables interaction with the Senzii scheduling app, allowing users to manage schedules, sessions, and related data through natural language.
Apache 2.0
mcp-sling
by poncheck
Related Servers
Alternatives to mcp-sling
No user-submitted related servers found.
Related Servers
- FlicenseCqualityDmaintenanceEnables natural language interaction with UKG Pro Workforce Management APIs. It detects intent, resolves missing inputs, hydrates related objects, and returns complete, validated operational answers across scheduling, timekeeping, attendance, and more.1-
- AlicenseBqualityDmaintenanceEnables interaction with the Officient HR API to manage people, days off, and salary slips through natural language.9MIT
- AlicenseNot gradedqualityDmaintenanceIntegrates Tanda Workforce API with AI assistants to manage employee schedules, timesheets, leave requests, clock in/out operations, and workforce analytics through natural language with OAuth2 authentication.2MIT
- FlicenseNot gradedqualityDmaintenanceProvides 50+ tools for interacting with Rippling's HR platform, including employee management, payroll, time tracking, benefits, recruiting, learning, devices, groups, and custom objects, all through natural language.-
- FlicenseNot gradedqualityDmaintenanceEnables interaction with the Harvest time tracking API for managing time entries, projects, and tasks through natural language.5-
TDQS
B3.2/5.0
Scored across 16 tools
Disambiguation4/5
Most tools have distinct purposes (e.g., create_shift, get_timesheets, update_user), but two organization retrieval tools (get_organization, get_organization_by_id) overlap slightly, and the generic sling_api_call could be confused with specific tools. Overall, the set is well-disambiguated.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_shift, get_users, update_timesheet). The only exception is sling_api_call, which still uses a noun_noun structure but is clearly named. The pattern is uniform and predictable.
Tool Count4/5
With 16 tools, the count is slightly above the ideal 3-15 range but still appropriate for the domain. Each tool covers a distinct function (users, shifts, timesheets, settings, etc.), and no tool feels redundant.
Completeness4/5
The tool set covers core CRUD operations for users, shifts, timesheets, organizations, and settings, plus reporting and a generic API call. Missing delete operations and shift updates are minor gaps, but the generic API call mitigates them. Coverage is good for common workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues