Where Them Logs

app.wherethemlogsv1.0.0更新於 Oct 5, 2026

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

已驗證Streamable HTTP可網頁執行Developer ToolsKnowledge & Memory

概覽

AI 產生的概覽

查詢 Windows、macOS 與 Linux 上應用程式寫入記錄檔的位置，回傳可直接複製的完整路徑。

功能
提供橫跨 Windows、macOS 與 Linux 的應用程式記錄檔位置可搜尋索引。路徑依安裝程式類型與架構標註，並以位元組原樣儲存，因此 %LOCALAPPDATA%、~/Library/Logs 等變數不會被展開。目錄以廠商、應用程式與記錄路徑組織，網站另提供平台、安裝程式、架構與範圍篩選。
適用情境
適合在事件處理或端點排障時，需要某個應用程式在特定平台上的記錄路徑，而不想翻找年代不明的論壇文章。也適合 IT 管理員與應用程式封裝人員記錄應用程式寫入記錄的位置。
執行需求
透過 streamable HTTP 連線至 wherethemlogs.app 的遠端 MCP 端點；未宣告任何套件、帳號、API 金鑰或環境變數。助理需要能連線至該端點的網路。
安裝前請注意
目前發布的目錄為種子資料——24 個廠商、33 個應用程式、86 條記錄路徑——並標示為示範資料集，使用前應先核實路徑。網站在使用者同意後載入 Google Analytics 4。MCP 端點不要求任何憑證。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Where Them Logs，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "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.

來源：README.md，提交 5408995

工具

0
工具後設資料尚未被收錄。

版本歷史

1
  1. v1.0.0最新Oct 5, 2026