Google Analytics Data API MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Google Analytics Data API MCP Server?

Google Analytics Data API MCP Server provides an interface to access the Google Analytics Data API using the Model Context Protocol (MCP).

How to use Google Analytics Data API MCP Server?

To use the server, set up a Google Cloud project, enable the Analytics Data API, create a service account, and configure the environment variables. Then, start the server using npm.

Key features of Google Analytics Data API MCP Server?

  • get_report: Retrieve reports based on specified date ranges, metrics, and dimensions.
  • get_realtime_data: Access real-time data from Google Analytics.
  • Access to Google Analytics property metadata.

Use cases of Google Analytics Data API MCP Server?

  1. Generating reports on user activity over a specified period.
  2. Monitoring real-time user engagement on a website.
  3. Accessing metadata for Google Analytics properties.

FAQ from Google Analytics Data API MCP Server?

  • Can I use this server for all Google Analytics properties?

Yes! It can be configured to work with any GA4 property.

  • Is there a setup guide available?

Yes! Detailed setup instructions can be found in the setup guide.

  • What programming language is this server built with?

The server is built using JavaScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
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