Where Them Logs

app.wherethemlogsv1.0.0Updated Oct 5, 2026

Where apps write their log files on Windows, macOS and Linux, as exact copyable paths.

VerifiedStreamable HTTPWeb executableDeveloper ToolsKnowledge & Memory

Overview

AI-generated overview

Looks up where applications write their log files on Windows, macOS and Linux, returning exact copyable paths.

What it does
Provides a searchable index of application log file locations across Windows, macOS and Linux. Paths are qualified by installer type and architecture and stored byte for byte, so variables such as %LOCALAPPDATA% or ~/Library/Logs are returned unexpanded. The catalogue is organised as vendor, app and log path, and the site also offers platform, installer, architecture and scope filters.
When to use it
Useful during incident response or endpoint troubleshooting when you need the log path for a specific application on a specific platform and do not want to dig through forum threads. Also handy for IT administrators and application packagers documenting where apps write logs.
Requirements
Remote MCP endpoint at wherethemlogs.app over streamable HTTP; no package, account, API key or environment variable is declared. The assistant needs network access to that endpoint.
Before you install
The published catalogue is currently seed data — 24 vendors, 33 apps and 86 log paths — labelled as a demonstration set, so paths should be verified before relying on them. The site loads Google Analytics 4 after consent. No credentials are requested by the MCP endpoint.

Installation

In SourceWeft

  1. Open Where Them Logs in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "log-locations": {
      "type": "http",
      "url": "https://wherethemlogs.app/api/mcp"
    }
  }
}

README

wherethemlogs.app

[Where Them Logs MCP connector - tool definition quality and endpoint health on Glama] [smithery badge]

A searchable index of application log file locations across Windows, macOS and Linux - every path qualified by installer type and architecture, printed exactly as the machine writes it.

Built for the people who need the path mid-incident: IT and endpoint administrators, application packagers, and anyone else who has lost twenty minutes to a forum thread of unknown vintage.

Layout

app/                  pages, route handlers, proxy - Next.js 16components/  lib/     UI, shared model, server-only data accessinfra/                Azure resources - Bicepscripts/              seed data and the seederdocs/                 architecture, API reference, deployment, MCP, answer engines

One application, one image. Pages are server-rendered from Cosmos; route handlers under app/api/ serve the browser and the admin portal from the same process.

Run it

bash
npm installLOCAL_ADMIN_BYPASS=true \COSMOS_ENDPOINT=https://<account>.documents.azure.com:443/ \COSMOS_DATABASE=wtla \npm run dev            # http://localhost:3777

Needs az login with an account that holds the Cosmos data-plane role. Full setup is in docs/DEPLOYMENT.md.

What's here

RouteWhat it does
/Title sign, search field with live type-ahead, recent additions, recent searches, platform filter
/searchFull results, filterable by platform, installer, architecture and scope
/privacyPrivacy and cookie notice
/adminAdmin portal - vendors, apps and log paths, with JSON import and export at /admin/import. Entra sign-in, admin role. API in docs/API.md.

Keyboard: / focuses the search field from anywhere, arrows walk the type-ahead, Enter commits to the full results, Shift+Enter copies the highlighted result's first path.

The catalogue

Vendor > App > LogPath. One vendor has many apps; one app has many log paths, embedded on the app document. Every vendor carries an icon and every app may override it - App.iconUrl: null means inherit the vendor's, resolved on read.

Currently seed data: 24 vendors, 33 apps, 86 log paths in scripts/seed-data.json, all real and verifiable, labelled as a demonstration set in the footer and on the privacy page.

bash
npm run seed -- --endpoint https://<account>.documents.azure.com:443/

Paths are stored byte for byte - %LOCALAPPDATA%, ~/Library/Logs, $XDG_STATE_HOME are never expanded, because the machine being fixed is not this one.

Contributing an entry

Open an issue. One issue per application, with the platform and installer type in the title, and say how you verified the path.

Issues are public: do not paste real hostnames, usernames, tenant identifiers or customer names into one.

Before this goes live

  • Register the Entra ID app, add the admin app role, and set the AUTH_CLIENT_ID / AUTH_TENANT_ID repository variables. Until then /admin has nowhere to send you. docs/DEPLOYMENT.md § 7.
  • Choose the analytics provider - Google Analytics 4, loaded only after Accept (components/Consent.tsx).
  • Replace the seed catalogue with the real index - /admin/import takes the research JSON.
  • Build the admin UI on top of the CRUD API.
  • Make the repo public - requests and corrections are issues here, from the forms in .github/ISSUE_TEMPLATE/.

Infrastructure

Azure Container Apps runs the image; Cosmos DB (serverless) and Blob Storage sit behind it, both reached by managed identity - no keys anywhere. Deploys are a new revision, so rolling back is a traffic shift rather than a rebuild.

Around $20/month. Why each piece, and what it costs, is in docs/ARCHITECTURE.md.

Design

DESIGN.md records the visual system as built. PRODUCT.md records product truth. The direction contract for the site's surfaces lives in .impeccable/surfaces/.

Two rules worth knowing before you touch the CSS:

  • Flat print, no exceptions. No gradients, no shadows, no floating cards. Structure is stencilled rules and hazard tape. Signal cyan on near-black must not drift into neon glow.
  • Two voices. Archivo for anything human, Spline Sans Mono for anything machine-true - paths, codes, counts, filter values. Nothing else.

Source: README.md at commit 5408995

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestOct 5, 2026