get_logsLABSCO SUMMARY
One tool, and the defaults are the design.
Log APIs charge by what you pull, which makes a naive agent expensive fast — asking for a wide window with no filter is exactly what a model does unprompted. Capping the default window at six hours and the count at ten forces the useful order of operations: find out which apps are logging, filter to the one you care about, add a level filter, then raise the count. Widen the time range only when the default genuinely does not reach the incident.
What it is
A single-tool MCP server for retrieving logs from Mezmo. The design is built around quota: it defaults to a six-hour window and ten log lines, and the documented workflow is to discover which apps exist with a handful of lines before filtering and scaling up.
What you get
get_logsreturns log lines from Mezmo, defaulting to the last 6 hours with a count of 10appsnarrows to specific applications, taking a comma-separated list — the single biggest reduction in resultslevelsfilters by severity, so a noisy app can be cut down to errors and warningsquerysearches within the matching lines for a phrasefrom_tsandto_tsset an explicit time range when the default window is not enough- All log levels are returned unless you filter, so the noise reduction is yours to choose
Requirements
A Mezmo Service API key, set as MEZMO_API_KEY in a local .env. The server runs in Docker through docker-compose up -d. Cursor connects over Streamable HTTP at http://localhost:18080/mcp; Claude Desktop can instead exec into the running container. Optional MCP-level authentication is available through MCP_ENABLE_AUTH and MCP_API_TOKEN. The Python package is mezmo-mcp, version 2.0.0.
Setup effort
Run a container — build the image from the repository, then point your client at it
USE CASES
01
Finding the error behind a report
Filter to the app and to error and warning levels, then read the handful of lines that matter.
02
Working out what is even logging
Pull three to five lines with no app filter to see the shape of the data first.
03
Searching for a specific failure
Add a phrase query on top of the app and level filters instead of scrolling.
04
Looking at a window that has already passed
Set an explicit start and end timestamp when the incident is older than the default window.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
- docker-compose on PATH
- MEZMO_API_KEY in the repository's .env file
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/riefer02/mezmo-logs-mcp
cd mezmo-logs-mcp
cp env.example .envEdit .env and set MEZMO_API_KEY to your Mezmo Service API key.
TERMINAL
docker-compose up -dMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"mezmo": {
"url": "http://localhost:18080/mcp",
"description": "Mezmo log retrieval"
}
}
}
