google-analytics-mcp-server-by-cdata

Created By
CDataSoftwarea year ago
This read-only MCP Server allows you to connect to Google Analytics data from Claude Desktop through CData JDBC Drivers. Free (beta) read/write servers available at
Overview

What is Google Analytics MCP Server by CData?

This project is a read-only Model Context Protocol (MCP) Server that allows users to connect to Google Analytics data through CData JDBC Drivers, enabling natural language queries without needing SQL.

How to use Google Analytics MCP Server?

To use the server, clone the repository, build it, install the CData JDBC Driver, configure your connection, and create a configuration file for your AI client (e.g., Claude Desktop).

Key features of Google Analytics MCP Server?

  • Provides a read-only interface to Google Analytics data.
  • Allows querying of live data using natural language.
  • Simplifies data access without requiring SQL knowledge.

Use cases of Google Analytics MCP Server?

  1. Querying live Google Analytics data for insights.
  2. Integrating with AI clients for automated reporting.
  3. Enabling data analysis through natural language questions.

FAQ from Google Analytics MCP Server?

  • Can I write data to Google Analytics using this server?

No, this server is read-only. For write capabilities, consider the full CData MCP Server for Google Analytics.

  • Is there a cost to use this server?

The server is currently in beta and is free to use.

  • What programming language is this server built with?

The server is built using Java.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
CDataSoftware
Star
0
Language
Java
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

11 hours ago