CData WooCommerce

What it is

A Java MCP server that puts CData's JDBC Driver for WooCommerce behind three read-only tools: list the tables, list a table's columns, and run a SQL SELECT. The driver is what does the work — it exposes WooCommerce as relational SQL models — and the server hands those models to your client so you can ask questions in plain language instead of writing SQL yourself.

What you get

• get_tables returns the tables available in the data source, as CSV with a header row
• get_columns returns the columns of one table, in the same CSV shape
• run_query executes a SQL SELECT and returns the rows
• Every tool name starts with the Prefix value from your .prp file, so several CData servers can run side by side without colliding
• You ask in plain language and the client picks the tools and writes the SQL itself

Requirements

Build the server with mvn clean install, which produces CDataMCP-jar-with-dependencies.jar. Separately download the CData JDBC Driver for WooCommerce and license it: run java -jar cdata.jdbc.woocommerce.jar --license and enter your name, email and either TRIAL or a licence key. Then write a .prp file naming DriverClass=cdata.jdbc.woocommerce.WooCommerceDriver plus the JdbcUrl you build in the driver's connection-string utility, and point your client at java -jar with the jar and that file. Transport is stdio, so the server has to run on the same machine as the client.

Setup effort

Build from source — git clone https://github.com/cdatasoftware/woocommerce-mcp-server-by-cdata.git

Tools you get

3 tools named in the project's documentation. All three are read-only (woocommerce_run_query runs SQL SELECT only); writes need CData's separate paid server. Names start with the Prefix set in the .prp file, woocommerce_ with the sample Prefix=woocommerce. The Tables setting does not limit what the tools reach; your connection's access does.

Where it runs

The documented client runs the server on your machine.