# Where Them Logs [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/scotscottmca/wherethemlogs.app  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/where-them-logs

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

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What Where Them Logs does

Where Them Logs MCP server exposes information from an index of application log locations for Windows, macOS, and Linux. The catalogue is organized as vendors, applications, and log-path records. An application can contain multiple paths, while vendor and application icon metadata supports the web interface rather than the path data itself.

The project is intended for situations where someone needs a log location during an incident or while preparing application support material. Its audience includes IT and endpoint administrators, application packagers, and other developers or operators investigating software behavior.

Paths are retained byte for byte. Variables and platform-specific notation such as `%LOCALAPPDATA%`, `~/Library/Logs`, and `$XDG_STATE_HOME` are not expanded on the server, because the target machine may differ from the machine running the catalogue.

## How it works

The application uses Next.js 16 for pages and route handlers. Server-rendered pages read from Azure Cosmos DB, and the same process serves browser and administrative API routes. Azure Container Apps runs the image, while Cosmos DB and Blob Storage are accessed through managed identity according to the repository description.

The public interface includes a live type-ahead search, recent additions, recent searches, a platform filter, and a fuller results view. Results can be filtered by platform, installer, architecture, and scope. The repository also identifies an MCP connector for the project, but the supplied material does not specify its transport, request schema, or individual MCP tool names.

## Setup and configuration

The documented local development command requires Node package installation and a Cosmos DB connection:

- `LOCAL_ADMIN_BYPASS=true`
- `COSMOS_ENDPOINT=https://<account>.documents.azure.com:443/`
- `COSMOS_DATABASE=wtla`

The README says that an Azure login with a Cosmos data-plane role is required. Seed data can be loaded with the repository's seeding script and a Cosmos endpoint. The supplied setup instructions describe the web application and database, not a separate MCP client configuration.

For production administration, the project plans to use Entra sign-in with an `admin` role. The documented deployment checklist references `AUTH_CLIENT_ID` and `AUTH_TENANT_ID` repository variables. These are associated with the administrative portal and are not presented as general MCP client settings.

## Tools and capabilities

Where Them Logs MCP server is supported by a catalogue containing 24 vendors, 33 applications, and 86 log paths in the current seed dataset. The README labels this collection as demonstration data, so coverage should not be treated as a complete inventory.

Supported application behavior includes:

- Searching application names and log locations.
- Filtering results by operating system, installer type, architecture, and scope.
- Returning paths without expanding environment variables or shell notation.
- Managing vendors, applications, and log paths through an authenticated admin portal.
- Importing and exporting JSON through the administrative interface.

The keyboard interface can focus search, move through type-ahead suggestions, submit full results, and copy the first path of a highlighted result. Those interactions describe the website UI; the provided README does not confirm which are exposed as MCP operations.

## Limitations and notes

The current catalogue is explicitly seed data and is marked as a demonstration set. Coverage, freshness, and verification status therefore depend on the entries that have been added. Contributions are requested through public issues, with one issue per application and platform and installer details included. Contributors are asked not to include real hostnames, usernames, tenant identifiers, or customer names.

Where Them Logs MCP server should not be assumed to expand paths for the host being investigated. A returned value may contain a variable or home-directory marker that must be interpreted on the target system. The supplied material also does not name supported MCP clients, define authentication for MCP requests, or document a standalone MCP installation command.

_Full upstream README: https://allmcps.com/mcp/where-them-logs/readme_