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.3021 npm2MIT
- 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
- AlicenseAqualityDmaintenanceRead-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
The read toolset has several overlapping routes to the same underlying data (get_task, fetch, graphql all read Workday pages; get_my_profile, get_worker, get_worker_task all surface worker data), so an agent must reason about which to pick. The descriptions do a good job of drawing the lines (structured vs raw vs GraphQL-only; catalog vs single item), which keeps selection mostly unambiguous.
All tools share the workday_ prefix and snake_case, and most follow a get_/open_ verb_noun pattern. Minor deviations exist (workday_fetch has no noun object; workday_healthcheck is a single word), but the convention is broadly predictable.
Ten tools is well-scoped for a read-only Workday reader, spanning profile, apps, tasks, workers, org chart, raw fetch, GraphQL, and diagnostics without padding. Each tool maps to a distinct access surface or fallback tier.
For a deliberately read-only server, coverage is strong: typed readers for the common surfaces plus raw fetch and GraphQL as escape hatches for unmodelled pages, and a healthcheck for diagnosing failures. The absence of any write/action tools is a real gap versus Workday's full domain, but is clearly by design rather than an oversight.