sap-successfactors -by-cdata
This read-only MCP Server allows you to connect to SAP SuccessFactors data from Claude Desktop through CData JDBC Drivers. For full CRUD support, check out the first managed MCP platform: CData Connect AI (https://www.cdata.com/ai/).
claude mcp add --transport stdio cdatasoftware-sap-successfactors-mcp-server-by-cdata java -jar /PATH/TO/CDataMCP-jar-with-dependencies.jar /PATH/TO/sap-successfactors.prp
How to use
This MCP server provides a read-only interface to SAP SuccessFactors data via the CData JDBC Driver. It exposes a set of tools that let an AI client discover what tables exist, inspect their columns, and run read-only queries against the data source. The available tools follow a naming pattern based on the server name: sap_successfactors_get_tables to list tables, sap_successfactors_get_columns to list columns for a table, and sap_successfactors_run_query to execute a SELECT query. Tools return results in CSV for table/column outputs and can be invoked through JSON-RPC payloads or a compatible MCP client.
To use it, configure Claude Desktop (or another MCP client) with the server entry that points to the local Java MCP JAR and the generated sap-successfactors.prp file. Once running, you can ask natural language questions and the AI will leverage these tools to query the underlying SAP SuccessFactors data. For example, you could ask about counts, join-like insights across tables, or specific records, and the client will translate that into appropriate tool calls such as get_tables, get_columns, and run_query. Since this server is read-only by design, write/update/delete operations are not exposed here.
How to install
Prerequisites:
- Java Runtime Environment (JRE) or JDK installed on your machine
- Maven (for building the project)
- Access to the SAP SuccessFactors data via the CData JDBC Driver (driver installed/licensed)
Installation steps:
- Clone the repository and build the MCP server
git clone https://github.com/cdatasoftware/sap-successfactors-mcp-server-by-cdata.git
cd sap-successfactors-mcp-server-by-cdata
mvn clean install
This creates the JAR file: CDataMCP-jar-with-dependencies.jar located in the build output.
- Install the CData JDBC Driver for SAP SuccessFactors
- Download from: https://www.cdata.com/drivers/sapsuccessfactors/download/jdbc
- Install according to the provider's instructions
- License the driver as required (see installation notes in the driver docs)
- Prepare the SAP SuccessFactors PRP file
- Create a sap-successfactors.prp with the required properties (Prefix, ServerName, ServerVersion, DriverPath, DriverClass, JdbcUrl, Tables).
- Example contents (adjust paths for your environment):
Prefix=sapsuccessfactors
ServerName=CDataSAPSuccessFactors
ServerVersion=1.0
DriverPath=PATH\\TO\\cdata.jdbc.sapsuccessfactors.jar
DriverClass=cdata.jdbc.sapsuccessfactors.SAPSuccessFactorsDriver
JdbcUrl=jdbc:sapsuccessfactors:InitiateOAuth=GETANDREFRESH;
Tables=
- Run the MCP server
- Start the server with the prepared PRP file:
java -jar /PATH/TO/CDataMCP-jar-with-dependencies.jar /PATH/TO/sap-successfactors.prp
- The server will listen on stdio; use a compatible MCP client on the same machine to communicate.
- Configure Claude Desktop (or another MCP client) to include the server entry (see the config examples in the README) and reload the client to see the SAP SuccessFactors MCP server.
Additional notes
Notes and tips:
- The MCP server runs via stdio, so the client must execute on the same machine.
- Ensure the CData JDBC Driver for SAP SuccessFactors is installed, licensed, and accessible via the DriverPath you configure in sap-successfactors.prp.
- If you don’t see the server in Claude Desktop after adding it, fully quit Claude Desktop and relaunch it so it reloads the MCP server list.
- The tools expose raw results (tables/columns) in CSV format; you can chain tool calls to explore data schema before issuing queries.
- For production use, keep the SAP SuccessFactors credentials and OAuth tokens secure in the driver configuration; avoid embedding sensitive data in PRP files where possible.