outreach_get_tablesLABSCO SUMMARY
Read-only by construction.
Three tools and no write path is the whole design: the model discovers tables, reads columns and runs SELECTs, so a badly framed question produces a wrong answer rather than a changed record. Two things decide whether it fits. The CData JDBC driver is a separate licensed product, with a trial key to start on. And the assistant can query every table the connection can see — the Tables field in the connection profile does not narrow that, so limit the connection or the account it signs in with.
What it is
A read-only MCP server built on CData's JDBC Driver for Outreach.io. The driver exposes Outreach.io as relational tables; the server puts three tools over it, so a client can discover what tables exist, read a table's columns, and run a SELECT — without anyone writing SQL by hand.
What you get
- The tables the driver exposes for Outreach.io, returned as CSV with a header row —
outreach_get_tables - The columns of one of those tables, also as CSV, so a query can be composed against real field names —
outreach_get_columns - A SQL SELECT executed against live Outreach.io data —
outreach_run_query - Tool names that carry the prefix you set in the connection profile — the sample uses
Prefix=outreach— so several CData servers can run side by side without colliding - A
Tablessetting 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 to build — mvn clean install produces CDataMCP-jar-with-dependencies.jar. The CData JDBC Driver for Outreach.io is a separate download and needs licensing: run java -jar cdata.jdbc.outreach.jar --license and enter a name, an email and either TRIAL or a licence key. Connection settings go in a .prp file carrying Prefix, ServerName (the sample uses CDataOutreach), ServerVersion, DriverPath, DriverClass (cdata.jdbc.outreach.OutreachDriver), the JdbcUrl produced by the driver's connection-string utility, and the optional Tables list. The client then launches java -jar CDataMCP-jar-with-dependencies.jar outreach.io.prp. Transport is stdio, so the server has to run on the same machine as the client. If the data source authenticates over OAuth, you approve it in a browser while building the connection string.
Setup effort
Build from source — git clone https://github.com/cdatasoftware/outreach.io-mcp-server-by-cdata.git
USE CASES
01
Asking how a sequence performed
Prospects, sequences, mailings and accounts arrive as tables, so engagement questions become a SELECT the client composes.
02
Comparing rep activity without an export
Query activity across users in one statement instead of downloading per-rep reports.
03
Discovering which Outreach objects are queryable
List the tables the driver models, then read one table's columns to see the fields available.
04
Keeping prospect records scoped
Restrict the profile's table list so only the objects you want reported on are reachable.
3 tools
Listed in project docs. Your client may show a different list.
outreach_get_columnsoutreach_run_queryBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation. Tool names start with the Prefix set in the .prp file; with the sample Prefix=outreach they are outreach_get_tables, outreach_get_columns and outreach_run_query. All three only read — run_query executes SELECT. 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.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/cdatasoftware/outreach.io-mcp-server-by-cdata.git
cd outreach.io-mcp-server-by-cdata
mvn clean installDownload and install the CData JDBC Driver for Outreach.io from https://www.cdata.com/drivers/outreach/download/jdbc
License the driver: from the driver install's lib folder run java -jar cdata.jdbc.outreach.jar --license, then enter your name, email, and "TRIAL" (or your license key)
Build the connection string: run java -jar cdata.jdbc.outreach.jar to open the Connection String utility, click "Test Connection" (browser OAuth if the source needs it), and copy the connection string
Create outreach.io.prp with:
FILE · outreach.io.prp
Prefix=outreach
ServerName=CDataOutreach
ServerVersion=1.0
DriverPath=<YOUR_DRIVER_PATH>
DriverClass=cdata.jdbc.outreach.OutreachDriver
JdbcUrl=<YOUR_JDBC_URL>
Tables=Tables only picks which tables also get a ready-made description for your assistant, and empty means none; the server can still list and query every table your connection string reaches, so to keep data out of reach, limit that connection or the account it signs in with.
Add the mcpServers entry (block below) to claude_desktop_config.json, then fully quit and re-open the client
MCP Clients
Claude Desktop — macOS, Linux
CLAUDE DESKTOP — MACOS, LINUX · JSON
{
"mcpServers": {
"outreach-io": {
"command": "<YOUR_PATH_TO_JAVA>",
"args": [
"-jar",
"<YOUR_PATH_TO_CDATA_MCP_JAR_WITH>",
"<YOUR_PATH_TO_OUTREACH_IO>"
]
}
}
}