Provides a native Android SDK (via JitPack) for tracking events, user identification, and autocapture in Android apps.
Publishes a Dart SDK on pub.dev for Flutter/Dart apps to send analytics events and user properties.
Offers a React Native SDK (via npm) that works with Expo for tracking events and autocapture in React Native apps.
Provides a Flutter SDK on pub.dev for tracking events and user properties in Flutter apps.
Provides a native Swift SDK (via SPM) for iOS apps to track events, identify users, and autocapture clicks.
Provides a Kotlin/Android SDK (via JitPack) for tracking events and user properties in Android apps.
Includes a framework guide for integrating the analytics snippet and track() calls in Next.js applications.
Includes a framework guide for integrating the analytics snippet and track() calls in React applications.
Provides a native Swift SDK (via SPM) for iOS/macOS apps to track events, identify users, and autocapture clicks.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@smolanalytics show me the funnel from signup to purchase"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
End-to-end tests written as one English sentence. An agent runs them in a real browser, and a passing run replays with no model call.
smolanalytics.com · The nightly proof · Docs · npm
npx smolanalytics test --url https://yourapp.com --test "the pricing page shows a monthly price"A test is one sentence in a markdown file. An agent opens a real browser, reads the page through its accessibility tree, works out how to do what the sentence says, and returns a verdict. There is no test code, so there is no selector to update when a button moves.
A run that passes is recorded, and every run after it replays that recording with no model call at all. The agent comes back only when the recording stops fitting your app.
Five verdicts, never blurred: passed, failed, stale, errored, flaky. Only failed is a claim about your app. A recording that stopped fitting is stale, never a bug report, and a runner that could not finish is errored, never counted against you.
test --suite tests/ --url <preview> --comment runs a folder of sentences and leaves one comment on
the pull request, edited in place on every push: what broke, the file most likely responsible and
the evidence for that guess. Exit codes are 0 (clean), 1 (your app failed a test) and 2 (the runner
could not finish). The workflow file is in the docs.
Related MCP server: DB-MCP
{ "mcpServers": { "smolanalytics": { "command": "npx", "args": ["-y", "smolanalytics", "mcp"] } } }Three tools: run_tests, can_i_ship and list_tests. Listed on the official MCP Registry as
io.github.Arjun0606/smolanalytics.
smolanalytics.com/proof is a GitHub Action that runs this product's own suite against two live sites every night and publishes every verdict, including the red ones. Nothing on that page is written by hand.
The CLI runs on your machine or your CI runner, on your own ANTHROPIC_API_KEY. A first run of a
test costs roughly what one agent conversation costs; a replay costs nothing. The hosted side at
smolanalytics.com is $19/month with 100 tested pull requests included,
after a 14-day trial with no card. This is commercial software, not open source.
Full CLI reference: cli/README.md. Questions: smolanalytics.com/contact.
This server cannot be deployed
Clamp Analytics MCP server: traffic, revenue, funnels, cohorts, errors, and search, for AI agents.
MCP server for building and testing AI agents with multi-model experimentation and insights.
MCP server for querying and analyzing data from ad platforms, analytics tools, and spreadsheets
Analytics your AI agent can actually use. Track, experiment, and optimize via MCP.
