home / mcp / google campaign manager 360 mcp server
This read-only MCP Server allows you to connect to Google Campaign Manager 360 data from Claude Desktop through CData JDBC Drivers. For full CRUD support, check out the first managed MCP platform: CData Connect AI (https://www.cdata.com/ai/).
Configuration
View docs{
"mcpServers": {
"cdatasoftware-google-campaign-manager-360-mcp-server-by-cdata": {
"command": "java",
"args": [
"-jar",
"CDataMCP-jar-with-dependencies.jar",
"/PATH/TO/google-campaign-manager-360.prp"
]
}
}
}You can query live Google Campaign Manager 360 data through a local MCP server that wraps the CData JDBC Driver. This server exposes GC Manager 360 data via a simple MCP interface, allowing you to ask natural language questions and retrieve results without writing SQL. The setup is designed for local, read-only access, enabling LLMs to fetch up-to-date information from Google Campaign Manager 360.
Once the MCP server is running on your machine, you connect your MCP client (such as Claude Desktop or another compatible AI client) to the local process. You do not need to issue SQL queries; you simply ask for the data you need in natural language and let the AI client generate the appropriate requests under the hood. Typical usage includes asking for campaign performance metrics, listing active campaigns, or retrieving recent events and their statuses. The server exposes a predictable set of tools to inspect the data model, list tables and columns, and run read-only queries that fetch the data you request.
Prerequisites: Java and Maven must be available on your system.
Step 1. Clone the project and navigate into the directory.
Step 2. Build the server to produce the runnable JAR.
# clone the project
git clone https://github.com/cdatasoftware/google-campaign-manager-360-mcp-server-by-cdata.git
cd google-campaign-manager-360-mcp-server-by-cdata
# build the MCP server JAR
mvn clean installThe server is a local, stdio-based MCP server. You start it by running the Java JAR and passing the path to a property file that contains the JDBC connection details.
Example start command (adjust the path to your generated JAR and to your google-campaign-manager-360.prp):
java -jar CDataMCP-jar-with-dependencies.jar /PATH/TO/google-campaign-manager-360.prpThe server provides standard MCP tools to interact with the data model. Each tool exposes a specific function to discover data structures and fetch data:
- googlecampaign360_get_tables — Retrieves a list of tables available in the data source. The output is in CSV format with column headers on the first line.
- googlecampaign360_get_columns — Retrieves a list of columns for a specified table. The output is in CSV format with column headers on the first line.
- googlecampaign360_run_query — Executes a SQL SELECT query against the data source.
This server is implemented in Java and is built with Maven. The configuration uses a .prp file to specify JDBC connection details. No additional environment variables are required for the basic read-only setup.
If the MCP server does not appear in your client, ensure you have fully stopped and restarted the client so it discovers local servers. Verify the path to the .prp file and confirm the JAR was built successfully. If you still encounter issues, confirm the JDBC driver license and connection string are correctly configured in the .prp file.
This MCP server is intended for local, read-only access to Google Campaign Manager 360 data via the CData JDBC Driver. Ensure you manage access to the local machine and control which clients can connect to the MCP server.
The server is distributed under the MIT License. This allows you to use, modify, and distribute the software under the terms of that license.
Retrieves a list of tables available in the data source. Output is CSV with column headers on the first line.
Retrieves a list of columns for a table. Output is CSV with column headers on the first line.
Executes a SQL SELECT query against the data source and returns results.