Linkedin Ads MCP Server By Cdata

🚀 LinkedIn Ads MCP Server by CData

CData's Model Context Protocol (MCP) Server for LinkedIn Ads, enabling LLMs to query live data.

🚀 Quick Start

This project builds a read-only MCP server. For full read, write, update, delete, and action capabilities and a simplified setup, check out our free CData MCP Server for LinkedIn Ads (beta).

✨ Features

We created this read-only MCP Server to allow LLMs (like Claude Desktop) to query live data from LinkedIn Ads supported by the CData JDBC Driver for LinkedIn Ads. The CData JDBC Driver connects to LinkedIn Ads by exposing them as relational SQL models. This server wraps that driver and makes LinkedIn Ads data available through a simple MCP interface, so LLMs can retrieve live information by asking natural language questions — no SQL required.

📦 Installation

1. Clone the repository:

git clone https://github.com/cdatasoftware/linkedin-ads-mcp-server-by-cdata.git
cd linkedin-ads-mcp-server-by-cdata

2. Build the server:

mvn clean install

This creates the JAR file: CDataMCP-jar-with-dependencies.jar

3. Download and install the CData JDBC Driver for {source}: https://www.cdata.com/drivers/linkedinads/download/jdbc

4. License the CData JDBC Driver:

   • Navigate to the lib folder in the installation directory, typically:
     • (Windows) C:\Program Files\CData\CData JDBC Driver for LinkedIn Ads\
     • (Mac/Linux) /Applications/CData JDBC Driver for LinkedIn Ads/
   • Run the command java -jar cdata.jdbc.linkedinads.jar --license
   • Enter your name, email, and "TRIAL" (or your license key).

5. Configure your connection to the data source (Salesforce as an example):

   • Run the command java -jar cdata.jdbc.linkedinads.jar to open the Connection String utility.
   • Configure the connection string and click "Test Connection"

     ⚠️ Important Note

     If the data sources uses OAuth, you will need to authenticate in your browser.

   • Once successful, copy the connection string for use later.

6. Create a .prp file for your JDBC connection (e.g. linkedin-ads.prp) using the following properties and format:

   • Prefix - a prefix to be used for the tools exposed
   • ServerName - a name for your server
   • ServerVersion - a version for your server
   • DriverPath - the full path to the JAR file for your JDBC driver
   • DriverClass - the name of the JDBC Driver Class (e.g. cdata.jdbc.linkedinads.LinkedInAdsDriver)
   • JdbcUrl - the JDBC connection string to use with the CData JDBC Driver to connect to your data (copied from above)
   • Tables - leave blank to access all data, otherwise you can explicitly declare the tables you wish to create access for

Prefix=linkedinads
ServerName=CDataLinkedInAds
ServerVersion=1.0
DriverPath=PATH\TO\cdata.jdbc.linkedinads.jar
DriverClass=cdata.jdbc.linkedinads.LinkedInAdsDriver
JdbcUrl=jdbc:linkedinads:InitiateOAuth=GETANDREFRESH;
Tables=

💻 Usage Examples

Using the Server with Claude Desktop

1. Create the config file for Claude Desktop (claude_desktop_config.json) to add the new MCP server, using the format below. If the file already exists, add the entry to the mcpServers in the config file.

Windows

{
    "mcpServers": {
        "{classname_dash}": {
            "command": "PATH\\TO\\java.exe",
            "args": [
                "-jar",
                "PATH\\TO\\CDataMCP-jar-with-dependencies.jar",
                "PATH\\TO\\linkedin-ads.prp"
            ]
        }
    }
}

Linux/Mac

{
    "mcpServers": {
        "{classname_dash}": {
            "command": "/PATH/TO/java",
            "args": [
                "-jar",
                "/PATH/TO/CDataMCP-jar-with-dependencies.jar",
                "/PATH/TO/linkedin-ads.prp"
            ]
        }
    }
}

If needed, copy the config file to the appropriate directory (Claude Desktop as the example). Windows

cp C:\PATH\TO\claude_desktop_config.json %APPDATA%\Claude\claude_desktop_config.json

Linux/Mac

cp /PATH/TO/claude_desktop_config.json /Users/{user}/Library/Application\ Support/Claude/claude_desktop_config.json

2. Run or refresh your client (Claude Desktop).

⚠️ Important Note

You may need to fully exit or quit your Claude Desktop client and re-open it for the MCP Servers to appear.

Running the Server

Run the following command to run the MCP Server on its own:

java -jar /PATH/TO/CDataMCP-jar-with-dependencies.jar /PATH/TO/Salesforce.prp

⚠️ Important Note

The server uses stdio so can only be used with clients that run on the same machine as the server.

📚 Documentation

Once the MCP Server is configured, the AI client will be able to use the built-in tools to read, write, update, and delete the underlying data. In general, you do not need to call the tools explicitly. Simply ask the client to answer questions about the underlying data system. For example:

• "What is the correlation between my closed won opportunities and the account industry?"
• "How many open tickets do I have in the SUPPORT project?"
• "Can you tell me what calendar events I have today?"

The list of tools available and their descriptions follow:

Tools & Descriptions

In the definitions below, {servername} refers to the name of the MCP Server in the config file (e.g. {classname_dash} above).

• {servername}_get_tables - Retrieves a list of tables available in the data source. Use the {servername}_get_columns tool to list available columns on a table. The output of the tool will be returned in CSV format, with the first line containing column headers.
• {servername}_get_columns - Retrieves a list of columns for a table. Use the {servername}_get_tables tool to get a list of available tables. The output of the tool will be returned in CSV format, with the first line containing column headers.
• {servername}_run_query - Execute a SQL SELECT query

JSON-RPC Request Examples

If you are scripting out the requests sent to the MCP Server instead of using an AI Client (e.g. Claude), then you can refer to the JSON payload examples below – following the JSON-RPC 2.0 specification - when calling the available tools.

source_get_tables

{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
        "name": "source_get_tables",
        "arguments": {}
    }
}

source_get_columns

{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
        "name": "source_get_columns",
        "arguments": {
            "table":  "Account"
        }
    }
}

source_run_query

{
    "jsonrpc": "2.0",
    "id": 3,
    "method": "tools/call",
    "params": {
        "name": "source_run_query",
        "arguments": {
            "sql":  "SELECT * FROM [Account] WHERE [IsDeleted] = true"
        }
    }
}

🔧 Technical Details

No technical details provided in the original document.

📄 License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.

All Supported Sources