Gauge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GAUGE_CONFIG | No | Path to the optional config file. Defaults to ~/.config/gauge/config.toml. | |
| GAUGE_UMAMI_URL | No | Your Umami address, e.g. https://analytics.example.com. Defaults to Umami Cloud when GAUGE_UMAMI_API_KEY is set. | |
| GAUGE_RESEND_FROM | No | Sender address on a domain verified in Resend. | |
| GAUGE_UMAMI_API_KEY | No | Umami Cloud API key, used instead of a username/password login. | |
| GAUGE_UMAMI_ENABLED | No | Set to false to turn the umami module off. | |
| GAUGE_RESEND_API_KEY | No | Resend API key. | |
| GAUGE_RESEND_ENABLED | No | Set to false to turn the resend module off. | |
| GAUGE_UMAMI_PASSWORD | No | Password for the self-hosted Umami login. A view-only user is enough. | |
| GAUGE_UMAMI_USERNAME | No | A self-hosted Umami login. A view-only user is enough. | |
| GAUGE_RESEND_FROM_NAME | No | Optional sender display name. | |
| GAUGE_RESEND_REQUIRE_CONFIRM | No | true by default: you approve each send. false lets the assistant send on its own. | true |
| GAUGE_RESEND_ALLOWED_RECIPIENTS | No | Optional comma-separated addresses or @domains the assistant may send to without asking each time, e.g. me@example.com,@example.com. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| umami_websitesB | List websites tracked in Umami. Paged: page starts at 1, page_size up to 100. |
| umami_statsC | Totals for one website. Range: last |
| umami_pageviewsC | Pageviews and sessions over time. unit: minute, hour, day, month or year. |
| umami_metricsC | Ranked breakdown, highest count first. type: path (top pages), referrer, entry, exit, title, country, region, city, browser, os, device, language, screen, event, utmSource, hostname. |
| resend_sendA | Send an email from the configured sender. Without confirm=true it only returns a preview. With confirm=true the person is asked to approve it (unless the recipients are pre-approved in settings); the assistant cannot approve on their behalf. |
| resend_emailsA | List sent emails, newest first. Page with after=<next_after from the previous page>. |
| resend_domainsA | List sending domains and whether each is verified. |
| gauge_modulesA | Which modules are on, what settings are missing, and what each tool does. Pass a module name for its full settings list. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analytics | When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For getting conversions into ad platforms (pixels, conversion tags, CAPI, server-side) and verifying they arrived, see conversion-tracking. For choosing attribution models, comparing multi-touch/MMM/incrementality, or reconciling conflicting numbers across tools, see attribution. For A/B test measurement, see ab-testing. Rate metrics divide matching closed windows — never full-period spend by partial-period results. |
| copywriting | When the user wants to write, rewrite, or improve marketing copy for any page, including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "hero section copy," "this copy is weak," "this sounds like AI," "AI slop," "make it sound human," or "help me describe my product." Drafts never use AI tells like "it's not X, it's Y" reveals, "no X, no Y, no Z" lists, or sentences that trail into extra comma clauses. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing. For the offer underneath the copy (bonuses, guarantees, value framing), see offers. Claims must be supportable, and a declined claim names the evidence that would unlock it. Diagnoses the input first (blank brief, real voice, or point edit) and changes only what it calls for. |
| email-best-practices | Use when building email features, emails going to spam, high bounce rates, setting up SPF/DKIM/DMARC authentication, implementing email capture, ensuring compliance (CAN-SPAM, GDPR, CASL), handling webhooks, retry logic, making emails accessible (alt text, headings, contrast, screen readers), or deciding transactional vs marketing. |
| emails | When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. Emails avoid AI tells like 'it's not X, it's Y' reveals, 'no X, no Y, no Z' lists, and fake 'Re:' subject lines. For cold outreach and outbound sequences, see cold-email. For in-app onboarding, see onboarding. |
| getting-started | Set up and check the Gauge MCP bundle (Umami analytics and Resend email). Use when the user installs Gauge, asks what Gauge can do, gets a "not_configured" or "auth_failed" error from a gauge tool, or wants to turn the analytics or email part on or off. |
| react-email | Use when building HTML email templates with React components, adding a visual email editor to an application using the React Email visual editor, rendering emails to HTML, or sending emails with Resend. Covers welcome emails, password resets, notifications, order confirmations, newsletters, transactional emails, and the embeddable email editor component. |
| resend | Use when working with the Resend email API — sending transactional emails (single or batch), receiving inbound emails via webhooks, managing email templates, tracking delivery events, managing domains, contacts, broadcasts, webhooks, API keys, inboxes (threads, labels, drafts, replies), automations, events, viewing API request logs, checking account usage and quotas, or setting up the Resend SDK. Always use this skill when the user mentions Resend, even for simple tasks like "send an email with Resend" — the skill contains critical gotchas (idempotency keys, webhook verification, template variable syntax) that prevent common production issues. |
| seo-audit | When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo. |
| weekly-site-report | Write a short weekly traffic report for a website from Umami data, using the Gauge tools. Use when the user asks how their site did this week or last week, wants a traffic summary, top pages, where visitors came from, or a report to email to themselves or a client. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| analytics/SKILL.md | |
| analytics/references/event-library.md | |
| analytics/references/ga4-implementation.md | |
| analytics/references/gtm-implementation.md | |
| copywriting/SKILL.md | |
| copywriting/references/ai-tells.md | |
| copywriting/references/copy-frameworks.md | |
| copywriting/references/natural-transitions.md | |
| email-best-practices/SKILL.md | |
| email-best-practices/references/accessibility.md | |
| email-best-practices/references/compliance.md | |
| email-best-practices/references/deliverability.md | |
| email-best-practices/references/email-capture.md | |
| email-best-practices/references/email-types.md | |
| email-best-practices/references/list-management.md | |
| email-best-practices/references/marketing-emails.md | |
| email-best-practices/references/sending-reliability.md | |
| email-best-practices/references/transactional-email-catalog.md | |
| email-best-practices/references/transactional-emails.md | |
| email-best-practices/references/webhooks-events.md | |
| emails/SKILL.md | |
| emails/references/copy-guidelines.md | |
| emails/references/email-types.md | |
| emails/references/sequence-templates.md | |
| getting-started/SKILL.md | |
| react-email/SKILL.md | |
| react-email/references/COMPONENTS.md | |
| react-email/references/EDITOR.md | |
| react-email/references/I18N.md | |
| react-email/references/PATTERNS.md | |
| react-email/references/SENDING.md | |
| react-email/references/STYLING.md | |
| resend/SKILL.md | |
| resend/references/api-keys.md | |
| resend/references/automations.md | |
| resend/references/broadcasts.md | |
| resend/references/contact-properties.md | |
| resend/references/contacts.md | |
| resend/references/domains.md | |
| resend/references/events.md | |
| resend/references/inboxes.md | |
| resend/references/installation.md | |
| resend/references/logs.md | |
| resend/references/receiving.md | |
| resend/references/segments.md | |
| resend/references/sending/batch-email-examples.md | |
| resend/references/sending/best-practices.md | |
| resend/references/sending/email-management.md | |
| resend/references/sending/overview.md | |
| resend/references/sending/single-email-examples.md | |
| resend/references/templates.md | |
| resend/references/topics.md | |
| resend/references/usage.md | |
| resend/references/webhooks.md | |
| seo-audit/SKILL.md | |
| seo-audit/references/ai-writing-detection.md | |
| seo-audit/references/international-seo.md | |
| seo-audit/references/local-seo-pages-and-measurement.md | |
| seo-audit/references/local-seo-profile-and-citations.md | |
| seo-audit/references/local-seo.md | |
| seo-audit/references/rankings-push.md | |
| seo-audit/references/title-tags.md | |
| weekly-site-report/SKILL.md |
TDQS
Scored across 8 tools
The Umami tools are mostly differentiated by resource and shape: websites lists sites, stats gives totals, pageviews gives time series, and metrics gives ranked breakdowns. Stats and pageviews both concern analytics and could be slightly confused, but descriptions clarify the distinction; Resend and module tools are clearly separate.
All tool names consistently follow a module_resource pattern in snake_case: umami_*, resend_*, and gauge_modules. The convention is predictable and readable throughout.
Eight tools is well-scoped for a server combining Umami analytics reads with Resend email operations. Each tool covers a distinct capability without obvious redundancy.
The surface covers core analytics reading (sites, totals, time series, breakdowns) and email sending/listing/domain listing. Minor gaps exist, such as retrieving a single sent email's details or managing/verifying domains, but agents can work around these.