Skip to main content
Glama
hyoon2007

mpulse-mcp

by hyoon2007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MPULSE_API_TOKENYesYour pre-issued mPulse API token (mPulse -> your name -> Account -> Generate/Revoke API Token).
MPULSE_APPS_CONFIGNoPath to the mPulse apps registry JSON file. Defaults to ./mpulse_apps.json../mpulse_apps.json
MPULSE_API_TOKEN_APP_BNoOverride API token for app-b if configured with a different api_token_env.

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_summaryA

Aggregate summary stats for one timer (median, margin-of-error, count, p95, p98).

mPulse query-type: summary. Data is per-minute aggregated over a single calendar day in the given timezone (default UTC).

Time selection (exactly one required):

  • date — a single calendar day, YYYY-MM-DD.

  • date_comparator — a relative window, e.g. Last24Hours, LastHour. A date range is not supported per call; split it into per-day calls.

Timer: timer (built-in, default PageLoad) OR custom_timer (a custom timer name). percentile is 1–99 (default 50).

Drilldowns filter the data (e.g. page_group, browser, country, device_type, ab_test). Unsupported combinations return empty data with a note rather than an error.

Set raw=True to get mPulse's untouched JSON. Numeric values are never rounded or summarized.

get_histogramA

Distribution (histogram buckets) for one timer over the period.

mPulse query-type: histogram. Returns per-bucket counts plus median/p95/ p98. Time selection and drilldowns behave exactly as in get_summary (single calendar day OR relative date_comparator).

Use raw=True for untouched mPulse JSON. Bucket counts are preserved losslessly.

get_timersA

A single timer's value by minute over time (time series).

mPulse query-type: by-minute. Best for one timer (built-in timer, default PageLoad, or a custom_timer). For multiple timers/metrics at once, use get_metrics (query-type timers-metrics).

Returns a series of {x, y} points at per-minute resolution for the selected calendar day (or date_comparator window). Values are preserved exactly.

get_metricsA

Multiple timers/metrics by minute over time.

mPulse query-type: timers-metrics. metric defaults to Beacons, timer to PageLoad. Returns values:[{id, history:[...per-minute...], latest}] plus the data timezone.

Time selection and drilldowns behave as in the other tools (single calendar day OR relative date_comparator). Numbers are preserved losslessly.

queryA

Call an arbitrary mPulse query-type with arbitrary parameters.

Use this for query-types not covered by the explicit tools (see list_query_types), e.g. dimension-values, geography, page-groups, app-error-summary.

params is a dict of mPulse wire parameter names (hyphenated), e.g. {"date-comparator": "Last24Hours", "page-group": "Home", "timer": "PageLoad"}. format=json is added automatically. Remember the one- calendar-day-per-query constraint.

raw=True returns mPulse's untouched JSON.

list_appsA

List registered mPulse apps and the default app.

Use this before other tools so you reference real app names. The app argument on every tool is optional and falls back to the default.

list_query_typesA

List the mPulse query-types this server knows about, with one-line summaries.

The explicit tools cover: summary→get_summary, histogram→get_histogram, by-minute→get_timers, timers-metrics→get_metrics. Everything else is reachable via the generic query tool.

describe_queryA

Describe a query-type: parameters, drilldowns, response shape, and caveats.

Pass a slug from list_query_types (e.g. summary, timers-metrics, geography).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 8 tools

Disambiguation5/5

Each tool has a clear, distinct role: summary/histogram/time-series/metrics cover different data shapes, query is explicitly for uncovered query-types, and list_apps/list_query_types/describe_query are discovery aids. No two tools appear interchangeable.

Naming Consistency5/5

Tool names follow a predictable verb_noun pattern: get_* for data retrieval, list_* for enumeration, describe_* for details, and a single 'query' for generic access. The style is uniform and intuitive.

Tool Count5/5

Eight tools is well-scoped for an analytics server: four query-specific getters, one generic fallback, and three utility/metadata tools. Each tool earns its place without redundancy or bloat.

Completeness5/5

The server covers the core mPulse analytics surface (summary, histogram, time series) and provides a generic query tool for any undiscovered query-type, plus list/describe tools for self-discovery. No obvious gaps; agents can handle arbitrary query-types without dead ends.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources