Skip to main content
Glama
nks-hub

rybbit-mcp

by nks-hub

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RYBBIT_URLYesURL pointing to your Rybbit instance.
RYBBIT_EMAILNoEmail for authentication (Development/testing)
RYBBIT_API_KEYNoAPI key for authentication (Recommended for production)
RYBBIT_PASSWORDNoPassword for authentication (Development/testing)

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": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
rybbit_get_configA

Get Rybbit server version and configuration

rybbit_list_sitesA

List all sites and organizations the authenticated user has access to

rybbit_create_siteA

Create a new site in Rybbit. Use type 'web' for websites (domain like 'example.com') or type 'mobile' for mobile apps (package name like 'com.example.app'). 'app' is accepted as a legacy alias for 'mobile'. Returns the created site with its siteId for tracking integration.

rybbit_get_site_idA

Look up a site by domain name. Returns the numeric siteId used for analytics API queries. Note: for SDK tracking setup, use the hash siteId returned by rybbit_create_site instead.

rybbit_update_site_configB

Update configuration for an existing Rybbit site. Change site identity (name, domain, type), toggle tracking features (IP, session replay, errors, button clicks, etc.), manage exclusions (IPs, countries, paths, hostnames, user agents), and public embedding.

rybbit_delete_siteA

Delete a site from Rybbit. This permanently removes the site and its replay data. Use rybbit_list_sites or rybbit_get_site_id to find site IDs.

rybbit_site_has_dataA

Check whether a site has received any tracking events yet. Useful for verifying SDK integration before drilling into analytics.

rybbit_get_page_titlesA

Get the most-viewed page titles for a site, broken down by pageviews and unique sessions. Complements rybbit_get_metric with parameter='pathname' by giving the human-readable page title instead of just the path.

rybbit_live_usersA

Get the current number of live/active users on a site in real-time

rybbit_get_overviewB

Get aggregated overview metrics for a site: sessions, pageviews, unique users, pages per session, bounce rate, and average session duration. Supports date range and filters.

rybbit_get_overview_timeseriesB

Get overview metrics as time-series data with configurable time buckets (minute, hour, day, week, month). Returns arrays of data points for charting trends.

rybbit_get_session_locationsA

Get geographic session location data with coordinates. Returns latitude, longitude, city, country, and session count for map visualization and geographic analysis.

rybbit_get_metricA

Get metric breakdown by dimension. Use parameter='pathname' for top pages, 'browser'/'operating_system'/'device_type' for tech stats, 'country'/'city' for geo, 'utm_source'/'utm_campaign' for marketing, 'referrer'/'channel' for traffic sources, 'entry_page'/'exit_page' for user flow. Returns sorted list with counts, percentages, bounce rate, and session duration.

rybbit_get_retentionB

Get user retention cohort analysis showing how many users return over time periods.

rybbit_list_sessionsA

List sessions for a site with filtering and pagination. Returns session ID, user info, device, location, pages visited, duration, bounce status, and IP address (if site has trackIp enabled). Supports client-side IP filtering.

rybbit_get_sessionA

Get detailed session information including all page views, events, user traits, device info, location, and full event timeline. Use rybbit_list_sessions first to find session IDs.

rybbit_list_usersA

List users for a site. Returns user IDs, session counts, first/last seen dates, and user traits. Supports filtering by most analytics dimensions. Use 'search' param to find users by username/email/name (case-insensitive partial match). IMPORTANT: event_name filter is silently STRIPPED here — upstream backend returns HTTP 500. To rank users by a specific event, use rybbit_get_event_user_leaderboard instead. Call rybbit_describe_dimension to see capability per filter dimension.

rybbit_get_userB

Get detailed information about a specific user including their traits, session history, and activity summary.

rybbit_get_user_traitsA

Get user trait keys, values, or find users by trait. mode='keys' lists all trait keys. mode='values' (default when key is provided) returns distinct values for a trait key. mode='users' finds users matching a specific trait key+value pair (case-insensitive).

rybbit_get_user_event_breakdownA

Get event count breakdown for a specific user. Shows how many times each event_name was triggered by this user. Accepts either the Rybbit user_id (device hash) or the identified_user_id (app-provided user ID). Useful for analyzing per-user behavior like ad_click, chat_message_sent, etc.

rybbit_get_user_session_countA

Get the per-day session count for a single user across the requested time range. Useful for plotting user engagement intensity (calendar heatmap or sparkline).

rybbit_list_eventsA

List raw events for a site with filtering and pagination. Returns individual event records with timestamps, types, pathnames, event names, and properties. When filtering by event_name, only matching events are returned (not entire sessions). Use beforeTimestamp from a previous response's cursor.oldestTimestamp to paginate backwards through history.

rybbit_get_event_aggregateA

Aggregate events by one or more dimensions (e.g. identified_user_id, traits.username, pathname, properties.room_id). Filters by event_name and optional property filters, then groups remaining events. Returns { groups: [{key, count, first_seen, last_seen, sessions, extras}], scanned, hitCount, hasMore }. When hasMore: true, the scan was capped — narrow the time window or raise maxScan for more accuracy.

rybbit_get_event_user_leaderboardA

Returns the top users for a given event (e.g. who sent the most pm_sent, who clicked the most ad_click). Groups by identified_user_id + traits.username. Answers questions like 'kdo dnes poslal nejvíc vzkazů'.

rybbit_get_event_namesA

Get all custom event names and their occurrence counts for a site. Useful for discovering what events are being tracked.

rybbit_get_event_propertiesB

Get property breakdowns for a specific custom event. Returns the distinct property keys and values with counts.

rybbit_get_event_timeseriesB

Get custom event counts as time-series data with configurable buckets. Useful for analyzing event trends over time.

rybbit_get_outbound_linksB

Get outbound link clicks tracked on the site. Shows which external URLs users are clicking and how often.

rybbit_get_errorsA

Get error tracking data. Workflow: (1) type='names' to see error types and counts, (2) type='events' with errorMessage to see individual instances with stack traces, (3) type='timeseries' with errorMessage to see trends over time.

rybbit_get_performanceA

Get Core Web Vitals performance metrics (LCP, CLS, INP, FCP, TTFB) with p50, p75, p90, p99 percentiles. Optionally break down by page path, browser, or OS.

rybbit_get_performance_timeseriesA

Get Core Web Vitals performance metrics as time-series data for trend analysis.

rybbit_list_funnelsA

List all saved funnels for a site with their step definitions.

rybbit_analyze_funnelB

Analyze a custom funnel by defining steps (page visits or events). Returns visitor counts and drop-off rates at each step.

rybbit_get_funnel_step_sessionsA

Get the sessions that reached (or dropped off at) a specific funnel step. Useful for drilling into why users drop off at a particular funnel step.

rybbit_create_funnelA

Save a new named funnel definition. Steps are evaluated in order. Pass an existing funnel report ID to overwrite that funnel instead of creating a new one.

rybbit_delete_funnelB

Permanently delete a saved funnel. This action cannot be undone.

rybbit_list_goalsB

List all goals for a site with their current conversion metrics and configuration.

rybbit_get_goal_sessionsA

Get sessions that completed a specific goal. Useful for analyzing which users and sessions triggered goal conversions.

rybbit_create_goalB

Create a new conversion goal for a site. Goal can be path-based (URL match) or event-based (custom event triggered).

rybbit_update_goalC

Update an existing goal's name, type, or configuration.

rybbit_delete_goalB

Permanently delete a goal. This action cannot be undone.

rybbit_get_journeysB

Get user journey (flow) analysis showing the most common navigation paths through the site. Shows sequences of pages users visit and how many sessions follow each path.

rybbit_describe_dimensionA

Look up which tools accept a given filter dimension (e.g. 'event_name', 'pathname', 'country'), where it works natively, where it is silently stripped due to upstream bugs (with alternative tool suggestions), and example values. Use this before constructing a complex filters[] array.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 43 tools

Disambiguation4/5

Most tools target a clearly distinct resource and action, and descriptions explicitly clarify overlaps like rybbit_get_metric vs rybbit_get_page_titles or rybbit_get_event_aggregate vs rybbit_get_event_user_leaderboard. A few event- and user-oriented tools could still be confused at a glance, but the set is generally well separated.

Naming Consistency4/5

All tools use the rybbit_ prefix with snake_case naming, and most follow a clear verb_noun pattern such as rybbit_list_users, rybbit_get_event_properties, and rybbit_create_funnel. Minor deviations like rybbit_site_has_data and rybbit_live_users are descriptive but not strictly verb_noun.

Tool Count2/5

With 43 tools, the server is far above the 15-tool comfortable range for an MCP tool set. While the analytics domain is broad, many separate query endpoints could likely be consolidated or grouped, making this feel heavy for routine agent use.

Completeness4/5

The surface covers core analytics workflows well: site management, sessions, users, events, goals, funnels, performance, errors, and configuration. Some peripheral capabilities like annotations, dashboards, alerting, or user administration are absent, but the primary analytics lifecycle is substantially covered.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive