CData PingOne

What it is

A Java MCP server that puts CData's JDBC Driver for PingOne 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 PingOne 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
• Plain-language questions about your PingOne data go straight to the client — it picks the tools and writes the SQL

Requirements

Build the server with mvn clean install, which produces CDataMCP-jar-with-dependencies.jar. Separately download the CData JDBC Driver for PingOne and license it: run java -jar cdata.jdbc.pingone.jar --license and enter your name, email and either TRIAL or a licence key. Then write a .prp file naming DriverClass=cdata.jdbc.pingone.PingOneDriver 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 — clone the repository, then point your client at the binary

Tools you get

3 tools named in the project's documentation. All three are read-only, so the server can audit PingOne but cannot create, disable or modify users; writes need CData's separate MCP Server for PingOne. Names start with the Prefix set in the .prp file (pingone_run_query with the sample Prefix=pingone).

Where it runs

The documented client runs the server on your machine.