Skip to content
KiweelyKiweelyKiweely

Are there open-source Workday MCP servers on GitHub, and can you use one?

Yes, about ten repos exist, none with more than 14 stars, and none says it was proven on a production tenant. The best known, CData’s, was archived on 17 November 2026. Several run as one shared account.

  • By Kiweely
  • 8 min read
On this page

The short answer: yes, open-source Workday MCP servers exist, but they are early. On 17 November 2026 we opened every repo we could find. The most-starred has 14 stars, none of the READMEs says it was proven on a production tenant, and that most-starred one, CData’s, was archived the same day. You can use one for a read-only trial on a sandbox, with eyes open. Running one against real employee data needs more checks than a README tells you to make.

Which open-source Workday MCP servers are on GitHub?

Counts, licences and dates below come from each repo’s GitHub page and README on 17 November 2026. “Last commit” is the newest commit on the default branch. We searched GitHub and the official MCP registry for “workday mcp”. Other hits were business-day calculators or unrelated tools, and a few repos had no usable README.

Repo What it does Signs in as Reads and writes Licence Stars Last commit Archived
RepoCDataSoftware/workday-mcp-server-by-cdata What it doesLocal Java server around CData’s JDBC driver, so an assistant can query Workday as SQL Signs in asOne Workday sign-in set in the driver’s connection string (OAuth) on the machine running it Reads and writesRead-only LicenceMIT Stars14 Last commit17 Nov 2026 ArchivedYes
Repochrischall/workday-mcp What it doesReads Workday through your own signed-in browser tab, using a browser extension and Workday’s internal web endpoints, not the official API Signs in asYour browser session Reads and writesMostly reads; four tools marked Write (update request, benefit enrollment, give feedback, request feedback), each behind a confirm token. Its README opens by calling the server read-only LicenceMIT Stars1 Last commit14 Nov 2026 ArchivedNo
RepoJustParent/workday-advanced-mcp What it does30 tools over Workday SOAP web services: staffing, organisations, roles, home addresses, payment elections, journals Signs in asIntegration system user and password by default; OAuth refresh token also supported Reads and writes15 reads, 14 writes, 1 preview; a read-only mode registers only the reads LicenceMIT Stars0 Last commit24 Oct 2026 ArchivedNo
Repokrishnagutta/workday-mcp-reference What it does“Clean-room” reference server with an OAuth broker, REST and SOAP client Signs in asEach user, through Workday OAuth; the server stores the Workday tokens Reads and writesReads and writes, including a time-off request and approving or denying inbox tasks LicenceMIT Stars0 Last commit12 Jun 2026 ArchivedNo
Repokkanakas/workday-mcp What it doesAzure Functions server for Copilot Studio, with Microsoft Entra sign-in and an on-behalf-of token exchange Signs in asEach user, through Entra Reads and writesReads: get worker, search workers LicenceNone stated Stars0 Last commit24 Sep 2026 ArchivedNo
RepoJamesAten/workday-mcp What it doesScaffold that exposes Workday’s WQL query API Signs in asOne OAuth refresh token for a service identity (the README says to use a scoped integration system user) Reads and writesReads (WQL) LicenceMIT Stars0 Last commit24 May 2026 ArchivedNo
RepoNoBanks/workday-mcp What it doesFive tools over the Staffing REST API: workers, managers, organisations Signs in asA bearer token you supply in an environment variable; no OAuth flow of its own Reads and writesRead-only LicenceMIT Stars0 Last commit30 May 2026 ArchivedNo
Reposhriram14999/workday-mcp-server What it doesSix tools for workers, organisations and job profiles, built for Flowise Signs in asOne browser sign-in at the server’s /auth page; the server keeps one set of tokens in a local JSON file Reads and writesReads LicenceNone stated Stars0 Last commit3 Apr 2026 ArchivedNo
Repoppoinha/LocalWorkdayMCP (DaySight MCP) What it doesDocumentation for a Windows extension for Claude Desktop; the source is not published Signs in asEach user, with their own Workday account; the README says the client secret and tokens stay on that PC Reads and writesRead-only (“no tools that change data”) LicenceProprietary (30-day trial per tenant) Stars1 Last commit30 Oct 2026 ArchivedNo
RepoWorkday/ai-conversation-bridge What it doesReference architecture connecting chat apps to Workday through an AI orchestrator Signs in asNot applicable: the demo MCP server returns mock data Reads and writesMock data only LicenceApache-2.0 Stars12 Last commit31 Aug 2026 ArchivedNo

One more repo, ganumallya-blip/Workday-MCP-GML (GitHub describes it as “Workday MCP tools for Employee Self service”), has no README to read, so we do not describe it.

A note on the table. DaySight is on GitHub but is not open source: the repo holds documentation, and its README describes the software as proprietary. The browser-session server is a different kind of tool from the rest; its README warns that it reads internal endpoints that Workday does not publish and tells readers to check their employer’s acceptable-use policy. JustParent’s docs say its schemas were checked against an implementation tenant’s published service definitions; that is a test tenant, not production.

Does any of them say it works on a production tenant?

None of the READMEs we read says so. Several say the opposite in plain words: JamesAten’s calls itself “a starter, not a finished product”, NoBanks’ says a write release will wait for “an opt-in tenant for validation”, and DaySight’s says “early testing”. The krishnagutta reference says it reproduces the architecture of a production server, which describes the design, not a tenant it ran against.

That is not a criticism of the authors; several say plainly what stage the project is at. It does mean that nobody has told you, on the record, that it has survived a Workday release, a security review or real load.

Is Workday’s own ai-conversation-bridge an MCP server?

No. We read the README and the repo on 17 November 2026. It calls itself “a reference architecture that connects enterprise messaging apps” to Workday, built mainly for markets where workers use apps such as LINE WORKS, DingTalk and Feishu. The pieces are a bridge service, a demo MCP server that “returns mock Workday data” and deprecated Flowise templates. The README says “for production, plan a full MCP integration”. It is a useful picture of the shape of a chat-to-Workday system. It is not a server you point at your tenant.

What should you check before running one against real data?

Whose access it uses. A server that signs in once as an integration system user, or with one refresh token, is one shared identity. Everyone who can reach the assistant gets that identity’s access, whatever their own Workday security says. JamesAten’s README puts it directly: any client that can call the tools can run any query the identity is allowed to run. JustParent’s and shriram14999’s servers work the same way. Per-user sign-in, as in the krishnagutta, kkanakas and DaySight designs, is the safer model, but then the server has to hold a Workday token for each person.

Which tools write. JustParent’s lists 14 write tools, including organisation changes that its README says bypass normal business-process approval, home address and payment elections. krishnagutta’s can request time off and approve or deny inbox tasks. A read-only flag helps only if it is on, and an assistant’s prompt is not an approval step. Turn writes off until you have decided where a human confirms each change.

Where the tokens live. Our read of the code: shriram14999’s server writes its tokens to a plain JSON file; krishnagutta’s keeps them in memory or Redis, keyed by an opaque id; JustParent’s keeps credentials in environment variables. Ask who can read that store, how long a token lives and how you would revoke it.

Whether it follows the MCP rules. The MCP specification of 25 November 2025 says an MCP server must accept only tokens issued for itself, and “MUST NOT pass through the token it received from the MCP client” to an upstream API. The upstream token is a separate one, issued by the upstream authorisation server. Several of these servers sidestep the question by running locally over stdio with one identity. If you need a remote server that many people use, this is the part you would have to build.

Where it can run. Claude and ChatGPT reach a remote server from the vendor’s cloud, so a stdio server on a laptop serves one person on one machine. What a production build involves is laid out in Kiweely’s build-versus-buy article, which also carries Kiweely’s own cost estimates; treat those as estimates, not measurements.

Also check the licence (two repos state none, and DaySight’s is proprietary with a trial), who maintains it, and what happens at the next Workday release. For that last one, the CData repo is the example: the most popular server is now archived.

What are the alternatives to running one yourself?

  • Workday’s own Agent-Ready Tools are Workday’s MCP route for outside agents. Workday’s 13 October 2026 release says they are generally available in Workday Extend AI. Its admin guide, updated 13 November 2026, says the feature is “for Extend Professionals only” and uses OAuth with a sign-in. It also needs Agent System of Record set-up. Workday’s rate card lists 10 Flex Credits per 100 base calls and 50 per 100 advanced calls for non-custom agents.
  • Managed vendors host the server for you. StackOne lists 162 Workday actions on its Workday page. Workato documents a Workday End User MCP server whose tools act as the user who connects, with the authorization code grant. Merge’s Agent Handler lists Workday with OAuth. Each has its own pricing, storage and approval model, so compare them on the same checks as above. Every option compared does that with dates.
  • Kiweely Bridge is coming next: Workday inside Claude, ChatGPT and Gemini, each person signed in as themselves, changes confirmed on a browser card, with nothing stored. It is not available yet. Register interest. Planned pricing is $499 a month per company up to 1,000 employees, $1,499 up to 5,000 and $3,999 up to 20,000, with Enterprise by quote.

Frequently asked questions

Is CData's Workday MCP server on GitHub still maintained?

No. CData's repository was archived on 17 November 2026. Its last commit adds a deprecation notice that points to CData Connect AI for enterprise MCP and the CData CLI for coding agents. It was read-only and needed a licensed CData JDBC driver.

Does Workday publish an open-source MCP server on GitHub?

Not one that connects to your tenant. Workday's Workday/ai-conversation-bridge repository is a reference architecture for chat apps such as LINE WORKS, DingTalk and Feishu. Its README says the demo MCP server returns mock Workday data and that production needs a full MCP integration.

What is the biggest risk of running an open-source Workday MCP server?

Whose access it uses. Several of these servers sign in once as an integration system user, so every person who uses the assistant gets that account's access. After that come write tools, where the tokens are stored, and whether the server follows the MCP rule against passing a token through to Workday.

Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.

We’ll email you once to confirm. Unsubscribe in one click from any issue.