saparibaprocurement_get_tablesLABSCO SUMMARY
Procurement data without writing the SQL yourself.
Ariba's data model is wide enough that finding the right table is half the job, which is precisely what the table-and-column discovery tools automate here. Everything stays read-only and local. The gate is the CData driver: it has to be installed and licensed on the same machine before the server can connect to anything.
What it is
A local MCP server around the CData JDBC Driver for SAP Ariba Procurement, which maps the procurement suite onto relational SQL models. The model gets table discovery, column discovery, and a read-only query tool. It speaks stdio, so the MCP client must run on the same machine.
What you get
- The SAP Ariba Procurement tables the driver exposes, as CSV with a header row —
saparibaprocurement_get_tables - The columns of a given table, so SQL is written against real field names —
saparibaprocurement_get_columns - A SQL
SELECTagainst live procurement data —saparibaprocurement_run_query - A
Tablessetting that only picks which tables also get a ready-made description (blank means none); it does not limit what the tools can list or query, so limit the connection or the account it signs in with
Requirements
An SAP Ariba Procurement account and a licensed CData JDBC Driver for SAP Ariba Procurement — trial licences work, applied with java -jar cdata.jdbc.saparibaprocurement.jar --license. Java to run, Maven to build (mvn clean install → CDataMCP-jar-with-dependencies.jar). The .prp connection file names DriverClass as cdata.jdbc.saparibaprocurement.SAPAribaProcurementDriver, the driver jar path, a tool Prefix such as saparibaprocurement, and the JDBC connection string built by the driver's Connection String utility; OAuth sources prompt a browser sign-in there. MIT licensed.
Setup effort
Build from source — clone the repository, then point your client at the binary
USE CASES
01
Answering a sourcing or spend question
Ask in plain language; the model locates the table, reads its columns, and runs a single SELECT against live Ariba data.
02
Getting oriented in the Ariba data model
Enumerate tables and columns to see what the driver exposes, instead of reading API docs to find the right object.
3 tools
Listed in project docs. Your client may show a different list.
saparibaprocurement_get_columnssaparibaprocurement_run_queryBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation. Tool names take the Prefix from your .prp file, so with the README's Prefix=saparibaprocurement they are saparibaprocurement_get_tables, saparibaprocurement_get_columns and saparibaprocurement_run_query.
Where it runs
Both documented setups run the server on your machine.
INSTALLATION
Connect your client
Clone the repository, then point your client at the binary. This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/cdatasoftware/sap-ariba-procurement-mcp-server-by-cdata.git
cd sap-ariba-procurement-mcp-server-by-cdata
mvn clean installDownload and install the CData JDBC Driver for SAP Ariba Procurement from https://www.cdata.com/drivers/saparibaprocurement/download/jdbc
License the driver: from the driver install's lib folder run java -jar cdata.jdbc.saparibaprocurement.jar --license, then enter your name, email, and "TRIAL" (or your license key)
Build the connection string: run java -jar cdata.jdbc.saparibaprocurement.jar to open the Connection String utility, click "Test Connection" (browser OAuth if the source needs it), and copy the connection string
Create sap-ariba-procurement.prp with:
FILE · sap-ariba-procurement.prp
Prefix=saparibaprocurement
ServerName=CDataSAPAribaProcurement
ServerVersion=1.0
DriverPath=<YOUR_DRIVER_PATH>
DriverClass=cdata.jdbc.saparibaprocurement.SAPAribaProcurementDriver
JdbcUrl=<YOUR_JDBC_URL>
Tables=Tables only picks which tables also get a ready-made description for your assistant, and empty means none; the server can still list and query every table your connection string reaches, so to keep data out of reach, limit that connection or the account it signs in with.
Add the mcpServers entry below to claude_desktop_config.json and fully restart the client
MCP Clients
Claude Desktop — Windows, macOS / Linux
JSON
{
"mcpServers": {
"sap-ariba-procurement": {
"command": "<YOUR_PATH_TO_JAVA>",
"args": [
"-jar",
"<YOUR_PATH_TO_CDATA_MCP_JAR_WITH>",
"<YOUR_PATH_TO_SAP_ARIBA_PROCUREMENT>"
]
}
}
}