googlesearch_get_tablesLABSCO SUMMARY
SQL semantics without writing SQL, and nothing leaves the machine.
The driver does the hard part — turning the source into tables an assistant can reason about — so the three tools reduce to discover, describe, query. Two constraints shape where it fits: stdio means the server has to run on the same machine as the client, and this build reads only. The vendor points at their managed platform and paid driver when you need remote access or writes.
What it is
A Java MCP server wrapping the CData JDBC Driver for Google Search. The driver models the source as relational tables; the server lets an assistant list them, inspect their columns, and run SELECT queries. It communicates over stdio, so client and server sit on the same machine.
What you get
- The tables the data source exposes, returned as CSV with a header row —
googlesearch_get_tables - The columns of a table, also as CSV —
googlesearch_get_columns - A SQL SELECT executed against the source —
googlesearch_run_query - 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, Maven, and the CData JDBC Driver for Google Search, which must be licensed — run java -jar cdata.jdbc.googlesearch.jar --license and enter TRIAL or your key. Build the server with mvn clean install to produce CDataMCP-jar-with-dependencies.jar, then write a .prp file naming Prefix, ServerName, ServerVersion, DriverPath, DriverClass and the JdbcUrl from the driver's connection-string utility. The client runs java -jar against that JAR with the .prp path as its argument. This build is read-only.
Setup effort
Build from source — git clone https://github.com/cdatasoftware/google-search-mcp-server-by-cdata.git
USE CASES
01
Seeing what the source actually exposes
List the tables and read their columns before asking a question that assumes a field exists.
02
Answering a question with a SELECT
Let the assistant write and run the query, and read the CSV that comes back.
3 tools
Listed in project docs. Your client may show a different list.
googlesearch_get_columnsgooglesearch_run_queryBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation. The tool names carry a prefix from your config, most likely googlesearch, as in googlesearch_get_tables. All three only read, despite a sentence promising write access. 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/google-search-mcp-server-by-cdata.git
cd google-search-mcp-server-by-cdata
mvn clean installDownload and install the CData JDBC Driver for Google Search from https://www.cdata.com/drivers/googlesearch/download/jdbc
License the driver: java -jar cdata.jdbc.googlesearch.jar --license (enter name, email, and "TRIAL" or a license key)
Run java -jar cdata.jdbc.googlesearch.jar with no arguments to open the Connection String utility, test the connection, copy the connection string
Write a .prp file (e.g. google-search.prp) containing Prefix=googlesearch, ServerName, ServerVersion, DriverPath, DriverClass=cdata.jdbc.googlesearch.GoogleSearchDriver, JdbcUrl, 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 below to claude_desktop_config.json, pointing java at CDataMCP-jar-with-dependencies.jar and at the .prp file, then fully quit and reopen the client
MCP Clients
Claude Desktop — macOS / Linux
CLAUDE DESKTOP — MACOS / LINUX · JSON
{
"mcpServers": {
"google-search": {
"command": "<YOUR_PATH_TO_JAVA>",
"args": [
"-jar",
"<YOUR_PATH_TO_CDATA_MCP_JAR_WITH>",
"<YOUR_PATH_TO_GOOGLE_SEARCH>"
]
}
}
}