
Logly
io.github.logly-ukPublished by GitHub account logly-ukv1.0.2Updated Oct 24, 2026
Query your Logly web analytics — traffic, funnels and real-time visitors — from any MCP client.
Overview
A local MCP server that lets an assistant query your Logly web analytics — traffic, breakdowns, real-time visitors and conversion funnels.
- What you can do
- List sites in your Logly account with their site IDs and retrieve the install snippet for adding Logly to a site's head tag. Read traffic stats such as pageviews, sessions, visitors, bounce rate and average duration, with daily series and previous-period comparison. Break down top pages, referrers, countries and device or browser splits. Check visitors active right now and count custom events. List a site's conversion funnels and their steps, and get completion counts and drop-off per step. Stats tools accept a days window of 7, 30 or 90, or an explicit from/to date pair.
- When to use it
- Useful when you already run Logly analytics and want to ask an assistant plain-language questions about traffic changes, traffic sources, or where a signup funnel is losing visitors, without opening the dashboard.
- Requirements
- Runs locally via npx, so Node.js 18 or newer is needed. A Logly account and an API key supplied in the LOGLY_API_KEY environment variable; the key is created in Settings → API keys and shown only once. Network access to the Logly API; LOGLY_API_BASE can override the default API base URL.
Installation
In SourceWeft
- Open Logly in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Logly MCP server
Query your Logly web analytics from Claude, Cursor, or any Model Context Protocol client.
Logly is privacy-first web analytics — under 1 KB, cookie-free, GDPR compliant by design. This server exposes your analytics over MCP so an AI assistant can answer questions like "how did traffic change this week?" or "where is my signup funnel losing people?" — and even hand you the install snippet for a new site.
Requirements
- Node.js 18 or newer
- A Logly account and an API key — create one in Settings → API keys in your
Logly dashboard. The key looks like
logly_a1b2c3...and is shown only once.
Setup
The server runs via npx — no install step needed.
Claude Desktop
Edit claude_desktop_config.json (Settings → Developer → Edit Config):
Restart Claude Desktop.
Claude Code
Cursor
Add to .cursor/mcp.json in your project (or the global one):
Tools
Date filters
Stats tools accept a days window (7, 30 or 90 — defaults to 30) or an explicit
from / to pair (YYYY-MM-DD). If both are given, from/to wins.
Environment variables
Links
- Logly — https://logly.uk
- MCP server page — https://logly.uk/mcp/
- Public API reference — https://logly.uk/docs
MIT licensed.
Source: README.md at commit dd771af
Tools
0Version history
1- v1.0.2LatestSep 16, 2026
Score
50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts