Eyepup

io.github.edholofyPublished by GitHub account edholofyv0.1.1Updated Oct 28, 2026

Agentic visitor analytics — five tools that hand the next CRO fix to your coding agent.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Eyepup gives an assistant agentic visitor analytics: ask free-text questions about site visitors, see friction patterns and high-intent visitors, and log…

What you can do
  • Ask natural-language questions about visitor behaviour and get LLM-grounded answers with evidence and ranked actions
  • List top friction patterns ranked by impact score, each with a paste-ready recommended action
  • See the top high-intent visitors currently active, and fetch a full LLM-written profile for one visitor by distinct_id
  • Log a UX change you just shipped so later visitor profiles can be graded against it
When to use it
Useful when you work on conversion or UX for a site and want an assistant to explain why visitors bounce, point to the highest-impact fix before editing, or identify visitors about to convert.
Requirements
A remote endpoint at eyepup.com or the local npm package eyepup-mcp over stdio. Requires an Eyepup API token supplied in the EYEPUP_API_TOKEN environment variable, minted in the Eyepup integrations page.
Before you install
The API token is a live credential (epk_live_ prefix) and should be kept secret. The log tool writes change records into your Eyepup account, and visitor profiles and analytics data are sent to Eyepup's service for LLM processing.

Installation

In SourceWeft

  1. Open Eyepup 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.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.edholofy%2Feyepup/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

This repository has no README.

Tools

5

eyepup_ask

Ask Eyepup about your visitors

Ask a natural-language question about your site visitors. Use this when the user asks 'why are people bouncing from /pricing', 'who's hot right now', 'what changed this week', or any other free-text question about visitor behaviour. Returns an LLM-grounded answer with evidence and ranked actions.

Parametersdayssitequestionrequired

eyepup_todo

List the friction-pattern To-Do queue

Get the top friction patterns ranked by impact score. Use BEFORE making any UX edit — the highest-impact pattern is usually a more valuable fix than whatever the user just asked about. Each row carries a paste-ready recommended_action.

Parameterssitelimit

eyepup_visitors_hot

Top high-intent visitors right now

Return the top high-intent visitors currently active. Use when the user asks 'who's hot', 'who's about to convert', 'who should I focus on'.

Parameterssitelimit

eyepup_visitor

Get the full dossier for one visitor

Fetch the full LLM-written profile for a single visitor by distinct_id. Use after eyepup_visitors_hot or eyepup_todo to dig into a specific visitor.

Parametersdistinct_idrequired

eyepup_log

Log a change you just shipped

Log a change you just shipped. The dossier agent reasons about every visitor profiled AFTER this log row, so it can grade whether the friction pattern recovered. CALL THIS after every UX edit.

Parameterskindsitepathstitlerequireddescription

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.