workday-mcp
Related Servers
Alternatives to workday-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceRead-only MCP server for Canvas LMS that works without API tokens by using session cookies, enabling AI assistants to access courses, assignments, grades, announcements, and more.3012 npm1MIT
- AlicenseNot gradedqualityDmaintenanceA vendor-neutral reference implementation of a Workday MCP server that enables integration with Workday for employee data, compensation, benefits, time off, org info, inbox tasks, admin operations, and headcount management through natural language.MIT
- AlicenseAqualityBmaintenanceRead-only MCP server for Edenred Plus that enables checking benefit balances, transactions, and deals via local browser authentication.5MIT
- AlicenseAqualityBmaintenanceAn MCP server that lets AI assistants like Claude read LinkedIn data through your own logged-in browser session. Access profiles and companies, search for jobs, or get job details.19Apache 2.0
- AlicenseAqualityCmaintenanceAn MCP server that lets AI assistants like Claude read LinkedIn data through your own logged-in browser session. Access profiles and companies, search for jobs, or get job details.17Apache 2.0
- FlicenseNot gradedqualityBmaintenanceRead-only MCP server for Hubstaff Time Tracking and Tasks APIs, providing tasks, comments, hours, and project data. Supports OAuth 2.1 for ChatGPT integration.-
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose: healthcheck, app discovery, app opening, structured page fetching, worker catalog, worker item fetching, raw fetching, and GraphQL. The potential overlaps between get_task/fetch and get_worker/get_worker_task are explicitly resolved in the descriptions.
The set consistently uses the workday_ prefix and mostly follows verb_noun naming like workday_get_apps and workday_get_worker_task. Minor deviations like workday_healthcheck, workday_fetch, and workday_graphql break the pattern slightly but are still readable and predictable.
Ten tools is well-scoped for a read-only Workday integration. Each tool covers a distinct surface area without redundancy, and the count feels neither bloated nor thin.
The toolset covers app discovery, profile/worker data, org chart navigation, structured page access, raw endpoint access, and GraphQL for non-HTML surfaces. The read-only boundary is intentional, and the raw fetch plus GraphQL escape hatches prevent dead ends.