KrystalView MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KRYSTALVIEW_API_KEY | Yes | Your KrystalView API key | |
| KRYSTALVIEW_TIMEOUT | No | Request timeout in seconds | 15 |
| KRYSTALVIEW_BASE_URL | No | API base URL | https://krystalview.com/api |
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 |
|---|---|
| get_sessionsA | List recent visitor sessions with filtering. Each session includes: duration, page count, entry/exit URLs, device info, screen size, IP address, location (country/city), friction score, and rage click count. Use this to find sessions matching specific criteria — e.g. frustrated mobile users, visitors from a specific country, or high-friction sessions. Args: query: Search entry/exit URLs (e.g. "/pricing", "/checkout") limit: Max results (1-100, default 20) offset: Pagination offset country: Filter by country name device_type: "mobile" or "desktop" min_friction: Minimum friction score (0-10) min_duration: Minimum session duration in seconds has_rage_clicks: Only sessions with rage clicks |
| get_session_detailA | Get full details for a specific session. Returns the complete session record including: all page visits with timestamps, event timeline, device/browser info, IP address, geographic location, friction breakdown, rage clicks, errors encountered, and navigation path. Use this to deep-dive into a specific session after finding it via get_sessions. Args: session_id: The session primary key (UUID) from get_sessions results |
| get_site_statsA | Get aggregate site statistics and performance metrics. Returns: total sessions, average duration, average friction score, bounce rate, rage click sessions, device breakdown (desktop/mobile), browser breakdown, top entry pages, top exit pages, daily session counts, and friction score distribution. Use this for an overview of site health and trends. Args: days: Lookback period in days (7-90, default 7) |
| get_anomaliesA | Get detected anomalies for the site. Anomalies are automatically detected when metrics deviate significantly from their 7-day rolling average (>2 standard deviations). Types include: traffic_spike, traffic_drop, friction_surge, and bounce_spike. Each anomaly includes: type, severity (warning/critical), metric name, expected vs actual values, deviation percentage, and an AI-generated explanation of what likely caused it. Args: limit: Max results (1-200, default 20) unacknowledged_only: Only show unacknowledged anomalies |
| get_funnelsA | List all conversion funnels defined for this site. Returns funnel definitions with their name, steps (URLs/patterns), and creation date. Use the funnel ID with get_funnel_analysis to see conversion rates and drop-off points. |
| get_funnel_analysisA | Analyze a conversion funnel — see where users drop off. Returns step-by-step conversion rates showing how many sessions reached each step, the conversion rate between steps, and the overall funnel completion rate. Use this to identify which step in a user flow (e.g. landing -> signup -> checkout -> payment) loses the most visitors. Args: funnel_id: Funnel ID from get_funnels results days: Lookback period in days (7-90, default 30) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct aspect of site analytics: anomalies, funnel definitions, funnel conversion analysis, session listing, session deep-dive, and aggregate stats. No two tools overlap in functionality.
All tool names follow a consistent 'get_<resource>' pattern with snake_case. Variations like 'get_funnel_analysis' and 'get_session_detail' extend logically without breaking the pattern.
With 6 tools covering anomalies, funnels, sessions, and site stats, the set is well-scoped for an analytics MCP server. Each tool serves a clear purpose without being overly granular or sparse.
The tool surface covers all major read-only analytics needs: listing and details for sessions, funnels, and anomalies plus aggregate stats. Minor gaps exist: no single anomaly detail view and no way to acknowledge anomalies, but the core workflows are supported.