# convalytics MCP server

Read-only analytics for Convex apps, queryable via MCP from Claude, Cursor, and other clients.

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-dan-cleary-convalytics
- Repository: https://github.com/Dan-Cleary/convalytics
- Website: https://convalytics.dev/mcp

## Install
- Endpoint: https://api.convalytics.dev/mcp
- Auth: Auth required by registry metadata

## Setup notes
- Remote header: Authorization (required; secret)
- The upstream registry signals required auth or secrets.
- Remote endpoint: https://api.convalytics.dev/mcp
- Header: Authorization

## Tools
- list_projects - List all Convalytics projects on the team this token belongs to. Useful when the agent needs to confirm the project it's querying against. No arguments. Endpoint: https://api.convalytics.dev/mcp
- get_usage - Return the current month's custom-event usage, monthly quota, retention days, and plan name for the team. Endpoint: https://api.convalytics.dev/mcp
- top_pages - Return the top pages for a specific project, ranked by views in a time window. Default window is the last 7 days. Use list_projects first if you don't know the project name. Returns path, views, uniqueVisitors, and percentage of total views for each page. Pass `user` to see pages a specific visitor hit. Endpoint: https://api.convalytics.dev/mcp
- top_referrers - Return the top referring hosts for a specific project, ranked by visit count in a time window. Includes '(direct)' for visits with no referrer. Default window is the last 7 days. Endpoint: https://api.convalytics.dev/mcp
- pageviews_count - Count page views for a specific project in a time window. Page views are the automatic hits captured by the browser script tag (separate from custom events). Use this for web-traffic questions like 'how many pageviews in the last 24 hours'. Default window is the last 7 days. Pass `user` to scope to one visitor. Endpoint: https://api.convalytics.dev/mcp
- events_count - Count CUSTOM PRODUCT events for a specific project in a time window, optionally filtered to one event name and/or one user. Custom events are emitted by explicit analytics.track() calls in app code (signup_completed, payment_succeeded, etc.). This does NOT count page views — use pageviews_count or weekly_digest for those. Returns count, unique visitors, and a `truncated` flag if the scan hit the maximum scan size. Endpoint: https://api.convalytics.dev/mcp
- recent_events - Return the most recent custom events for a specific project, optionally filtered to one event name and/or one user. PII (userEmail, userName, props) is redacted by default; pass redact: false to include them. Endpoint: https://api.convalytics.dev/mcp
- user_activity - Composite snapshot of a specific user's activity on a project. Returns an identity block (visitorId, userEmail, userName, firstSeen, lastSeen), total pageviews, total custom events, session count, top pages this user visited, their most-fired event names, and their 20 most recent events with props. Use this for 'how is dancleary54@gmail.com using my app?' style questions — one call, full picture. For ad-hoc drill-down (just a count, just recent events) pass `user` to the individual tools instead. Default window is the last 7 days. Endpoint: https://api.convalytics.dev/mcp
- weekly_digest - Composite snapshot of a project's web analytics over a lookback window. Returns unique visitors, pageviews, sessions, bounce rate, average session duration, top 5 pages, top 5 referrers, total custom events, and top 5 event names. Includes period-over-period comparison against the prior equal-length window unless compare: false. Prefer this over chaining top_pages + top_referrers + events_count when the agent just wants to report on the week. Endpoint: https://api.convalytics.dev/mcp
- list_funnels - List active funnels defined on a project. A funnel is a saved ordered sequence of steps (events or pageview paths) that Convalytics computes step-by-step conversion for. Soft-deleted funnels are excluded. Endpoint: https://api.convalytics.dev/mcp
- get_funnel - Return the full definition of one funnel by id: name, description, ordered steps, and conversion window. Endpoint: https://api.convalytics.dev/mcp
- create_funnel - Create a new funnel on a project. Steps are 2–10 ordered events or pageview paths. conversionWindowMs caps how long a visitor has between consecutive steps (default 7 days); this is the step-to-step limit, without which a funnel is just event co-occurrence. Returns { id } on success. Endpoint: https://api.convalytics.dev/mcp
- update_funnel - Patch an existing funnel. Any subset of name/description/steps/conversionWindowMs. Refuses updates on deleted funnels. Endpoint: https://api.convalytics.dev/mcp
- delete_funnel - Soft delete a funnel. The row is retained with status='deleted' and excluded from list/get/compute. Idempotent — calling twice is a no-op. Use if the funnel is obsolete; the record is kept for audit and cannot be undone from MCP. Endpoint: https://api.convalytics.dev/mcp
- compute_funnel - Run a funnel over a time window and return per-step visitor count, conversion from previous step, conversion from start, and average time to convert between steps. Returns `truncated` flags if the scan cap was hit. Endpoint: https://api.convalytics.dev/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.Dan-Cleary
- Version: 1.0.0
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Apr 23, 2026
- Source: https://registry.modelcontextprotocol.io