MCP Search Analytics Server

Created By
dexter480a year ago
MCP server for GA and GSC data analysis
Overview

what is MCP Search Analytics Server?

MCP Search Analytics Server is a Model Context Protocol (MCP) server designed for analyzing data from Google Analytics and Google Search Console.

how to use MCP Search Analytics Server?

To use the MCP Search Analytics Server, clone the repository, set up a virtual environment, install the required dependencies, configure your Google Service Account, and run the server to access real-time analytics data.

key features of MCP Search Analytics Server?

  • Unified access to Google Analytics 4 and Google Search Console data
  • Real-time analytics queries through the MCP interface
  • Secure credential management via environment variables

use cases of MCP Search Analytics Server?

  1. Analyzing website traffic and performance metrics from Google Analytics.
  2. Monitoring search performance and visibility through Google Search Console.
  3. Integrating data from multiple sources for comprehensive analytics reporting.

FAQ from MCP Search Analytics Server?

  • What are the prerequisites for using this server?

You need Python 3.8+, a Google Cloud Project with Analytics and Search Console APIs enabled, and a Google Service Account with appropriate permissions.

  • Is it secure to use this server?

Yes, it emphasizes secure credential management and advises against committing sensitive files to version control.

  • Can I contribute to this project?

Yes! You can fork the repository, create a feature branch, and submit a pull request after making your changes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dexter480
Star
0
Language
Python
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)

2 days ago