Hey HN. Clamp is web analytics where the interface is your coding agent, not a dashboard.
I kept going back and forth between my editor and analytics dashboards, exporting CSVs, dragging them into Claude, just to check how stuff I shipped was doing. My agent already knows what PR I merged, what page I changed. Now it can also see how they impact user behaviour.
Ship a pricing page redesign, ask "how's the pricing page doing since yesterday?" Push a new landing page, ask "where's the traffic coming from?" an hour later.
Stack: browser SDK (<1KB gzipped, no cookies, no personal data), Hono API, Redis buffer, ClickHouse. IPs resolve to country/city via MaxMind server-side and get discarded.
The MCP server (`npx -y @clamp-sh/mcp`) exposes 11 tools: traffic overview, top pages, referrers, countries, cities, devices, custom events, timeseries, funnels, alerts.
I kept going back and forth between my editor and analytics dashboards, exporting CSVs, dragging them into Claude, just to check how stuff I shipped was doing. My agent already knows what PR I merged, what page I changed. Now it can also see how they impact user behaviour.
Ship a pricing page redesign, ask "how's the pricing page doing since yesterday?" Push a new landing page, ask "where's the traffic coming from?" an hour later.
Stack: browser SDK (<1KB gzipped, no cookies, no personal data), Hono API, Redis buffer, ClickHouse. IPs resolve to country/city via MaxMind server-side and get discarded.
The MCP server (`npx -y @clamp-sh/mcp`) exposes 11 tools: traffic overview, top pages, referrers, countries, cities, devices, custom events, timeseries, funnels, alerts.
SDK and MCP server are MIT licensed:
https://github.com/clamp-sh/analytics
https://github.com/clamp-sh/mcp
API is closed source. Free tier is 5K events/month.
Would love feedback on the MCP tool design.