Lodd Mcp Server

io.github.hholenPublished by GitHub account hholenv0.1.15Updated Oct 25, 2026

Headless web analytics for AI agents. 42 MCP tools for traffic, events, funnels.

VerifiedSTDIODesktop onlyData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Lodd's first-party web analytics MCP server lets an AI assistant query your own site traffic, events, funnels and conversions as structured JSON.

What you can do
Query traffic, sources and page performance for your site's analytics data, including bounce rates and unusual activity investigation. Explore events, conversions and funnels, such as building a homepage-to-signup-to-purchase funnel. Review actor analytics, annotations, trackable links and account management through the same tool set. Results come back as structured JSON rather than a dashboard.
When to use it
Use it when your site already sends data to Lodd and you want an assistant to answer questions about traffic, conversions, funnels or traffic sources directly, or to investigate unusual changes in your analytics.
Requirements
Runs locally via npx from the npm package @lodd/mcp-server over stdio. Requires a Lodd API key in the LODD_API_KEY environment variable, obtained from the provider. A Lodd account with the tracking script installed on your site is needed for data. Network access to the Lodd API.
Before you install
Requires the secret LODD_API_KEY; keep it out of shared configs and repositories. Tools cover account management and annotations alongside read queries, so some actions may change data. Analytics data is sent to and stored by Lodd, a third party. Free tier is limited to 2,500 events per month; paid plans cost EUR 9.99 per month for 100K events.

Installation

In SourceWeft

  1. Open Lodd Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@lodd/mcp-server

First-party web analytics for AI agents. You add a 2KB script, Lodd collects your site's traffic, and your agent queries your own data over MCP. It's the analytics platform, not a connector to one.

42 MCP tools covering traffic, events, funnels, conversions, sources, performance, and actor analytics. No dashboard. Your agent queries structured JSON directly.

Quick start

bash
npx -y @lodd/mcp-server

Set LODD_API_KEY in your environment. Get a key at lodd.dev.

Claude Code / Cursor

Add to your MCP config:

json
{  "mcpServers": {    "lodd": {      "command": "npx",      "args": ["-y", "@lodd/mcp-server"],      "env": {        "LODD_API_KEY": "your-api-key"      }    }  }}

Claude Desktop / claude.ai

Add https://api.lodd.dev/mcp as an MCP connector. OAuth handles auth automatically.

What you can ask

  • "How's traffic this week?"
  • "Show me the pages with the highest bounce rate"
  • "Build a funnel from homepage to signup to purchase"
  • "Which traffic sources drive the most conversions?"
  • "Something unusual is happening today. Investigate."

Tools

42 tools across analytics, breakdowns, events, conversions, actors, annotations, trackable links, and account management. Full reference at lodd.dev/docs.

REST API

Same data is also available via REST at api.lodd.dev/v1/. API docs at lodd.dev/api. OpenAPI spec at lodd.dev/openapi.yaml.

Pricing

Free up to 2,500 events/month. EUR 9.99/month for 100K events. All tools included on both tiers.

Links

Source: README.md at commit a518957

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.15LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts