SAS xpt is an awkward format to explore interactively; the CData driver flattens it into SQL tables and this server puts those tables in front of a model. Budget your time for the driver install and licensing step rather than for the MCP wiring. Read, write, update and delete are not in this build — CData keeps those in the MCP server it sells.
A Java MCP server that wraps the CData JDBC Driver for SAS xpt, exposing the data as relational SQL models so a client can answer questions about it without anyone writing SQL. This build is read-only.
- A tool that lists the tables the driver exposes, returned as CSV with a header row
- A tool that lists the columns on any one of those tables
- A tool that runs a SQL SELECT and hands back the rows
- Tool names carry the prefix you set in the .prp file — with a prefix of source they read as `sasxpt_get_tables`, `sasxpt_get_columns` and `sasxpt_run_query`
- JSON-RPC payload examples for each tool, for scripting the calls instead of using a chat client
Build the jar with `mvn clean install`, then install and license the CData JDBC Driver for SAS xpt (`java -jar cdata.jdbc.sasxpt.jar --license`). Write a .prp file with DriverPath, DriverClass `cdata.jdbc.sasxpt.SASxptDriver` and the JdbcUrl copied from the connection-string utility. stdio only — the client has to run on the same machine as the server.
Build from source — clone the repository and build it, then point your client at the binary