Skip to content
UXsniff logo

UXsniff MCP server

AI-powered UX analytics: session recordings, heatmaps, feedback widgets, and surveys for your website.

UXsniff is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
1
Works with
Any MCP client
Auth
API key
License
MIT, open source
Updated
September 2026

About the UXsniff MCP server

Connect UXsniff once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches UXsniff and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

UXsniff tools your AI can run

Once connected, your assistant can call any of these UXsniff actions by asking in plain language.

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Triggers

UXsniff events your agent can watch

These start a run the moment something happens in UXsniff, so work gets picked up on its own.

  • New Feedback

    Triggers when a visitor submits new feedback on your website.

  • New Survey Response

    Triggers when a visitor submits a new response to the selected survey.

    1 field

Give your assistant UXsniff

Connect UXsniff once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

UXsniff MCP, answered.

No. That is the point of it. One Activepieces server exposes UXsniff alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect UXsniff in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 1 tool, including Custom API Call, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.