Once the driver is licensed and the connection string is in place, the assistant can answer questions about live TaxJar records without anyone touching a query editor. The setup, not the usage, is the work: you install a JDBC driver, license it through its own utility, test the connection string, and hand-write a properties file. Writes are out of scope here — CData sells a separate MCP server for read, write, update, delete and actions.
A Java MCP server that wraps the CData JDBC Driver for TaxJar and exposes TaxJar as relational SQL tables, so a client can retrieve live data from natural-language questions. This build is read-only: queries are SELECT 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 `taxjar_get_tables`, `taxjar_get_columns` and `taxjar_run_query`
- JSON-RPC payload examples for each tool, if you are 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 TaxJar (`java -jar cdata.jdbc.taxjar.jar --license` takes your name, email, and TRIAL or a licence key). Write a .prp file holding Prefix, ServerName, DriverPath, DriverClass and the JdbcUrl you copy out of the driver's connection-string utility. The server speaks stdio, so it only works with clients on the same machine.
Build from source — clone the repository and build it, then point your client at the binary