# Slimlytics [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/djedi/slimlytics  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/slimlytics

## Description
Privacy-first cookieless web analytics with agent one-prompt setup via remote MCP OAuth.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "slimlytics": {
    "url": "https://slimlytics.com/docs/mcp"
  }
}
```

## Documentation

## What Slimlytics MCP server does

Slimlytics MCP server gives an AI coding agent access to setup operations for Slimlytics, a cookieless web analytics service. The documented workflow lets an agent create a site, add tracking to a web project, configure first-party proxy routes, and check whether tracking is working. This is intended for installation and verification, not for replacing the Slimlytics dashboard.

Slimlytics analytics collects information such as pages, referrers, countries, devices, campaigns, visitors, and custom events. The product is designed to work without tracking cookies, fingerprinting, or session replay. Sensitive query parameters are redacted before storage, and the service respects Do Not Track and Global Privacy Control.

## How it works

The hosted MCP service is available at `https://slimlytics.com/api/mcp`. A compatible client connects over HTTP and completes browser-based OAuth. After authorization, the agent can act on the Slimlytics account and configure tracking for a specified site.

A typical request might ask the agent to set up Slimlytics for a website behind Nginx and verify it. The agent creates the site, prepares first-party proxy routes and the script tag, then confirms that the first page view reached Slimlytics. First-party delivery can use generated Caddy, Nginx, or Apache routes, according to the project documentation.

The repository also supports scoped personal tokens and a REST API, but the documented MCP setup uses the hosted service and OAuth. The MCP workflow does not require cloning the repository when using Slimlytics Cloud.

## Setup and configuration

Add the hosted endpoint to Claude Code with:

```bash
claude mcp add --transport http slimlytics https://slimlytics.com/api/mcp
```

Then authorize the connection in the browser and describe the site configuration you want the agent to apply. The repository identifies Claude Code, Codex, and Hermes as agent clients that can use the MCP workflow, and says the endpoint can be used by MCP clients generally. Client-specific setup instructions for Codex and Hermes are linked from the project documentation.

For a self-hosted analytics deployment, the repository documents Docker Compose, PostgreSQL, Caddy, and a generated `.env` file. That deployment path is separate from connecting to the hosted MCP endpoint. Review deployment URLs and settings before starting the stack, and do not expose the base HTTP configuration directly to the Internet.

## Tools and capabilities

The documented MCP capabilities support:

- Creating a Slimlytics site for an account.
- Adding tracking and first-party proxy configuration to a web project.
- Generating routes for Caddy, Nginx, or Apache setups.
- Verifying that an initial page view was received.
- Automating analytics installation through an AI coding agent.

Slimlytics MCP server is most relevant when setup needs to happen in the codebase or deployment configuration. For ongoing reports, live visitor activity, CSV exports, goals, and marketing analysis, the Slimlytics dashboard and product APIs are the documented product surfaces.

## Limitations and notes

The material documents a hosted remote MCP endpoint with browser OAuth; it does not provide a complete MCP tool schema or individual tool names. Exact behavior may depend on the connected client and the site’s web server configuration. The analytics service itself is privacy-oriented, but its first-party script still needs to be installed on the target site for data collection to begin.

Self-hosting requires operating the application infrastructure, including PostgreSQL and the reverse proxy. GeoIP-based visitor locations are optional and require the documented local database setup. The hosted product is the simpler path if the goal is to use analytics without managing those services.

_Full upstream README: https://allmcps.com/mcp/slimlytics/readme_