Google Analytics Data API MCP Server

Created By
mattcoatswortha year ago
Overview

What is Google Analytics Data API MCP Server?

Google Analytics Data API MCP Server is a Model Context Protocol (MCP) server designed for interacting with the Google Analytics Data API v1, providing tools for querying Google Analytics data, managing audiences, and accessing metadata.

How to use Google Analytics Data API MCP Server?

To use the server, clone the repository, install the necessary dependencies, set up your Google Analytics credentials in a .env file, and run the server using npm start.

Key features of Google Analytics Data API MCP Server?

  • Run standard and pivot reports
  • Batch reporting capabilities
  • Access metadata about dimensions and metrics
  • Create, list, update, and delete audiences
  • Check compatibility between dimensions and metrics
  • Comprehensive resource endpoints for exploring GA data

Use cases of Google Analytics Data API MCP Server?

  1. Generating detailed reports on user interactions and behaviors.
  2. Managing audience segments for targeted marketing campaigns.
  3. Accessing and analyzing metadata for better data insights.

FAQ from Google Analytics Data API MCP Server?

  • What are the prerequisites for using this server?

You need Node.js 14 or higher, a Google Analytics 4 property, and a Google Cloud service account with appropriate permissions.

  • Is there a license for this project?

Yes, the project is licensed under MIT.

  • How can I run multiple reports at once?

You can use the batchRunReports feature to run multiple reports in a single batch.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mattcoatsworth
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