{"id":"cdatasoftware-google-ad-manager-mcp-server-by-cdata","name":"google-ad-manager-mcp-server-by-cdata","af_score":53.2,"security_score":49.2,"reliability_score":32.5,"what_it_does":"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.","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.","last_evaluated":"2026-04-04T19:39:11.660554+00:00","has_mcp":true,"has_api":false,"auth_methods":["CData JDBC driver authentication (connection string; may involve OAuth per README note)","JDBC driver licensing (separate from data auth)"],"has_free_tier":false,"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."],"error_quality":0.0}