google-ad-manager-mcp-server-by-cdata
Provides a read-only MCP server that exposes Google Ad Manager data via CData’s JDBC Driver (as SQL-accessible relational models) to MCP-capable clients (e.g., Claude Desktop). It runs as a local stdio MCP server, using a .prp file to configure the JDBC driver and connection string.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
TLS enforcement for the JDBC connection is not explicitly documented in the README. Authentication is delegated to the CData JDBC driver (potentially OAuth), configured via a local .prp file; details of secret storage/redaction are not described. The MCP server allows running SQL SELECT queries; without explicit constraints, an agent could issue costly/overbroad queries against the connected data source. Dependency hygiene and CVE status are not assessable from the provided content.
⚡ Reliability
Best When
You have MCP-capable tooling on the same machine as the server and want quick read-only access to Google Ad Manager data through a consistent tool interface.
Avoid When
You need robust networked deployment, centralized auth/rate limiting, or guaranteed SQL safety/guardrails for user-supplied queries.
Use Cases
- • Ask questions about live Google Ad Manager data without writing SQL
- • Discover available tables/columns and run SELECT queries via MCP tools
- • Integrate Google Ad Manager reporting/lookup workflows into MCP-enabled desktop chat/agents
Not For
- • High-throughput multi-client remote access (stdio implies local-only use)
- • APIs/clients that require HTTP/REST connectivity to data
- • Write/update/delete operations (explicitly described as read-only MCP server)
Interface
Authentication
README notes that if the underlying data source uses OAuth, authentication is performed in a browser when testing connection. The MCP server itself is configured via a local .prp file containing JdbcUrl/connection details.
Pricing
README indicates use of the CData JDBC driver, which is typically a paid component/licensable. No pricing tiers are provided for the MCP wrapper itself.
Agent Metadata
Known Gotchas
- ⚠ Server uses stdio, so it can only be used by clients running on the same machine as the server.
- ⚠ The README examples include writing 'Source_get_tables' etc.; actual callable tool names in MCP are described as {servername}_get_tables/{servername}_get_columns/{servername}_run_query—agents must use the server-specific prefix.
- ⚠ No documented guardrails for SQL (the agent may attempt large/expensive queries); pagination/limits are not described.
- ⚠ If running Claude Desktop, the README notes you may need to fully quit and reopen for MCP servers to appear.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for google-ad-manager-mcp-server-by-cdata.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.