Logly MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOGLY_API_KEY | Yes | Your Logly API key (required) | |
| LOGLY_API_BASE | No | Override the API base URL | https://app.logly.uk |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| logly_list_sitesA | List every website in the authenticated Logly account with its site ID. Start here to find the site ID the other tools need. |
| logly_statsB | Traffic totals for a site — pageviews, sessions, visitors, bounce rate, average duration — plus a daily series and a comparison against the previous period. |
| logly_breakdownC | Top pages, top referrers, top countries and device/browser split for a site over the given period. |
| logly_realtimeB | Visitors currently active on a site (real-time, the last few minutes). |
| logly_eventsB | Custom event counts for a site (events sent via logly('event', ...)) over the given period. |
| logly_funnelsA | List the conversion funnels defined for a site, with their IDs and step sequences. |
| logly_funnel_resultsC | Completion counts and drop-off per step for one conversion funnel. |
| logly_install_snippetA | Return the Logly tracking snippet for a site — the single tag to add to the site's . Works offline, no API call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool maps to a distinct analytics concern: site selection, overall stats, dimensional breakdown, realtime activity, custom events, funnel definitions, funnel performance, and snippet installation. Stats and breakdown are related but their descriptions make the outputs clearly non-overlapping.
All tools share a consistent logly_ prefix and snake_case style, which makes the set predictable. However, names mix noun-style resources like stats and events with verb-style actions like list_sites and install_snippet, so the convention is not perfectly uniform.
Eight tools is a well-scoped count for a web analytics server. Each tool covers a meaningful slice of the analytics workflow without redundancy.
The set covers site discovery, high-level and dimensional traffic reporting, realtime monitoring, custom events, funnel definition and result retrieval, plus snippet installation. There are no obvious dead ends for the read-only analytics use case implied by the tools.