Skip to main content
Glama
chrischall

workday-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to workday-mcp

No user-submitted related servers found.

    Related Servers

    • workday-mcp-reference

      krishnagutta
      A
      license
      Not graded
      quality
      D
      maintenance
      A 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

    • Edenred Plus MCP

      B-Mahdj
      A
      license
      A
      quality
      B
      maintenance
      Read-only MCP server for Edenred Plus that enables checking benefit balances, transactions, and deals via local browser authentication.
      5
      MIT

    • MCP Server for LinkedIn

      bartest5
      A
      license
      A
      quality
      C
      maintenance
      An 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.
      17
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target clearly distinct resources: apps, my-profile, worker, org-chart, worker-task. There is some overlap among workday_get_task, workday_fetch, and workday_graphql (all retrieve Workday pages/endpoints), but the descriptions establish a clear hierarchy (structured view vs raw JSON escape hatch vs GraphQL-only surfaces), which prevents most misselection.

    Naming Consistency4/5

    All tools share the workday_ prefix and mostly follow a verb_noun pattern (get_apps, get_worker, open_app, get_org_chart). Minor deviations exist: workday_healthcheck is noun-only, and workday_fetch/workday_graphql omit a noun, but the set reads consistently overall.

    Tool Count5/5

    Ten tools is well-scoped for a read-only Workday browser bridge, with no apparent redundancy and each tool earning its place (discovery, profile reads, page fetch, and two explicit escape hatches).

    Completeness4/5

    For an explicitly read-only server, the surface covers discovery (apps, org chart), profile/catalog reads, named task access, and raw JSON plus GraphQL escape hatches for unmodeled pages. The only gap is the deliberate absence of any write/mutation operations, which is by design rather than an oversight.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources