Edgemesh Connector — Team Guide

READ-ONLY

Ask Claude how melindamaria.com is performing — site speed and the full shopping funnel — in plain English. Which pages are slow? Where do shoppers drop off? What's our conversion rate? No dashboards to learn. Just ask.

Status: Live ✓ Version: 0.1.0 Updated: June 26, 2026 Access: read-only — analytics API, no writes API limit: no fixed per-call limit documented Sign-in: your Google work account Questions: David
3.45M
distinct users (90 days)
3.82M
sessions (90 days)
12.9M
page views (90 days)
64%
new users
70%
avg. cache-hit rate

Live numbers for melindamaria.com, last 90 days (pulled June 26, 2026). Ask Claude for the latest anytime.

What it is Connect in 1 minute How to ask Example prompts Limits & risks Get help / request more Live artifacts Architecture How your data flows

What is the Edgemesh connector?

Edgemesh is the analytics layer running on melindamaria.com — it measures both site performance (how fast pages load for real shoppers) and conversion (the shopping funnel from landing to purchase). The Edgemesh connector lets Claude ask those analytics real questions on your behalf, so anyone on the team can understand site speed and shopper behavior without opening a dashboard or knowing any code.

📈 What it knows

Two lenses. Performance — real-user Core Web Vitals & load times (LCP, FCP, TTFB, page-load, layout shift) sliceable by page, device, country, and date. Conversion — the full funnel (sessions → product/category views → cart → checkout → purchase), plus revenue-per-user, new-vs-returning, and breakdowns by referrer, UTM, country, and device.

🔒 What it can't do

It is read-only. It can look at the analytics but cannot change anything — no edits to the site, the tags, or the data. It only reports on what already happened. Safe for the whole team to explore.

🧠 What makes it useful

It answers "why are sales soft?" in business terms: is the site slow on mobile, or are shoppers dropping at checkout? It turns raw web analytics into plain-English answers — and pairs perfectly with our sales connectors.

Why we built it: site speed and a smooth funnel directly drive revenue. This connector lets the whole team self-serve the numbers behind conversion — find the slow pages costing us sales, see exactly where shoppers leave, and learn which traffic sources actually convert.
What's "MCP"? MCP (Model Context Protocol) is the standard way Claude plugs into outside tools and data. A "connector" is a small piece of software that exposes a set of tools Claude can call. Each tool here is one safe, read-only question you can ask about our site's performance or conversion.

Connect it in about a minute

How to connect in three steps Open Settings then Connectors in Claude, find this connector and click Connect, then sign in once with the account noted below. Settings Profile Connectors Data controls 1 · Open Settings → Connectors MM This connectornot connected Connect 2 · Find it · click Connect you@melindamaria.com •••••••• Sign in ✓ 3 · Sign in once — done
In Claude: Settings → Connectors → find it → click Connect → sign in. It’s already added for the team, so this is a one-time, ~1-minute step (see “Which login” below).

The Edgemesh connector is already set up in Claude for the team — you just switch it on and sign in. Takes about 30 seconds.

1
In Claude, open SettingsConnectors (or click the + in the message box → Connectors). Find Edgemesh in the list — it's already there.
2
Click the + (or Connect) next to Edgemesh.
3
When prompted, sign in through Edgemesh’s login with your MM work email. You never paste an API key — Edgemesh handles the secure part.
4
Approve the connection. It shows Connected — then try "Using Edgemesh, show our site conversion rate for the last 30 days." A real number back means you're live.
🔑 Which login? This one signs in through Edgemesh’s own login (their secure OAuth page) using your MM work email — it’s Edgemesh-hosted, so there’s no Google gate on our side. You never paste any API key.
Don't see it in your Connectors list? Ask David — it gets enabled once for the team, then appears for everyone to switch on.

How to ask — just say "use Edgemesh…"

The connector is named Edgemesh. The simplest way to make sure Claude uses it is to mention it in your request:

"Using Edgemesh, <your question>."

You don't have to memorize tool names — plain English works. A few tips that get great results:

Say which lens you mean

"…how fast our pages load" (performance) vs. "…where shoppers drop off" (conversion). Naming speed or funnel points Claude at the right tool.

Be specific about the slice

"…on mobile", "…by country", "…for the product pages", "…over the last 30 days". Dimensions and time frames sharpen the answer.

Ask for the format you want

"…as a table", "…worst 10 pages", "…make a PDF", "…show the drop-off at each step". Claude will shape it.

Chain connectors in one ask

You can combine tools: "compare Edgemesh conversion to Shopify sales", "match Edgemesh traffic to ShopMy creator referrals". See the multi-connector examples below.

Heads up on actions: the Edgemesh connector itself only reads. But when you ask Claude to send an email, post to Slack, or create a task using our other connectors, it will draft it and ask you to confirm before anything goes out. Nothing is sent without your OK.

22 example prompts — from quick checks to full reports

Copy these, tweak them, make them yours. They get more advanced as you go down. The label shows the level, and the line under each shows which connectors get involved.

Simple one quick answer Analysis Edgemesh does the digging Multi-connector combines tools Takes action drafts an email / Slack / task (you confirm)

Site speed & performance

Simple
"Using Edgemesh, what's our average page-load time across the whole site over the last 30 days?"
Edgemesh — performance
Analysis
"Using Edgemesh, show me our 10 slowest pages by load time over the last 30 days, with how many visits each one gets."
Edgemesh — slowest pages
Analysis
"Using Edgemesh, break down LCP (largest contentful paint) by device — mobile vs. desktop vs. tablet — for the last 30 days."
Edgemesh — LCP by device
Analysis
"Using Edgemesh, which page templates (product, collection, cart, home) are slowest, and is performance worse on mobile?"
Edgemesh — by template
Analysis
"Using Edgemesh, compare site-speed metrics (TTFB, FCP, LCP) by country for our top 5 markets."
Edgemesh — performance by country
Analysis
"Using Edgemesh, run a site-speed audit for the last 30 days: Core Web Vitals overall, plus the worst pages and devices to fix first."
Edgemesh — speed audit
🛒

Conversion funnel

Simple
"Using Edgemesh, what's our overall site conversion rate for the last 30 days?"
Edgemesh — conversion
Analysis
"Using Edgemesh, walk me through the funnel for the last 30 days — sessions → product views → cart → checkout → purchase — and show where the biggest drop-off is."
Edgemesh — funnel drop-off
Analysis
"Using Edgemesh, what's our cart-to-checkout completion rate, and how has it trended over the last 90 days?"
Edgemesh — cart → checkout
Analysis
"Using Edgemesh, compare conversion rate and revenue-per-user for new vs. returning visitors over the last 30 days."
Edgemesh — new vs. returning
Analysis
"Using Edgemesh, break down conversion rate by device for the last 30 days — where are we losing the most mobile shoppers?"
Edgemesh — conversion by device
Analysis
"Using Edgemesh, show conversion rate and sessions by country for our top 8 markets."
Edgemesh — conversion by country
🎯

Traffic sources & attribution

Analysis
"Using Edgemesh, which traffic sources (referrers) drive the most sessions, and which actually convert best?"
Edgemesh — attribution by source
Analysis
"Using Edgemesh, break down sessions and conversion rate by UTM campaign for the last 30 days, best converters first."
Edgemesh — attribution by UTM
Analysis
"Using Edgemesh, which dimensions and metrics are available so I know what I can slice by?"
Edgemesh — dimensions / metrics list
🔗

Cross-system analysis & reports

Multi-connector
"Compare our site-speed trend in Edgemesh with daily sales from Shopify over the last 30 days — did slow days line up with lower revenue?"
Edgemesh + Shopify — speed vs. sales
Multi-connector
"Cross-reference the funnel: pull conversion-rate-by-source from Edgemesh and creator-driven traffic from ShopMy, and tell me whether influencer traffic converts better than average."
Edgemesh + ShopMy — funnel vs. creator traffic
Multi-connector
"Using Edgemesh conversion and Shopify revenue, estimate how much we'd gain if mobile converted at the same rate as desktop."
Edgemesh + Shopify — opportunity sizing
Takes action
"Each Monday, using Edgemesh, summarize last week's site speed (Core Web Vitals) and conversion funnel, and post a tidy draft to our #marketing Slack channel for me to review."
Edgemesh + Slack — weekly draft (you confirm)
Takes action
"Using Edgemesh, watch our conversion rate: if it drops more than 15% vs. the prior 7-day average, draft an alert to #marketing in Slack with the likely culprit (speed or funnel step)."
Edgemesh + Slack — conversion-drop alert (you confirm)
Takes action
"Build a monthly site-health report from Edgemesh — Core Web Vitals, the conversion funnel, new-vs-returning, and top converting sources — as a PDF, and draft an email to the leadership list with a 3-bullet summary."
Edgemesh + PDF + Gmail — drafts email (you confirm)
📊

Live artifacts, dashboards & spreadsheets

Analysis
“Create a live artifact: a site pulse dashboard — sessions, conversion and cache hit rate, refreshed each open.”
Edgemesh — live artifact
Analysis
“Build a campaign-day traffic board artifact: hourly sessions vs the same day last week.”
Edgemesh — campaign
Analysis
“Make a spreadsheet (.xlsx) of the last 90 days of traffic and conversion for marketing.”
Edgemesh — xlsx
Analysis
“Build a web-vitals watch artifact — LCP and CLS trends with red/green thresholds.”
Edgemesh — performance
Multi-connector
“Create one artifact joining Edgemesh and Klaviyo: send-day traffic lift per campaign.”
Edgemesh + Klaviyo

Limitations, caveats & risk (please read)

TopicWhat to knowStatus
Read-onlyThe connector cannot change anything — not the site, the tags, or the data. It only reports on what already happened. It's safe to explore freely.Safe
Who can sign inAccess requires a login on Melinda Maria’s Edgemesh account — only teammates invited to our Edgemesh workspace can connect. Enforced by Edgemesh’s OAuth on every login.Locked down
Needs the right scopesTo return data, Edgemesh must grant the connector read permissions — insights:performance:read and insights:conversion:read (plus feature grants). If a lens (speed or funnel) ever comes back empty, a missing scope is the likely cause — tell David.Scope-gated
Not real-time-to-the-secondAnalytics are aggregated, so very recent activity (the last few minutes/hours) may not be fully reflected yet. For "right now" totals use our order systems; Edgemesh is best for trends and patterns over days/weeks.By design
It's aggregate web analyticsEdgemesh reports patterns across many visitors — it does not identify individual customers by name. Numbers can be estimated/sampled at very fine slices, so for a high-stakes figure, sanity-check or widen the window.Verify fine slices
Confidential dataSite performance and conversion numbers are company data. Don't paste exports into outside tools, and share reports only with people who should see them.Handle with care

Get help, request features, or report something odd

Something looks wrong?

If a number seems off, a prompt errors out, or a lens comes back empty (often a missing scope) — tell David. Include what you asked and what you got back (a screenshot helps). Anomalies are worth flagging early.

Want a new capability or report?

Need a recurring site-health report, a new breakdown, or a specific funnel view? Send the idea to David. Many things are quick to add — the connector is built to grow.

A handy built-in you can always run: auth_whoami (confirms you're signed in and the connector is reaching Edgemesh). If it ever fails, that's the thing to send David.

What is a live artifact and how to share it

Short version: a live artifact is a page Claude builds once and then refreshes every single time you open it — so a dashboard you ask for today is still accurate next month. Here is what one is, and the three ways to get it in front of your team.

📊 NEW — build live artifacts, dashboards & spreadsheets with this connector

A live artifact is a small interactive page Claude builds and saves for you — a dashboard, tracker, or report that pulls fresh data from this connector every time you open it, instead of being a frozen snapshot. In a Cowork session, just ask: “create a live artifact that…” — it lands in your Artifacts list, reusable forever, and its charts and tables refresh themselves on open.

Sharing with the team: artifacts are saved to your Claude account. Three easy ways to share: (1) ask Claude to export a snapshot (PDF, image, or .xlsx) and drop it in Slack; (2) send a teammate the prompt that built it — their copy fills with live data through their own connector sign-in; (3) for a permanent all-team dashboard, that’s the MM Intelligence project on the AI roadmap.

How it works — architecture

Here's the actual build, for anyone who's curious how the answers get to you. You don't need any of this to use the connector — but it shows what's running under the hood (and why it's safe).

Edgemesh MCP Connector — Architecture Edgemesh connector architecture: Edgemesh's own hosted, read-only MCP server answering live queries from the Edgemesh Insights API for site-performance (Core Web Vitals) and conversion-funnel analytics on melindamaria.com. No database. Edgemesh MCP Connector — Architecture (live)Live site-performance + conversion analytics · hosted by Edgemesh · ~10 read-only tools · domain www.melindamaria.comLIVEYou + the teamin Claude (Cowork,Desktop, Web, Code)ask in plain Englishplain EnglishClaudepicks the rightedgemesh_ tool &fills in filtersMCP · OAuth 2.1Edgemesh MCP — hosted by EdgemeshREAD-ONLY🔐 Edgemesh OAuth sign-inyou sign in to MM’s Edgemesh account — no keys to paste~10 named read-only toolsperformance_query/analyze · conversion_query/analyzedimensions/metrics lists · attribution · whoami/domains🔑 Your Edgemesh login sessionheld by Edgemesh — never in Claude, never shown to you💾 No database — live & freshKV holds only login sessions + a short read cache.LIVE READtokenEdgemesh Insights APIperformance + conversionneeds insights:performance:read + insights:conversion:read scopesPlain-English answerreal-user speed & funnel data —always current — no stored copy.You / sourceEdgemesh MCPlive readFlow1. Ask in plain English → 2. Claude picks a tool → 3. Edgemesh checks your sign-in →4. runs a live read against Edgemesh with the stored token → 5. answer back. Nothing stored.
Hosted by Edgemesh themselves at mcp.edgemesh.com/mcp — unlike most of our custom connectors, this one runs on Edgemesh’s infrastructure and you sign in through Edgemesh’s own secure login (OAuth). Our live status page still watches it 24/7 with an authenticated probe every 5 minutes. All traffic over HTTPS/TLS.

Two lenses — speed & conversion

Edgemesh measures both halves of "is the site working for shoppers?": performance (how fast it loads for real visitors) and conversion (how many of them actually buy). Claude can use either lens — or combine them — to explain what's happening.

Live, read-only

It's a pure pass-through: every question runs live against the Edgemesh Insights API and comes straight back. There's no database, nothing is stored, and there are zero write tools — the connector can't change the site or the data.

Scoped access

The connector needs Edgemesh to grant it the right read permissions — insights:performance:read and insights:conversion:read (plus the matching feature grants). Those scopes are what let Claude pull both lenses; without them, a lens simply returns nothing.

How your data flows (the 30-second version)

You don't need to understand the plumbing to use it — but here's the simple picture. It's a live pass-through: every question goes straight to the Edgemesh Insights service and comes back fresh.

When you ask a speed question

e.g. "Which pages are slowest on mobile?" → Claude calls a performance insights tool and reports real-user load times, sliceable by page, device, country, or date.

When you ask a funnel question

e.g. "Where do shoppers drop off before checkout?" → Claude calls a conversion insights tool and walks the funnel from sessions to purchase, with the drop-off at each step.

Everything happens behind a secure sign-in. The connector only works for people signing in with a @melindamaria.com or @7ate9.com Google account. The data is aggregate site analytics (no customer names) — still company data, so treat anything you export as confidential.
Melinda Maria · Edgemesh Connector Team Guide · v0.1.0 · June 26, 2026 · read-only · hosted by Edgemesh · sign in through Edgemesh’s login.
Performance + conversion analytics for melindamaria.com. Questions, anomalies, and feature requests → David. · ← Back to all connectors
Turning Data Into a Competitive Advantage. Know what's slow, see where shoppers leave, fix what matters.