Skip to main content
Glama

Server Details

Ask your AI about your product's events, delivery health and usage

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
Repository
mytinyrocket/eventsend-claude-plugin
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 9 tools

Disambiguation4/5

The tools split cleanly into org/config, usage, analytics, and event retrieval, with each tool having a distinct primary purpose. However, search_events and get_user_timeline both retrieve events for a customer user, and event_stats vs list_event_names both report event counts/names over a range, creating minor selection ambiguity.

Naming Consistency4/5

Most tools follow a verb_noun pattern (get_event, list_organizations, search_events, describe_setup), but delivery_health and event_stats are noun-first. All names use snake_case and remain readable, but the set is not fully uniform.

Tool Count5/5

Nine tools is well-scoped for a read-only event analytics server. Each tool covers a distinct capability, and there is no obvious redundancy or bloat.

Completeness4/5

The surface covers organizations, configuration, usage, event names, event stats, event search, user timelines, individual events, and delivery health. Minor gaps include no write/management operations and list_event_names returning only frequent names rather than an exhaustive list, but these are small for a query-focused toolset.

Publisher details

Operator
My Tiny Rocket LLC
Operator website
https://mytinyrocket.com
Vendor relationship
Not applicable
Privacy policy
Not provided
Trust center
Not available
Restrictions
Not available

Available Tools

9 tools
delivery_healthDelivery healthA
Read-onlyIdempotent
Inspect

Delivery health per destination (Slack, Discord, webhooks, …) over a range of calendar days — delivered, failed, success rate, response time, what was held back — plus the most recent failed deliveries with their errors. Totals come from daily aggregates; failures from raw deliveries within retention.

Inputs: to, org, days, from, +4 more.

describe_setupDescribe setupA
Read-onlyIdempotent
Inspect

The organization's configuration: routes (where events arrive), sources (Stripe, GitHub, Vercel connectors), topics (routing rules) and destinations (Slack, Discord, Telegram, webhooks, push) with their ids and names. Call it before filtering another tool by route, source or destination.

Inputs: org.

event_statsEvent statisticsA
Read-onlyIdempotent
Inspect

Event counts over a range of calendar days — per day, per level, in total, and against the previous period — for the whole organization or one event name. From daily aggregates (12 months on every plan). Dates only, in the organization's time zone.

Inputs: to, org, days, from, +1 more.

get_eventGet eventA
Read-onlyIdempotent
Inspect

Fetches one event by id with its full payload and a page of its delivery history (newest first; page with deliveries_cursor). Use it after search_events or get_user_timeline when the payload or every delivery attempt is needed.

Inputs: id (required), org, deliveries_limit, deliveries_cursor.

get_usageGet usageA
Read-onlyIdempotent
Inspect

The organization's event quota for the current billing period — used, limit, remaining, overage, a run-rate projection — and its plan and raw-event retention.

Inputs: org.

get_user_timelineGet customer timelineA
Read-onlyIdempotent
Inspect

The timeline of one customer: every raw event whose user_id matches any of the given identifiers, ordered by when it occurred (newest first), with a summary of the range on the first page. Bounded by the plan's retention. Page with next_cursor until exhausted is true.

Inputs: user_ids (required), org, limit, since, +2 more.

list_event_namesList event namesA
Read-onlyIdempotent
Inspect

The organization's most frequent event names over a range of calendar days, with counts and share, from daily aggregates (12 months on every plan). Use it to learn what an organization sends before searching or computing stats. Dates only, in the organization's time zone.

Inputs: to, org, days, from, +1 more.

list_organizationsList organizationsA
Read-onlyIdempotent
Inspect

Lists the organizations this credential can read, with the default one marked. Call it first when the user names an organization, or when another tool answers that no default is set, and then pass that organization's slug as org on every later call.

Inputs: no named parameters.

search_eventsSearch eventsA
Read-onlyIdempotent
Inspect

Searches the organization's recent raw events (newest first) by text, event name, level, delivery status, customer user_id, route, source and time, with each event's latest deliveries. Bounded by the plan's retention. Page with next_cursor until exhausted is true; a short page with a cursor means the search window ended, not the history.

Inputs: org, level, limit, since, +9 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Intelligence layer for AI that enables querying across revenue, errors, identity, and analytics layers in plain English, returning rendered charts and dashboards.
      11
      55 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI-powered analytics for OpenReplay user sessions through natural language queries. Supports session search, user journey analysis, error tracking, performance metrics, and funnel analysis to understand user behavior patterns.
      11
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible clients to query and act on a self-hosted product analytics platform, including analytics data, session replays, errors, feature flags, surveys, and SQL-based insights through natural-language tools.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.