CData LinkedIn Ads

What it is

A local MCP server built on the CData JDBC Driver for LinkedIn Ads, which presents the ad platform as relational SQL tables. The model is given the table list, the column list, and a read-only query tool, so campaign questions are answered from live data. It runs over stdio and therefore only works with a client on the same machine.

What you get

• The LinkedIn Ads tables the driver exposes, as CSV with a header row — linkedinads_get_tables
• The columns of a chosen table, so the model builds queries against real field names — linkedinads_get_columns
• A SQL SELECT run against live LinkedIn Ads data — linkedinads_run_query
• 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

A LinkedIn Ads account and a licensed CData JDBC Driver for LinkedIn Ads — trial licences are accepted via java -jar cdata.jdbc.linkedinads.jar --license. Java runs the server; Maven builds it with mvn clean install, producing CDataMCP-jar-with-dependencies.jar. A .prp connection file carries DriverClass as cdata.jdbc.linkedinads.LinkedInAdsDriver, the driver jar path, a tool Prefix such as linkedinads, and the JDBC connection string from the driver's Connection String utility — OAuth sources authenticate in the browser at that step. MIT licensed.

Setup effort

Build from source — git clone https://github.com/cdatasoftware/linkedin-ads-mcp-server-by-cdata.git

Tools you get

3 tools named in the project's documentation. Tool names start with the Prefix in the .prp file, so the README's Prefix=linkedinads gives linkedinads_get_tables, linkedinads_get_columns and linkedinads_run_query. All three only read: run_query executes SQL SELECT, despite a sentence in the documentation promising write, update and delete.

Where it runs

The documented client runs the server on your machine.