google-analytics-mcp-server-by-cdata
Provides a local, read-only Model Context Protocol (MCP) server that exposes Google Analytics data to LLM clients. It wraps a CData JDBC Driver for Google Analytics, generates MCP tools for listing tables/columns and executing SQL SELECT queries via tools/call, and is intended to be run locally using stdio (same machine as the MCP client).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Local stdio reduces network exposure, but secrets/connection strings are placed in a local .prp file; the README does not discuss secure storage, redaction, or log handling. OAuth may be required via browser for the JDBC driver, but scope/granularity and token lifecycle handling are not documented in this repo. No explicit TLS/network security controls apply beyond 'local' operation; if any remote components are used, they are not described here. Dependency/CVE hygiene is not assessable from the provided content.
⚡ Reliability
Best When
You want on-device (local) integration from an MCP client (e.g., Claude Desktop) to query Google Analytics via a JDBC-backed SQL interface.
Avoid When
You need network-accessible remote MCP endpoints, fine-grained authorization management within this repo, or guaranteed operational controls like published SLAs/rate-limit contracts.
Use Cases
- • Querying live Google Analytics data from an MCP-capable desktop client without writing SQL
- • Exploratory analytics and ad-hoc reporting (e.g., totals, breakdowns, correlations) via natural-language tool use
- • Building lightweight internal dashboards/assistants that answer questions over GA data
Not For
- • Production multi-tenant or remote MCP access scenarios (stdio is local-only per README)
- • Write/update/delete GA data (README describes the MCP server as read-only)
- • Use cases requiring a hosted API gateway, rate-limit headers, or managed OAuth flows inside this repo
Interface
Authentication
Auth details for OAuth scopes are not documented in this README; it references that OAuth may require browser authentication for the JDBC driver/connection string.
Pricing
README explicitly requires licensing the CData JDBC Driver; pricing terms are not provided here.
Agent Metadata
Known Gotchas
- ⚠ Server uses stdio, so it can only be used by clients running on the same machine.
- ⚠ The README claims read-only behavior, but also mentions write/update/delete capability in a general paragraph—this mismatch may confuse agents; treat available tools as limited to the listed tools (get_tables/get_columns/run_query) and underlying JDBC driver permissions.
- ⚠ SQL is passed through run_query; the AI may generate inefficient or invalid SQL—there is no SQL safety/validation guidance in the README.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for google-analytics-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.