Where apps write their log files on Windows, macOS and Linux, as exact copyable paths.
Scored across 2 tools
search_log_locations is for discovery by app name/alias/file, while get_app_log_locations retrieves details for a known slug. The two are related and both return log locations, which could cause slight confusion, but the slug requirement makes the intended workflow clear.
Both names follow a consistent snake_case verb_noun pattern and share the _log_locations suffix. The difference between get_ and search_ is a standard and predictable distinction.
Two tools is borderline thin for a server, though the narrow lookup purpose could justify it. The surface may feel under-scoped compared to typical MCP servers with more operations.
The search-then-get workflow covers the main lifecycle for finding log locations. Minor gaps exist, such as no obvious way to list all apps without a search term or to reverse-lookup an app from a known log path.
Every log location for one app, by the slug that search_log_locations returns.
Inputs: slug (required).
Find where an application writes its log files. Matches app names and aliases (for example 'teams', 'zoom', 'docker') and the names of files listed under a path (for example 'AppWorkload.log'), not vendor names. Returns each app's log paths by platform.
Inputs: query (required), limit, platform.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Search your mobile, web and server app logs session by session, and read grouped errors, daily stats, releases and alerts.
Your AI apps as one team: hand work to Codex or Claude Code on your Mac, with a shared logbook.
Open-source agent that observes and fixes your application. Query logs, traces, metrics, incidents.
Changelogs for apps, games and operating systems. Ask what shipped since the version you run.
Add one secure layer between your agents and this server.
