Data · Local MCP server
Logly
Query your Logly web analytics — traffic, funnels and real-time visitors — from any MCP client.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.logly-uk/logly-mcp- Version
- 1.0.2
- Status
- Active
- Category
- data
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-05-18
- Updated
- 2026-05-18
- Publisher
- logly-uk (GitHub)
- Website
- logly.uk/mcp/
- Repository
- github.com/logly-uk/logly-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @logly-uk/mcp | 1.0.2 | stdio |
How to connect Logly
Logly runs locally from a Node.js package published to the npm registry: @logly-uk/mcp version 1.0.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @logly-uk/mcp@1.0.2. It reads the environment variable LOGLY_API_KEY (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"logly-mcp": {
"command": "npx",
"args": [
"-y",
"@logly-uk/mcp@1.0.2"
],
"env": {
"LOGLY_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, logly.uk, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | Real file, HTTP 200 · 2026-10-04 |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More data servers
| Server | Runs |
|---|---|
| loc8n Geographic DataU.S. demographics, housing, mortgage, migration, and employment data via loc8n API. | Remote & Local · SSE, stdio |
| LocalPro — Verified US Local Service Provider DataVerified US local service providers across 10 home-services trades. Owned data, no API key. | Remote · HTTP |
| LocusPay-per-use APIs for agents: web research, data lookups, and metered endpoints billed to credits. | Remote · HTTP |
| Loggly MCPRead-only Loggly search and analytics with aggregation-first traffic tools and IP intelligence. | Local · stdio |
| Logo.dev MCPLook up company logos and brand data via the logo.dev API. | Local · stdio, HTTP |
| LogobakerSearch logos, browse feeds and blogs, check your stats — from your AI chat. | Remote · HTTP |
| LogoKit Brand & Company DataCompany & brand data by domain or ticker/ISIN: industry, headcount, HQ, social, colors, logos. | Remote · HTTP |
| Lol Datadragon MCPLeague of Legends champion data from Data Dragon. No key required. | Local · stdio |