The analytics MCP: every read-only tool

Fifteen tools, one scope, no way to change anything.

ReferenceUpdated 9 September 2026Checked against GemBoss MCP, August 2026

This is the measuring half of the MCP surface. Everything here carries the workflow:read scope, so it is the safest server to hand an agent: there is no tool on it that can change or publish anything.

Calling it

Every call is a JSON-RPC 2.0 request authenticated with your key.

POST /api/mcp Authorization: Bearer <your-key> { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "gemboss.get_metrics", "arguments": { "shop_id": "your-store.myshopify.com" } } }

In practice you do not write this by hand. Connect the server to Claude and ask in words.

What to know

Read-only. These tools carry the workflow:read scope. Nothing here can change or publish your store.
Scoped per shop. A key is bound to the shops it may read. A request for any other shop is rejected before it reaches your data.
Issued to you, by you. Connect at https://mcp.gemboss.com/mcp and sign in through your browser; GemBoss issues the credential itself, scoped to the stores you pick. Static keys issued to older workspaces keep working.

The tools

Tool	What it returns
`gemboss.get_metrics`	Funnel, conversion rate, AOV, per-section engagement and per-variant CR. Start here for any performance question.
`gemboss.get_tracking_health`	Whether the data can be trusted at all: missing data, broken purchase to session stitching, thin COGS coverage.
`gemboss.get_segment_funnel`	The funnel broken down by segment, with the sessions reaching each stage.
`gemboss.get_device_metrics`	Sessions, CR, AOV and profit by device: mobile, tablet, desktop.
`gemboss.get_source_metrics`	The same by traffic channel: direct, organic, social, referral. Covers traffic that carries no tags.
`gemboss.get_visitor_metrics`	New against returning visitors, each with sessions, CR, AOV and profit.
`gemboss.get_campaign_revenue`	Revenue and profit per marketing campaign by UTM, first touch, ranked by profit rather than revenue.
`gemboss.get_time_patterns`	When people shop and convert, by day of week and hour of day, in UTC.
`gemboss.get_recommendations`	Ranked CRO hypotheses with the reasoning, section aware when you pass a job id.
`gemboss.get_behavior_signals`	Top products viewed per SKU, top on-site search terms, and video engagement.
`gemboss.get_search_performance`	Organic queries from Google Search Console with clicks, impressions, CTR and average position.
`gemboss.get_ga_traffic`	Sessions, conversions and revenue per channel from Google Analytics 4.
`gemboss.get_market_signals`	Tracked competitors' price moves and the price band of your niche.
`gemboss.list_campaigns`	The shop's governed campaigns and their status, the unit that launches and tests run through.
`gemboss.get_store_state`	Which theme is live, the latest job, the latest client review verdict, and the Shopify connection.

The other server

Building and changing things lives on the same connection, under gem.* and gemtheme.*. The tools you are shown are filtered to the ones your credential may actually call, so the list length varies by account. See what Claude can and cannot change for how those are gated.

Stuck on the connection?

You connect at https://mcp.gemboss.com/mcp and sign in through your browser — there is no key to ask for. If the browser step does not finish, the troubleshooting page walks through what to check.

When the connection will not come up →

Was this page useful?