googleanalytics_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 Google Analytics. The driver exposes Google Analytics 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 Google Analytics, returned as CSV with a header row —
googleanalytics_get_tables - The columns of one of those tables, also as CSV, so a query can be composed against real field names —
googleanalytics_get_columns - A SQL SELECT executed against live Google Analytics data —
googleanalytics_run_query - Tool names that carry the prefix you set in the connection profile — the sample uses
Prefix=googleanalytics— 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 Google Analytics is a separate download and needs licensing: run java -jar cdata.jdbc.googleanalytics.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 CDataGoogleAnalytics), ServerVersion, DriverPath, DriverClass (cdata.jdbc.googleanalytics.GoogleAnalyticsDriver), 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 <YOUR_PRP_FILE>.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 — clone the repository, then point your client at the binary
USE CASES
01
Asking traffic questions without opening the reporting UI
Sessions, sources and page metrics come back as tables, so the question can be asked in a sentence and answered with a SELECT.
02
Pulling a metric into a longer piece of work
Read a figure mid-conversation and use it in the document or analysis you were already writing.
03
Finding out which dimensions are queryable
List the tables the driver exposes and read their columns to see which dimensions and metrics are reachable.
04
Authorising once, querying repeatedly
Google Analytics uses OAuth, so the browser approval happens while building the connection string and later queries reuse it.
3 tools
Listed in project docs. Your client may show a different list.
googleanalytics_get_columnsgoogleanalytics_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 in your .prp file. The README's sample uses Prefix=googleanalytics, giving googleanalytics_get_tables. All three only read (run_query executes SELECT), even though the README's usage section says the tools can write, update and delete.
Where it runs
Both documented setups run the server on your machine.
INSTALLATION
Connect your client
Clone the repository, then point your client at the binary. This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/cdatasoftware/google-analytics-mcp-server-by-cdata.git
cd google-analytics-mcp-server-by-cdata
mvn clean installDownload and install the CData JDBC Driver for Google Analytics from https://www.cdata.com/drivers/ganalytics/download/jdbc
License the driver: java -jar cdata.jdbc.googleanalytics.jar --license (enter name, email, and "TRIAL" or a license key)
Run java -jar cdata.jdbc.googleanalytics.jar with no arguments to open the Connection String utility, test the connection, copy the connection string
Write a .prp file (e.g. google-analytics.prp) containing Prefix=googleanalytics, ServerName, ServerVersion, DriverPath, DriverClass=cdata.jdbc.googleanalytics.GoogleAnalyticsDriver, 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 — Windows, Linux, macOS
JSON
{
"mcpServers": {
"google-analytics": {
"command": "<YOUR_PATH_TO_JAVA>",
"args": [
"-jar",
"<YOUR_PATH_TO_CDATA_MCP_JAR_WITH>",
"<YOUR_PATH_TO_GOOGLE_ANALYTICS>"
]
}
}
}