samuelcsantana/pyxis-mcp

reading, through a connection or a token you can revoke at any time.
Pyxis · Live demo ·
API reference
> Status: on npm as pyxis-mcp, every release published from GitHub Actions with
> provenance, and served by the Pyxis API at https://api.pyxis-analytics.dev/mcp.
## Ecosystem
| Repository | Role |
| pyxis-api | Ingestion, sign-in, dashboard queries, accounts and billing, erasure, the MCP endpoint |
| pyxis-sdk | Browser tracker published to npm as pyxis-analytics |
| pyxis-web | The dashboard and the home page |
| pyxis-mcp (this one) | MCP server: Claude and other agents read the dashboard's numbers |
## Why it exists
More and more questions about a product are asked to an agent instead of a dashboard: "how did
last week compare", "where does the sign-up funnel lose people", "which route started failing".
This server gives Claude Code, Claude Desktop, Cursor and other MCP clients the same numbers the
Pyxis dashboard shows, and nothing more: it reads through a Claude connection the admin allows or
an access token the admin creates, both read-only and revocable in the dashboard's Settings at any
moment. Like the rest of Pyxis, there
is no personal data to hand over: events carry no cookies, no addresses and no user agents.
## Tools
Every tool only reads, and maps to one GET route of the Pyxis API. Dates are YYYY-MM-DD in the
project's time zone; listprojects gives each project's today, so call it first. The server's
instructions tell the agent what an empty account means: with no project, one is created in the
dashboard; with a project that has received no event, the site does not run the tracker yet, and
llms.txt explains how to install it.
| Tool | What it answers |
| listprojects | The projects the token can read: id, name, time zone, today there, conversion event, first and last event |
| overview | Visits, identified users, conversions and failed writes against the previous period; top pages and events |
| devices | Visits and conversions by device type, browser, system, country and region |
| acquisition | Visits per day and channel, and the sources and campaigns behind them |
| engagement | Entry and exit pages, single-page visits, visit length |
| timeofday | Visits by weekday and local hour |
| features | The most used named events or screens, day by day |
| eventproperties | How the property values of one named event break down |
| propertysummary | The median and quartiles of a numeric property, split by another: how long people read each article |
| requests | Calls to the site's backend per route: failures, statuses, durations, latest errors |
| funnel | How many visits or people reached each step, and the time between steps |
| funnelsegments | The same funnel per device type or channel |
| funnelsubjects | The visits or people who reached, or dropped at, one step |
| visits | The visits of a range, filtered by pages, events, channel, device, country, campaign, failed requests |
| visittimeline | Every event of one visit, or every visit of one identified person |
| projectsettings | Time zone, conversion event, allowed origins, retention, live public keys |
A result is JSON text, { "untrustedvisitortext": "…", "report": … }: the report is the API's