CData Salesloft Server

What it is

A local, read-only bridge between an assistant and Salesloft. CData's JDBC driver exposes Salesloft as relational SQL models; this server wraps the driver so a model can discover the tables and query them, and you can ask in plain language instead of writing SQL. It runs over stdio, so the client has to be on the same machine.

What you get

• get_tables lists the tables the driver exposes, returned as CSV with a header row
• get_columns lists the columns on one of those tables, in the same CSV shape
• run_query executes a SQL SELECT against live Salesloft data
• Tool names carry the prefix you set in the property file — the sample config uses Prefix=salesloft
• A Tables setting 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

Java and Maven: mvn clean install builds CDataMCP-jar-with-dependencies.jar. Separately install the CData JDBC Driver for Salesloft and license it by running java -jar cdata.jdbc.salesloft.jar --license, entering TRIAL or a license key. Build the connection string with the same jar, authenticating in the browser if the source uses OAuth, then write a .prp file naming the driver path, the driver class cdata.jdbc.salesloft.SalesloftDriver and that JDBC URL. Point your client at java -jar with the built jar and the .prp file.

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. Tool names take the Prefix value from your .prp file, so with Prefix=salesloft they are salesloft_get_tables, salesloft_get_columns and salesloft_run_query. All three only read; write access is CData's separate paid MCP Server.

Where it runs

Both documented setups run the server on your machine.