Developer · Local MCP server

Logly

Query your Logly web analytics - traffic, funnels and real-time visitors - from any MCP client.

Visit Logly's website

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
developer
Transport
stdio (local process)
Package
npm
Published
2026-05-18
Updated
2026-05-18
Publisher
logly-uk (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/logly-uk) · how
Website
logly.uk/mcp/
Repository
github.com/logly-uk/logly-mcp
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
npm@logly-uk/mcp1.0.2stdioLOGLY_API_KEY (required, secret)

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.

FileResult
/llms.txtReal file, HTTP 200 · 2026-10-04
/.well-known/mcp.jsonNo real file found
/.well-known/ai-plugin.jsonNo real file found
/agents.jsonNo real file found

More developer servers

All 5,152 →
ServerRunsEndpoint or package
LogbookLocal Git-history memory for coding agents: reverts, suppressions, hotspots, and annotations.Local · stdionpm: @promptwheel/logbook-mcp
Logclaw MCP ServerConnect AI coding tools to LogClaw incidents, logs, and anomaly detections.Local · stdionpm: logclaw-mcp-server
LoggerheadRead the logs, metrics, and traces of the app you are editing, from the Loggerhead Mac app.Local · stdioMCP Bundle (.mcpb): rubics-code/loggerhead-mcp/releases/download/v1.
Logicapps MCPMCP server for Azure Logic Apps - debug workflows, manage runs, and authoring.Local · stdionpm: logicapps-mcp
Logto MCPMCP server for Logto: users, applications. Works with Cloud or self-hosted.Local · stdionpm: logto-mcp
Loki ModeAutonomous spec-to-product coding-agent CLI with an MCP server exposing 39 tools over stdio.Local · stdionpm: loki-mode
LokkaQuery and manage Microsoft Graph and Azure Resource Manager APIs from MCP clients.Local · stdionpm: @merill/lokka
LonghandLocal memory for Claude Code. Semantic recall across session history with zero API calls.Local · stdioPyPI: longhand