Query your Logly web analytics — traffic, funnels and real-time visitors — from any MCP client.
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.
logly_a1b2c3...
and is shown only once.The server runs via npx — no install step needed.
Edit claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": {
"logly": {
"command": "npx",
"args": ["-y", "@logly-uk/mcp"],
"env": { "LOGLY_API_KEY": "logly_your_key_here" }
}
}
}
Restart Claude Desktop.
claude mcp add logly -e LOGLY_API_KEY=logly_your_key_here -- npx -y @logly-uk/mcp
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" }
}
}
}
| 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>. |
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.
| Variable | Required | Purpose |
|---|---|---|
LOGLY_API_KEY | yes | Your Logly API key. |
LOGLY_API_BASE | no | Override the API base URL (default https://app.logly.uk). |
MIT licensed.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @logly-uk/mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-logly-uk-logly-mcp": {
"command": "npx",
"args": [
"-y",
"@logly-uk/mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceLogly works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.