Agentic visitor analytics — five tools that hand the next CRO fix to your coding agent.
Connect Remote server
claude mcp add --transport http eyepup https://eyepup.com/mcp
{
"mcpServers": {
"eyepup": {
"url": "https://eyepup.com/mcp"
}
}
}
{
"servers": {
"eyepup": {
"type": "http",
"url": "https://eyepup.com/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://eyepup.com/mcp
Tools 5 found in our last check
eyepup_askAsk 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 a…
eyepup_todoGet 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.
eyepup_visitors_hotReturn 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'.
eyepup_visitorFetch 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.
eyepup_logLog 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.
Details
| Endpoint | https://eyepup.com/mcp (Streamable HTTP) |
| Package | [email protected] (NPM, stdio) |
| First published | 5 May 2026 |
| Last updated | 5 May 2026 |
| Registry name | io.github.edholofy/eyepup |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
