CData Workday MCP Service Endpoint

This repository furnishes an MCP (Model Context Protocol) server component crafted by CData specifically for Workday data access.

:warning: Note on Functionality: This implementation provides strictly read-only access. For comprehensive CRUD operations (Create, Read, Update, Delete) along with action execution capabilities, and for an expedited setup process, we advise exploring our complimentary CData MCP Server for Workday (Beta release).

Core Objective

The primary motivation behind this restricted-access MCP server is to empower LLMs, such as Claude Desktop, to dynamically interrogate live Workday datasets. This is achieved through the integration of the CData JDBC Driver for Workday.

The CData JDBC Driver functions by virtualizing Workday endpoints, rendering them accessible as standard relational SQL models.

This server component wraps the aforementioned driver, exposing Workday assets via a straightforward MCP interface. Consequently, AI agents can extract contemporary insights by formulating queries in plain English—eliminating the prerequisite of generating SQL statements.

Deployment Instructions

1. Repository Acquisition: bash git clone https://github.com/cdatasoftware/workday-mcp-server-by-cdata.git cd workday-mcp-server-by-cdata

2. Software Compilation: bash mvn clean install

   This step yields the executable artifact: CDataMCP-jar-with-dependencies.jar 3. Driver Acquisition: Secure the CData JDBC Driver tailored for Workday from: https://www.cdata.com/drivers/workday/download/jdbc and complete its installation. 4. Driver Licensing Procedure: * Navigate to the lib directory within the driver's installation location (e.g., Windows: C:\Program Files\CData\CData JDBC Driver for Workday\ or Linux/Mac: /Applications/CData JDBC Driver for Workday/). * Execute the licensing utility: java -jar cdata.jdbc.workday.jar --license * Provide your details (name, email) and input "TRIAL" or your valid license key. 5. Data Source Connectivity Configuration: * Initiate the Connection String utility by running: java -jar cdata.jdbc.workday.jar

   • Configure the necessary parameters for your Workday connection and validate it using "Test Connection".

     Authentication Alert: If OAuth is employed for data source access, an in-browser authentication step will be mandatory.

   • Upon successful validation, capture and retain the resulting JDBC connection URI.
   • Property File Generation (.prp): Define a configuration file (e.g., workday.prp) detailing the connection parameters:
   • Prefix: A namespace identifier for the exposed tools.
   • ServerName: The designated name for this service instance.
   • ServerVersion: The version identifier for the service.
   • DriverPath: Absolute path to the downloaded JDBC driver JAR file.
   • DriverClass: The fully qualified name of the JDBC Driver implementation class (e.g., cdata.jdbc.workday.WorkdayDriver).
   • JdbcUrl: The connection string obtained in step 5.
   • Tables: Specify desired tables; leave empty to expose all available structures. env Prefix=workday_service ServerName=LiveWorkdayDataGateway ServerVersion=1.1 DriverPath=ABSOLUTE/PATH/TO/cdata.jdbc.workday.jar DriverClass=cdata.jdbc.workday.WorkdayDriver JdbcUrl=jdbc:workday:InitiateOAuth=GETANDREFRESH;SomeOtherParam=Value; Tables=

Integrating with an AI Client (e.g., Claude Desktop)

1. Client Configuration File Creation: Construct or modify the client's configuration file (e.g., claude_desktop_config.json) to incorporate the new MCP endpoint definition within the mcpServers block.

   Windows Path Example:

   { "mcpServers": { "workday_service": { "command": "C:\PATH\TO\java.exe", "args": [ "-jar", "C:\PATH\TO\CDataMCP-jar-with-dependencies.jar", "C:\PATH\TO\workday.prp" ] }, ... } }

   Linux/Mac Path Example:

   { "mcpServers": { "workday_service": { "command": "/usr/bin/java", "args": [ "-jar", "/opt/mcp/CDataMCP-jar-with-dependencies.jar", "/etc/configs/workday.prp" ] }, ... } }

   Ensure this configuration file resides in the correct location for the client application (e.g., Windows: %APPDATA%\Claude\claude_desktop_config.json). 2. Client Restart: Completely terminate and subsequently relaunch the AI client application to ensure the newly defined MCP resources are loaded.

Troubleshooting Tip: If the server endpoints do not manifest after configuration, ensure the client application process is fully terminated (check Task Manager/Activity Monitor).

Standalone Server Execution

To launch the gateway independently (for testing or direct stdio communication): bash java -jar /PATH/TO/CDataMCP-jar-with-dependencies.jar /PATH/TO/workday.prp

I/O Mode: This server communicates exclusively via standard input/output (stdio), necessitating that the client application runs on the identical host machine.

Operational Use Case Summary

Once the service is successfully initialized and connected to the AI client, the model gains access to integrated functions for querying the underlying Workday structure. Explicit tool invocation is generally unnecessary; the LLM should be directed to pose questions about the data ecosystem. For example: * "What is the aggregate compensation budget for employees hired last quarter?" * "Summarize open requisitions categorized by department." * "Detail all planned employee time-off events for the upcoming holiday period."

The available toolset and their corresponding definitions follow:

Available Functions & Semantics

In the function signatures below, {gateway_prefix} substitutes the Prefix value defined in your .prp file (e.g., workday_service).

• {gateway_prefix}_get_tables: Fetches a comprehensive registry of accessible schemas within Workday. Complement this by invoking {gateway_prefix}_get_columns to detail specific table attributes. Output is delivered in CSV format, with the initial line serving as headers.
• {gateway_prefix}_get_columns: Retrieves the schema definition (field list) for a specified data structure. Refer to {gateway_prefix}_get_tables for the inventory of targets. Output is delivered in CSV format, with the initial line serving as headers.
• {gateway_prefix}_run_query: Permits the execution of arbitrary SQL SELECT commands against the Workday relational view.

JSON-RPC Invocation Examples

For scenarios requiring direct scripting of requests rather than relying on the AI interface, utilize the JSON-RPC 2.0 standard payloads demonstrated below when invoking the designated functions.

Invoking workday_service_get_tables

{ "jsonrpc": "2.0", "id": 101, "method": "tools/call", "params": { "name": "workday_service_get_tables", "arguments": {} } }

Invoking workday_service_get_columns

{ "jsonrpc": "2.0", "id": 102, "method": "tools/call", "params": { "name": "workday_service_get_columns", "arguments": { "table": "Worker_Assignments" } } }

Invoking workday_service_run_query

{ "jsonrpc": "2.0", "id": 103, "method": "tools/call", "params": { "name": "workday_service_run_query", "arguments": { "sql": "SELECT Worker_ID, Hire_Date FROM [Worker_Details] WHERE Hire_Date > '2023-01-01'" } } }

Common Resolution Paths

1. Visibility Issue: If the configured CData MCP service is not visible within the host AI client, confirm that the client application has been completely shut down (not just minimized).
2. Data Retrieval Failure: If the client cannot fetch data, meticulously re-verify the connection URI configuration, ensuring the string copied from the CData Connection Builder utility is accurately reflected in the .prp configuration file.
3. Connectivity Problems: For issues connecting directly to the Workday source, please engage the CData Support Portal.
4. Server Operation Feedback: For inquiries regarding MCP server functionality or to submit suggestions, join the CData User Forum.

Licensing

This MCP gateway software is distributed under the permissive MIT License. This grants broad rights to utilize, modify, and redistribute the code, contingent upon adherence to the MIT License terms. Full licensing details are available in the repository's LICENSE file.

Data Source Compatibility Index (Partial List)

This driver architecture supports numerous data repositories beyond Workday. A representative sample of connectivity targets includes:

Category	Included Connectors	Category	Included Connectors
Cloud & SaaS	Salesforce, ServiceNow, SAP, NetSuite, HubSpot	Databases	PostgreSQL, MySQL, SQL Server, Oracle, MongoDB
Analytics	BigQuery, Redshift, Snowflake, Tableau CRM	File Systems	S3, HDFS, Dropbox, SharePoint, JSON, CSV
ERP/HR	Dynamics 365, ADP, PeopleSoft	Marketing	Google Ads, Facebook Ads, MailChimp
...	...	...	...

Consult the CData documentation for the complete list of over 300 supported integrations, including connectors for Oracle HCM, SAP SuccessFactors, and Microsoft Azure services.