KrystalView Analytics

io.github.McSlainePublished by GitHub account McSlainev0.1.2Updated Oct 24, 2026

AI agent access to website analytics, session replay, and anomaly detection.

VerifiedSTDIODesktop onlyProductivity & WorkflowData & Analytics

Overview

AI-generated overview

Lets an assistant query KrystalView website analytics, visitor sessions, funnels, campaigns, errors, and anomaly alerts.

What you can do
Connects an AI assistant to KrystalView website analytics. Read-only tools cover visitor sessions and session detail, site statistics, scroll depth, live visitors, AI-detected anomalies, conversion funnels and step-by-step drop-off, UTM campaign summaries, sessions and ROAS, aggregated browser errors, and notifications. It runs either as a hosted remote MCP endpoint or as a local stdio package that proxies to the KrystalView API.
When to use it
Useful when you want to ask an assistant about site performance, traffic changes, funnel drop-off, campaign results, or UX friction without opening the KrystalView dashboard. Suited to teams already using KrystalView for analytics and session replay.
Requirements
A KrystalView account and an API key generated in the console under Settings > API Keys, supplied as KRYSTALVIEW_API_KEY. The local option needs Python and the krystalview-mcp package; the hosted option needs a client that supports remote MCP with OAuth. Optional KRYSTALVIEW_BASE_URL and KRYSTALVIEW_TIMEOUT. Network access to the KrystalView API.
Before you install
Requires the secret KRYSTALVIEW_API_KEY, which is scoped to a single site; keys can be rotated or revoked in the console. Tools are read-only, but they expose visitor session, campaign, and error data to the assistant and its provider. The hosted endpoint also accepts a read API key via the Authorization or X-API-Key header. Default rate limit is 60 requests per minute.

Installation

In SourceWeft

  1. Open KrystalView Analytics in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

KrystalView MCP Server

Give your AI agents direct access to website analytics. Query visitor sessions, investigate UX friction, analyze conversion funnels, review campaigns and errors, and get anomaly alerts — all from Claude, Cursor, or any MCP-compatible client.

Connection Options

Hosted Remote MCP

Use this when your client supports remote MCP servers or connector-style OAuth. No local package install is required.

FieldValue
Endpointhttps://krystalview.com/mcp
Transportstreamable-http
AuthenticationOAuth authorization code + PKCE
OAuth metadatahttps://krystalview.com/.well-known/oauth-authorization-server
Protected resource metadatahttps://krystalview.com/.well-known/oauth-protected-resource

During OAuth, KrystalView asks the signed-in user to choose the site the MCP client can read. The issued token is read-only and scoped to that site. The hosted OAuth server supports dynamic client registration, authorization code + PKCE, resource indicators, refresh-token rotation, and token revocation.

For clients that support custom headers instead of OAuth, the hosted endpoint also accepts a KrystalView read API key as either:

http
Authorization: Bearer kv_live_...

or:

http
X-API-Key: kv_live_...

Local stdio MCP Package

Use this when your MCP client runs local stdio servers, such as Claude Desktop, Claude Code, Cursor, or similar developer tools.

Install

bash
pip install krystalview-mcp

Configure

Generate an API key in your KrystalView console under Settings > API Keys.

Claude Desktop

Add to your claude_desktop_config.json:

json
{  "mcpServers": {    "krystalview": {      "command": "krystalview-mcp",      "env": {        "KRYSTALVIEW_API_KEY": "your-api-key-here"      }    }  }}
Claude Code
bash
claude mcp add krystalview -- krystalview-mcp# Then set your API key:export KRYSTALVIEW_API_KEY="your-api-key-here"
Cursor

Add to your MCP settings:

json
{  "krystalview": {    "command": "krystalview-mcp",    "env": {      "KRYSTALVIEW_API_KEY": "your-api-key-here"    }  }}

Available Tools

ToolDescription
get_sessionsList/search visitor sessions with filters (device, location, friction, rage clicks)
get_session_detailDeep dive into a specific session — full timeline, events, navigation path
get_site_statsAggregate performance metrics — sessions, friction, devices, top pages
get_scroll_depthScroll-depth buckets for a specific page path
get_live_visitorsCurrently active visitor count and recent live sessions
get_anomaliesAI-detected anomalies with explanations (traffic spikes/drops, friction surges)
get_funnelsList defined conversion funnels
get_funnel_analysisStep-by-step funnel conversion rates and drop-off analysis
get_campaign_summaryUTM campaign attribution summary
get_campaign_sessionsVisitor sessions from a specific campaign
get_campaign_roasPaid campaign spend, conversions, and ROAS where connected
get_errorsAggregated client-side browser errors
get_notificationsRecent KrystalView notifications and insights

Example Prompts

Once connected, try asking your AI assistant:

  • "How's my site performing this week?"
  • "Show me frustrated mobile users from the last 24 hours"
  • "Why did our traffic drop yesterday?"
  • "Where are users dropping off in the checkout funnel?"
  • "Find sessions with rage clicks on the pricing page"
  • "Which campaigns are driving the most high-friction sessions?"
  • "Show me unresolved browser errors with sample session IDs"
  • "Are there any anomalies I should know about?"

Environment Variables

VariableRequiredDefaultDescription
KRYSTALVIEW_API_KEYYes—Your KrystalView API key
KRYSTALVIEW_BASE_URLNohttps://krystalview.com/apiAPI base URL
KRYSTALVIEW_TIMEOUTNo15Request timeout in seconds

Rate Limits

API keys have configurable rate limits (default: 60 requests per minute). Rate limit headers are included in every response. If you hit the limit, the server returns a clear error with retry timing.

Security

  • API keys are scoped to a single site — agents can only access data for the site the key was created for
  • OAuth tokens issued by the hosted MCP endpoint are read-only and scoped to the selected site
  • Hosted OAuth supports refresh-token rotation and token revocation
  • Browser-originating MCP/OAuth requests are checked against explicit trusted origins
  • Tools are read-only
  • All requests use HTTPS
  • Keys can be rotated or revoked in the KrystalView console
  • The local stdio package stores no data — it proxies directly to the KrystalView API

License

MIT

Source: README.md at commit f4df256

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts