Mezmo

A Model Context Protocol (MCP) server for retrieving logs from Mezmo. Quota-conscious design with intelligent defaults - just add your API key and run!

- Time Range: Last 6 hours (when not specified) - balances quota with finding actual logs
- Log Count: 10 logs per request
- Log Levels: All levels (you control filtering)
- First, fetch 3-5 logs to discover available apps and log shape
- Then, filter by specific app(s) you're debugging
- Add level filtering for ERROR/WARNING to reduce noise
- Increase count only after filters are in place (e.g., 20-50)
- This approach minimizes quota usage significantly!

Get your Mezmo Service API key from the Mezmo dashboard.

# Clone the repository # (replace with your fork/clone URL) git clone <your-repo-url> cd <your-repo-dir> # Create your local .env (never commit it) cp env.example .env # then edit .env and set MEZMO_API_KEY # Build and run docker-compose up -d

{ "mcpServers": { "mezmo": { "url": "http://localhost:18080/mcp", "transport": "streamable-http", "description": "Mezmo log retrieval" } } }

For Claude Desktop(add to MCP settings):

{ "mcpServers": { "mezmo": { "command": "docker", "args": ["exec", "mezmo-mcp-server", "python", "server.py"] } } }

Restart your MCP client and you'll have access to theget_logstool!

Theget_logstool automatically retrieves logs from thelast 6 hourswhen no time range is specified - perfect for debugging while conserving quota.

Step 1: Discover available apps (3-5 logs):

{ "count": 3, "levels": "ERROR,WARNING" }

{ "count": 10, "apps": "app-a", "levels": "ERROR,WARNING" }

Advanced filtering (scale up only after filters work):

{ "count": 50, "apps": "app-a,app-b", "levels": "ERROR,WARNING", "query": "database connection" }

Custom time range (use sparingly - impacts quota):

{ "count": 50, "apps": "app-a", "from_ts": "1640995200", "to_ts": "1640998800" }

- Always filter by appwhen possible - this drastically reduces results
- Start tiny- use count=3-5 for discovery, then increase if needed
- Add level filtering- specify levels="ERROR,WARNING" to reduce noise
- Use default 6-hour windowunless you need wider historical data

- Never commit.env(it contains yourMEZMO_API_KEY).
- Prefer using.env.exampleas a template and keep your real values local.
- If you enable MCP authentication (MCP_ENABLE_AUTH=true), keepMCP_API_TOKENsecret as well.

docker-compose up -d # Start the server docker-compose down # Stop the server docker-compose logs -f # View logs

- Check your.envfile hasMEZMO_API_KEY=your_actual_key
- View logs:docker-compose logs

- Ensure container is running:docker-compose ps
- Restart your MCP client after configuration changes

That's it! The server runs on port 18080 and automatically handles time windows, retries, and error handling.

Fetch logs, metrics, traces, and events from the Chronosphere observability platform.

Kubernetes observability and diagnostics MCP server for cluster health, workload diagnosis, logs, events, topology, audit findings, and remediation actions.

Seamlessly bring real-time production context—logs, metrics, and traces—into your local environment to auto-fix code faster.

Provides access to OpenTelemetry traces and metrics through Logfire.

A server for querying Loki logs from Grafana.

Incident forensic with log files analyzing

An MCP server for log analysis using the LogAI framework, with optional Grafana and GitHub integrations.

A Go-based server to query Grafana Loki logs using the Model Context Protocol (MCP).

An MCP server for querying Loki logs via logcli.

The IBM Instana MCP server enables seamless interaction with the IBM Instana observability platform, allowing you to access real-time observability data directly within your development workflow.