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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago