Hoot Lens

com.hootlensv1.0.1Updated Oct 8, 2026

Read Hoot Lens recordings, replays, heatmaps, funnels and findings with your own account.

VerifiedStreamable HTTPWeb executableData & AnalyticsProductivity & Workflow

Overview

AI-generated overview

Lets an assistant read Hoot Lens session recordings, replays, heatmaps, funnels and findings using your own account.

What it does
Hoot Lens exposes its analytics content to an assistant: session recordings and replays, heatmaps, funnels and findings, read through your own Hoot Lens account. The manifest does not list individual tools, but a HOOTLENS_TOOLSETS setting suggests selectable groups covering read, replay, annotate, install, feedback and issues. A default project can be pinned so tools act on one project without repeating it.
When to use it
Useful when you want an assistant to pull qualitative product analytics — what users did in recorded sessions, where they dropped off in funnels, or what findings already exist — into a debugging, UX review or reporting conversation. Worth adding if your team already keeps this data in Hoot Lens and you want it reachable without switching tools.
Requirements
Runs as a remote endpoint at mcp.hootlens.com or as a local process via npx @hootlens/mcp over stdio, so Node.js is needed for the local option. Authentication is not declared in the manifest; access uses a Hoot Lens access key in HOOTLENS_PAT, or the sign-in stored by running the package's login command. Optional settings: HOOTLENS_API_URL, HOOTLENS_PROJECT and HOOTLENS_TOOLSETS. Network access to the Hoot Lens API is required.
Before you install
The HOOTLENS_PAT access key is a secret and should be supplied through the environment, not committed or shared. The toolset list includes annotate, install, feedback and issues, which may write to or change data in your Hoot Lens workspace rather than only reading it; restrict HOOTLENS_TOOLSETS to read-only groups if you only want inspection. Recordings and analytics data are sent to the assistant and its model provider, so review what is captured before connecting a production project.

Installation

In SourceWeft

  1. Open Hoot Lens in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.hootlens.com/mcp"
    }
  }
}

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.1LatestOct 8, 2026