bing-ads -by-cdata

This MCP server provides a read-only interface to Bing Ads data via the CData JDBC Driver. It exposes a set of MCP tools that allow a client (such as Claude Desktop or other MCP clients) to list available tables, inspect columns, and run SQL queries against Bing Ads data through a JDBC bridge. The server runs locally and uses stdio for communication, so it should be run on the same machine as the client. To use it, start the MCP jar with your prepared .prp configuration file (which contains the connection details to Bing Ads via the JDBC driver). In Claude Desktop, register an MCP server entry that points to the Java launch command and include the path to the bing-ads.prp file as an argument. Once configured, you can issue tool calls like get_tables, get_columns, or run_query to retrieve results in CSV or structured formats. Typical queries might retrieve ad performance metrics, campaigns, or keywords, depending on the tables exposed by the JDBC driver.

Prerequisites:

• Java Runtime Environment (JRE) or JDK installed and available on your PATH
• Maven (for building the server) if you intend to build from source
• Bing Ads CData JDBC Driver downloaded and licensed

Step-by-step:

1. Clone the repository and navigate to the project root: git clone https://github.com/cdatasoftware/bing-ads-mcp-server-by-cdata.git cd bing-ads-mcp-server-by-cdata

2. Build the MCP server (if you are building from source): mvn clean install This will produce a JAR named something like CDataMCP-jar-with-dependencies.jar

3. Install and license the CData JDBC Driver for Bing Ads (outside the MCP server):

   • Download the driver from: https://www.cdata.com/drivers/bingads/download/jdbc
   • Install it according to the vendor instructions
   • License the driver by running in your installation's lib directory: java -jar cdata.jdbc.bingads.jar --license
   • Provide your name, email, and a license key (or TRIAL)

4. Configure a .prp file (e.g., bing-ads.prp) with connection details to Bing Ads via the JDBC driver. Example content: Prefix=bingads ServerName=CDataBingAds ServerVersion=1.0 DriverPath=PATH\TO\cdata.jdbc.bingads.jar DriverClass=cdata.jdbc.bingads.BingAdsDriver JdbcUrl=jdbc:bingads:InitiateOAuth=GETANDREFRESH; Tables=

5. Run the MCP server using the prepared .prp file: java -jar /path/to/CDataMCP-jar-with-dependencies.jar /path/to/bing-ads.prp

6. (Optional) Configure Claude Desktop or another MCP client with the server entry, pointing to the Java executable and passing the path to the bing-ads.prp file as an argument.

Prerequisites recap: Java installed and on PATH, the CData Bing Ads JDBC Driver installed and licensed, and a valid bing-ads.prp configuration file ready.

Notes and tips:

• The MCP server is read-only in this setup; write/update/delete operations are not exposed.
• The server uses stdio; ensure the client runs on the same machine or adapt the setup accordingly if using a different IPC method.
• Ensure the JDBC driver is licensed; without a valid license, connections may fail.
• If you encounter connection issues, verify the JdbcUrl and any OAuth flow requirements in the connection utility beforehand, and copy the resulting connection string into bing-ads.prp.
• When configuring Claude Desktop, fully restart the client after adding the MCP server so the new server appears in the UI.
• The tool names follow the pattern {servername}_get_tables, {servername}_get_columns, and {servername}_run_query; replace {servername} with the actual configured prefix in bing-ads.prp (e.g., bingads).
• Example outputs are returned in CSV format for tables and columns and as SQL query results for run_query.