2,500+ MCP servers ready to use
Vinkius

Google Analytics MCP Server for LlamaIndex 12 tools — connect in under 2 minutes

Built by Vinkius GDPR 12 Tools Framework

LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add Google Analytics as an MCP tool provider through Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    agent = FunctionAgent(
        tools=tools,
        llm=OpenAI(model="gpt-4o"),
        system_prompt=(
            "You are an assistant with access to Google Analytics. "
            "You have 12 tools available."
        ),
    )

    response = await agent.run(
        "What tools are available in Google Analytics?"
    )
    print(response)

asyncio.run(main())
Google Analytics
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Google Analytics MCP Server

Connect your Google Analytics 4 (GA4) account to any AI agent and take full control of web and app analytics through natural conversation.

LlamaIndex agents combine Google Analytics tool responses with indexed documents for comprehensive, grounded answers. Connect 12 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.

What you can do

  • Custom Reports — Run reports with any combination of metrics (activeUsers, screenPageViews, sessions, eventCount) and dimensions (city, country, deviceCategory, channel grouping)
  • Realtime Data — Monitor what's happening on your site right now with live user counts, events, and traffic sources from the last 30-60 minutes
  • Batch Reports — Execute multiple report configurations in a single API call for efficient dashboard loading
  • Metadata Discovery — List all available metrics and dimensions for your property, including custom definitions
  • Compatibility Checks — Validate metric/dimension combinations before running reports to avoid errors
  • Audience Exports — List and monitor audience export jobs for user segmentation and activation
  • User Activity — Retrieve event history for specific users for journey analysis and support investigations
  • Funnel Analysis — Visualize user progression through conversion steps and identify drop-off points

The Google Analytics MCP Server exposes 12 tools through the Vinkius. Connect it to LlamaIndex in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Google Analytics to LlamaIndex via MCP

Follow these steps to integrate the Google Analytics MCP Server with LlamaIndex.

01

Install dependencies

Run pip install llama-index-tools-mcp llama-index-llms-openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.py and run: python agent.py

04

Explore tools

The agent discovers 12 tools from Google Analytics

Why Use LlamaIndex with the Google Analytics MCP Server

LlamaIndex provides unique advantages when paired with Google Analytics through the Model Context Protocol.

01

Data-first architecture: LlamaIndex agents combine Google Analytics tool responses with indexed documents for comprehensive, grounded answers

02

Query pipeline framework lets you chain Google Analytics tool calls with transformations, filters, and re-rankers in a typed pipeline

03

Multi-source reasoning: agents can query Google Analytics, a vector store, and a SQL database in a single turn and synthesize results

04

Observability integrations show exactly what Google Analytics tools were called, what data was returned, and how it influenced the final answer

Google Analytics + LlamaIndex Use Cases

Practical scenarios where LlamaIndex combined with the Google Analytics MCP Server delivers measurable value.

01

Hybrid search: combine Google Analytics real-time data with embedded document indexes for answers that are both current and comprehensive

02

Data enrichment: query Google Analytics to augment indexed data with live information before generating user-facing responses

03

Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying Google Analytics for fresh data

04

Analytical workflows: chain Google Analytics queries with LlamaIndex's data connectors to build multi-source analytical reports

Google Analytics MCP Tools for LlamaIndex (12)

These 12 tools become available when you connect Google Analytics to LlamaIndex via MCP:

01

batch_run_reports

Provide property_id and an array of report configurations. Each report can have different metrics, dimensions, and date ranges. This is efficient for dashboard loading or comparative analysis. The reports parameter should be a JSON array of report objects with metrics, dimensions, and dateRanges. Run multiple reports in a single API call

02

check_compatibility

Before running complex reports, use this to ensure compatibility between your chosen metrics and dimensions. This prevents errors and wasted API calls. Provide property_id and the metrics/dimensions you plan to use. Returns compatibility status and any conflicts that would prevent the report from running successfully. Check if metrics and dimensions can be combined in a report

03

get_audience_export

Audience exports allow you to extract user lists matching specific audience criteria. Use this to monitor the progress of audience extraction jobs. Provide property_id and the audience_export_id from list_audience_exports. Get status of a specific audience export

04

get_metadata

This includes both standard and custom metrics/dimensions with their descriptions, types, and compatibility information. Use this to discover what data is available before building reports. The propertyId is required and can be found in your GA4 admin settings. Get available metrics and dimensions for a GA4 property

05

get_property

Use the property_id obtained from list_properties to inspect property configuration. Get detailed information about a specific GA4 property

06

get_user_activity

This shows all interactions a user has had with your property, including pageviews, events, and conversions. Use this for user-level analysis, journey mapping, or support investigations. The userId must match the one sent with your tracking events. Get activity history for a specific user

07

list_accounts

This is the top-level container for properties. Each account can contain multiple properties. Use this to discover what accounts are available before drilling down into properties. List all Google Analytics accounts accessible to the user

08

list_audience_exports

Audience exports are used to extract user lists matching specific audience criteria for activation in other platforms. Shows status (CREATING, ACTIVE, FAILED) and configuration of each export job. List all audience export jobs for a property

09

list_properties

Properties represent individual websites, apps, or measurement streams. Each property has a unique ID needed for running reports. Use this to find the correct property_id for report queries. List all GA4 properties in an account

10

run_funnel_report

This helps identify where users drop off in conversion paths like checkout flows or signup processes. Provide property_id and a funnelSpec object defining the steps and breakdown settings. The funnelSpec should be a JSON object with steps array containing stepName, filterExpression, and optional breakdown settings. Run a funnel analysis report

11

run_realtime_report

Unlike standard reports, this shows what's happening on your site/app right now. Provide property_id and the metrics/dimensions you want to monitor in realtime. Common realtime metrics: activeUsers, eventCount, screenPageViews. Common realtime dimensions: city, country, deviceCategory, streamId. Get realtime analytics data (last 30-60 minutes)

12

run_report

You must provide the property_id, metrics (e.g., 'activeUsers', 'screenPageViews', 'eventCount'), and dimensions (e.g., 'city', 'pageTitle', 'sessionDefaultChannelGrouping'). Date ranges use YYYY-MM-DD format. Optional filter expression can narrow results. Common metrics: activeUsers, screenPageViews, sessions, eventCount, engagementRate, averageSessionDuration. Common dimensions: city, country, deviceCategory, sessionDefaultChannelGrouping, pageTitle, pagePath. Run a custom Google Analytics report

Example Prompts for Google Analytics in LlamaIndex

Ready-to-use prompts you can give your LlamaIndex agent to start working with Google Analytics immediately.

01

"Show me the number of active users and pageviews by country for the last 7 days for property 123456789."

02

"What's happening on the site right now? Show me realtime users by traffic source."

03

"Run a funnel analysis for our checkout flow: step 1 = viewed product, step 2 = added to cart, step 3 = started checkout, step 4 = completed purchase. Show me where users drop off."

Troubleshooting Google Analytics MCP Server with LlamaIndex

Common issues when connecting Google Analytics to LlamaIndex through the Vinkius, and how to resolve them.

01

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

Google Analytics + LlamaIndex FAQ

Common questions about integrating Google Analytics MCP Server with LlamaIndex.

01

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
02

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query Google Analytics tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
03

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

Connect Google Analytics to LlamaIndex

Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.