Two ways to give Claude a Workday tool

Claude Code can call tools exposed by an MCP server. For Workday, the server might wrap WQL, RaaS, REST APIs, or a custom integration. What Claude can do depends on the server's actual tools, the credential behind them, and that credential's Workday permissions. The words “Workday MCP” alone do not tell you its reach.

kiweely is a desktop Workday workspace that can run Claude Code with your own Claude subscription. It provides its own Workday connections, project context, tools, and approval flow to the conversation. You still sign in to Workday separately. The two setups can use the same Claude model, but they expose different routes to the tenant.

For a narrow data question

If you need a known read-only query, an MCP server exposing only the relevant Workday API may be enough. Ask its operator which endpoints it exposes, which tenant it targets, and which identity runs the query. A server that returns worker records does not necessarily provide a way to inspect tenant configuration or build an Extend app.

Workday documents WQL through its REST API and the setup of an Integration System User and API client. Those are useful foundations for an API-based MCP server. They do not, by themselves, define the tools a particular server has implemented.

For an Extend app or a browser task

Building an Extend app takes more than retrieving records. Workday separates building, testing, deployment, and release in its Extend lifecycle. An API-only MCP server can cover only the steps for which someone built and authorized tools. It is possible to build a broader server; check its tools rather than assuming it cannot do the job.

kiweely is designed to carry an Extend task across source, Workday validation, deployment, and browser testing, with the user's review at consequential steps. That makes it a better fit when the answer must include what happened in the tenant and on the screen, not merely a generated file. The Claude Extend walkthrough shows the sequence and the evidence to ask for.

Choose by the proof you need

For either route, start with the task and work backward. Identify the tenant, the acting identity, the available tools, and whether the result must be read back from Workday or checked in a browser. If the task is limited to an API your MCP server exposes, use that smaller connection. If it crosses into app building or tenant UI work, verify that your chosen setup can complete and prove those steps.

You can set up Claude in kiweely without replacing your other Claude Code workflows. Choose the route that has the access and review points the particular job requires.