The Devrev browser action destination for use with @segment/analytics-next.
Connect Analytics to Claude, Cursor or any other MCP client and it stops being a tab you switch to. The Devrev browser action destination for use with @segment/analytics-next. The analytics mcp server is what makes that connection.
Action Destinations are the new way to build streaming destinations on Segment.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Note — this part of the schema is not persisted outside the codePasswords — User passwords, service account passwords, or any authentication credentialsTokens — Access tokens, refresh tokens, bearer tokens, OAuth tokens, or JWT tokensSecrets — Client secrets, shared secrets, or any confidential authentication dataTesting — Refer here for more information about testing your destination actionsConfiguring — Action destinations are configured using a single Destination setting (subscriptions) that should contain a JSON blob of all subscriptions for theAmong the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Analytics's toolset — Note, Passwords, Tokens and 3 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Note | this part of the schema is not persisted outside the code |
| Passwords | User passwords, service account passwords, or any authentication credentials |
| Tokens | Access tokens, refresh tokens, bearer tokens, OAuth tokens, or JWT tokens |
| Secrets | Client secrets, shared secrets, or any confidential authentication data |
| Testing | Refer [here](./docs/testing.md) for more information about testing your destination actions. |
| Configuring | Action destinations are configured using a single Destination setting (subscriptions) that should contain a JSON blob of all subscriptions for the destination. The format should look like this: |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.