Hoot Lens MCP server

Hoot Lens

Give your coding agent evidence from website visits: recordings, click maps, funnels and recurring snags. Trace a finding to the page, release, device and recorded moment before proposing a fix.

Version 1.2.0 is published with the doctor command and npm provenance from the public mcp-v1.2.0 tag. The release record links the exact source, attestation and official MCP Registry entry. Issues and questions are welcome here.

The 1.1.0 release record preserves that release's provenance and source. Provenance identifies the source and build, not a security certification. The 1.1.0 security evidence records bounded scans and synthetic permission checks. Historical scan evidence remains specific to the versions it inspected. Neither transfers to 1.2.0.

Try a first investigation without an account

Connect a remote MCP client to:

https://mcp.hootlens.com/demo

For Claude Code:

claude mcp add --transport http hootlens-demo https://mcp.hootlens.com/demo

Ask your agent:

Find one recurring snag in the fictional Fieldnote site. Say the data is synthetic. Cite its page, release, revision, device, variant and one recording with a timed source moment. Separate what was observed from what still needs reproduction. Do not change anything.

The demo offers read and replay tools only. It requires no account or token. Start with whoami to verify the synthetic project, then reviewfindings. Follow an example through getheatmap, getrecording and getsession_narrative. A historical cohort is evidence to investigate, not proof of a current defect, a visitor's opinion or an improvement.

Connect your own site

The local package needs Node.js 20 or newer. Sign in with the projects and read permissions you want to share:

npx -y @hootlens/mcp@1.1.0 login --scopes read,replay
npx -y @hootlens/mcp@1.1.0 whoami

Add a stdio server to your client with command npx and arguments -y @hootlens/mcp@1.1.0 --toolsets read,replay for an investigation connection. Read scopes alone do not remove default install and feedback tools, which can submit setup requests or issues. Selecting the toolsets narrows what your agent is offered. It uses the saved sign-in. HOOTLENSPAT, when set, overrides it. You can pin a project with --project YOURPROJECT_ID; the API still checks access on every request.

For remote clients, connect to https://mcp.hootlens.com/mcp and approve Hoot Lens sign-in in the browser. See the current client guides and permission details, or the Cline installation guide.

Package 1.1.0 includes MCP Apps for hosts that render them, JavaScript error tools and optional site creation and configuration tools. The package and hosted server have separate release schedules. Run the CLI whoami above, then call the MCP whoami tool and inspect tools/list on the connection you actually use. A listed client guide is not proof that every client has been tested.

End the local sign-in with npx -y @hootlens/mcp@1.1.0 logout. Revoke a connected app or access key in the Hoot Lens dashboard when access should end.

Check local setup with doctor

Doctor requires 1.2.0 or a source build containing the command. Published 1.1.0 does not include it. In a release containing doctor:

npx -y @hootlens/mcp doctor --toolsets read,replay
npx -y @hootlens/mcp doctor --authenticated --project YOUR_PROJECT_ID --toolsets read,replay --json

To check this source before publication, build the checkout and use its executable:

node dist/cli.mjs doctor --toolsets read,replay
node dist/cli.mjs doctor --authenticated --project YOUR_PROJECT_ID --toolsets read,replay --json

Shortened. The full README is on GitHub.