QuerySail: Google Analytics

com.querysailPublished by querysail.comOfficial publisherv1.0.0Updated Oct 24, 2026

Hosted, read-only Google Analytics 4 MCP: reports, period comparisons, realtime, custom fields.

The publisher's own server: QuerySail: Google Search Console

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Hosted, read-only Google Analytics 4 MCP server that lets an assistant list properties and run traffic, comparison and realtime reports in plain language.

What you can do
  • List readable GA4 properties and the dimensions, metrics and key events a property can report on
  • Run reports on users, sessions, views, engagement, events, key events and revenue, broken down by date, channel, source, page, country or device, with filters
  • Compare two periods and surface the channels, sources, pages or countries that gained or lost the most
  • Check active users, views and events in the last 30 minutes by country, city, device, page or event
When to use it
Useful when you want an assistant to answer questions about your own site or app analytics — traffic, engagement, conversions, period-over-period changes or live activity — without building Google Analytics API queries yourself.
Requirements
A remote Streamable HTTP endpoint with OAuth 2.1 sign-in; no install, Google Cloud project or API key. A QuerySail account with Google Analytics connected under Account → Connections, and a paid plan after a 7-day trial. Clients that only run local commands need Node.js for the mcp-remote bridge.
Before you install
Requires signing in to QuerySail and granting Google Analytics read access via the analytics.readonly scope; refresh tokens are stored encrypted by the provider. Reports are fetched from Google and cached up to 15 minutes, so analytics data passes through a third-party hosted service. Paid subscription after the trial. All tools are read-only and cannot change GA4 settings; Universal Analytics is unsupported and Google sampling or thresholding may apply.

Installation

In SourceWeft

  1. Open QuerySail: Google Analytics in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.querysail%2Fga4/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "querysail-google-analytics": {
      "type": "http",
      "url": "https://mcp.querysail.com/ga4/mcp"
    }
  }
}

README

QuerySail: Google Analytics MCP server

[QuerySail logo]

QuerySail is a hosted MCP server for Google Analytics 4. Connect it to ChatGPT, Claude, Codex, Cursor or VS Code, sign in, connect your Google account once, and ask about your traffic, engagement and conversions in plain language. There is nothing to install, no Google Cloud project and no API key to paste.

This repository holds the public listing files (MCP Registry server.json, a Claude Code plugin, client configs). The service itself is hosted at querysail.com; its source is not published here.

Tools

All tools are read-only. QuerySail cannot create or edit properties, data streams, key events, audiences or any other Google Analytics setting.

ToolWhat it does
list_propertiesLists the Google Analytics 4 properties your connected Google accounts can read, with exact property IDs and their Analytics accounts.
list_fieldsLists the dimensions and metrics a property can report on, including its custom dimensions, custom metrics and key events.
run_reportUsers, sessions, views, engagement, events, key events, revenue and any other Data API metric, broken down by date, channel, source/medium, landing page, page, country, device, event and more, with filters.
compare_reportCompares two periods (previous period, same weekdays a year earlier, or custom dates) and lists the channels, sources, pages or countries that gained or lost the most.
run_realtime_reportActive users, views and events in the last 30 minutes, by country, city, device, page or event.

Example prompts

  • How many users and sessions did my site have in the last 28 days?
  • Which channels brought the most sessions last month, and how did that change from the month before?
  • What are my top landing pages by key events?
  • How many people are on the site right now, and from which countries?
  • Compare organic search sessions with the same weeks last year.

Setup

You need a QuerySail account with Google Analytics connected: sign up at https://querysail.com and choose Connect Google Analytics under Account → Connections. Each client below opens a browser window to sign in the first time.

Claude Code

bash
claude mcp add --transport http --scope user querysail-ga4 https://mcp.querysail.com/ga4/mcp

Then run /mcp, choose querysail-ga4 and sign in. Or install it as a plugin, which also adds a Google Analytics analysis skill:

text
/plugin marketplace add querysail/querysail-ga4/plugin install querysail-ga4@querysail-ga4

Claude Desktop and claude.ai

Open Customize → Connectors, select + Add → Add custom connector, name it QuerySail GA4 and paste https://mcp.querysail.com/ga4/mcp as the server URL.

ChatGPT

Turn on Developer mode under Settings → Security and login, go to chatgpt.com/plugins, select the plus button and paste the endpoint as the connection URL.

Codex

bash
codex mcp add querysail-ga4 --url https://mcp.querysail.com/ga4/mcpcodex mcp login querysail-ga4

Cursor

Add to ~/.cursor/mcp.json:

json
{  "mcpServers": {    "querysail-ga4": { "url": "https://mcp.querysail.com/ga4/mcp" }  }}

VS Code

Run MCP: Add Server, choose HTTP and paste the endpoint, or add to mcp.json:

json
{  "servers": {    "querysail-ga4": { "type": "http", "url": "https://mcp.querysail.com/ga4/mcp" }  }}

Cline

Open MCP Servers → Remote Servers, name it querysail-ga4, paste the endpoint, choose Streamable HTTP and click Add Server. Or add to cline_mcp_settings.json:

json
{  "mcpServers": {    "querysail-ga4": { "type": "streamableHttp", "url": "https://mcp.querysail.com/ga4/mcp" }  }}

Sign in with your QuerySail account when Cline asks.

Clients that only run local commands

Use the mcp-remote bridge (needs Node.js):

json
{  "mcpServers": {    "querysail-ga4": { "command": "npx", "args": ["mcp-remote", "https://mcp.querysail.com/ga4/mcp"] }  }}

Agent skill

The querysail-google-analytics skill tells coding agents such as Claude Code, Codex, Cursor and OpenCode which QuerySail tool to call for each question and how to report the numbers. Install it with the skills CLI (needs Node.js):

bash
npx skills add https://querysail.com --skill querysail-google-analytics

Data and limits

  • Google access uses the analytics.readonly scope, granted separately from Search Console. Refresh tokens are encrypted at rest. You can hide properties, disconnect Google or delete your account at any time.
  • Reports are fetched from Google when asked and cached for at most 15 minutes; realtime reports are not cached. Universal Analytics properties are not supported.
  • Google may apply thresholding or sampling to some reports; QuerySail passes those flags on to your assistant. Google's per-property API quotas apply.
  • Privacy: https://querysail.com/privacy · Terms: https://querysail.com/terms · Support: https://querysail.com/support

License

The files in this repository are MIT licensed. The QuerySail service is subject to its terms.

Source: README.md at commit d496671

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 11, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Querysail integrations

QuerySail: Google Search Console

com.querysailOfficial publisher

Hosted, read-only Google Search Console MCP server that lets an assistant query search performance, compare periods, inspect URLs and list sitemaps.

Streamable HTTPWeb executableAuth
Web Search & ScrapingCredential requiredOct 24, 2026