adobeanalytics_get_tablesLABSCO SUMMARY
Analytics as tables, and you choose which ones.
Turning Adobe Analytics into SQL models is what makes a natural-language question answerable at all — the assistant discovers the tables and columns, then writes one SELECT. This build is the reading half of CData's stack by design; write access and the managed remote option are separate products. The assistant can query every table the connection can see — the Tables property in the connection file does not narrow that, so limit the connection or the account it signs in with.
What it is
A local, read-only MCP server from CData that wraps the CData JDBC Driver for Adobe Analytics. The driver presents Adobe Analytics as relational SQL models; the server exposes three tools over that connection, so an assistant can answer questions about live analytics data without anyone writing SQL by hand.
What you get
- The list of tables the driver exposes for your Adobe Analytics connection, returned as CSV with a header row —
adobeanalytics_get_tables - Column listings for any of those tables, also as CSV with headers —
adobeanalytics_get_columns - SQL SELECT execution against the live connection —
adobeanalytics_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
A licensed CData JDBC Driver for Adobe Analytics — run java -jar cdata.jdbc.adobeanalytics.jar --license and enter TRIAL or your key. Java and Maven, since the server is built with mvn clean install into CDataMCP-jar-with-dependencies.jar. A .prp file carrying Prefix, ServerName, ServerVersion, DriverPath, DriverClass and JdbcUrl, passed to the jar as its argument. Adobe Analytics authenticates over OAuth, so the first connection is completed in a browser. Transport is stdio, so the client must run on the same machine as the server.
Setup effort
Build from source — clone the repository, then point your client at the binary
USE CASES
01
Answering an analytics question without opening the console
Ask in plain language; the client lists the tables and columns it needs, then runs one SELECT against live data.
02
Finding out what the driver actually exposes
List the tables and read the columns of the promising ones, so queries are written against real field names.
3 tools
Listed in project docs. Your client may show a different list.
adobeanalytics_get_columnsadobeanalytics_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=adobeanalytics, giving adobeanalytics_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
Clone the repository: git clone https://github.com/cdatasoftware/adobe-analytics-mcp-server-by-cdata.git then cd adobe-analytics-mcp-server-by-cdata
Build the server: mvn clean install — this creates the JAR file CDataMCP-jar-with-dependencies.jar that the config block points at
Download and install the CData JDBC Driver for Adobe Analytics from https://www.cdata.com/drivers/adobeanalytics/download/jdbc/
License the driver: from the driver install's lib folder run java -jar cdata.jdbc.adobeanalytics.jar --license and enter your name, email, and "TRIAL" (or your license key)
Build the connection string: run java -jar cdata.jdbc.adobeanalytics.jar to open the Connection String utility, click "Test Connection", and copy the working connection string (browser OAuth may be required here)
Create a .prp file (e.g. adobe-analytics.prp) containing Prefix / ServerName / ServerVersion / DriverPath / DriverClass / JdbcUrl / Tables — set JdbcUrl to the connection string you copied in the previous step
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 to claude_desktop_config.json pointing at your java binary, the built JAR, and the .prp file; copy the file to %APPDATA%\Claude\ (Windows) or ~/Library/Application Support/Claude/ (Mac)
Fully quit and re-open Claude Desktop for the MCP server to appear
MCP Clients
Claude Desktop — Windows, Linux, macOS
JSON
{
"mcpServers": {
"adobe-analytics": {
"command": "<YOUR_PATH_TO_JAVA>",
"args": [
"-jar",
"<YOUR_PATH_TO_CDATA_MCP_JAR_WITH>",
"<YOUR_PATH_TO_ADOBE_ANALYTICS>"
]
}
}
}