Query your Logly web analytics — traffic, funnels and real-time visitors — from any MCP client.
Query your Logly web analytics — traffic, funnels and real-time visitors — from any MCP client. The logly mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 9 defined tools rather than through you.
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.
Everything the assistant can do here goes through one of these:
logly_list_sites — List every site in your account with its site ID — start herelogly_stats — Pageviews, sessions, visitors, bounce rate, avg duration, daily series, previous-period comparisonlogly_breakdown — Top pages, referrers, countries and device/browser splitlogly_realtime — Visitors active right nowlogly_events — Custom event countslogly_funnels — List a site's conversion funnels and their stepslogly_funnel_results — Completion counts and drop-off per funnel steplogly_install_snippet — The tag to add Logly to a site's Cursor — Add to .cursor/mcp.json in your project (or the global one):You will need one environment variable: LOGLY_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
logly_a1b2c3... and is shown only once.Installation goes through your MCP client rather than a global install: point it at @logly-uk/mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Logly's toolset — logly_list_sites, logly_stats, logly_breakdown and 6 more — is a fair guide to whether it matches your workflow. It is maintained by logly-uk; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| logly_list_sites | List every site in your account with its site ID — start here. |
| logly_stats | Pageviews, sessions, visitors, bounce rate, avg duration, daily series, previous-period comparison. |
| logly_breakdown | Top pages, referrers, countries and device/browser split. |
| logly_realtime | Visitors active right now. |
| logly_events | Custom event counts. |
| logly_funnels | List a site's conversion funnels and their steps. |
| logly_funnel_results | Completion counts and drop-off per funnel step. |
| logly_install_snippet | The <script> tag to add Logly to a site's <head>. |
| Cursor | Add to .cursor/mcp.json in your project (or the global one): |
{
"mcpServers": {
"logly": {
"command": "npx",
"args": ["-y", "@logly-uk/mcp"],
"env": { "LOGLY_API_KEY": "logly_your_key_here" }
}
}
}Configuration as documented by the project. Restart the client after saving.
logly_a1b2c3... and is shown only once.| Variable | Description | Required |
|---|---|---|
| LOGLY_API_KEY | Credential the server authenticates with. | Yes |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.