Mezmo

Mezmo MCP Server lets you retrieve logs from Mezmo through the Model Context Protocol, with quota-conscious defaults so you can debug efficiently without quickly exhausting your quota. You provide your API key, run the server, and then query logs with practical filtering to discover and investigate relevant events.

How to use

You will connect your MCP client to the Mezmo MCP Server to fetch logs. Start with a small, discovery-focused query to understand what data is available, then narrow your results by app, level, and time window. Use the default 6-hour time range and a small initial log count to conserve quota, and progressively increase the count only after you have confidence in the filters.

How to install

Prerequisites you need before beginning: a container runtime (Docker and docker-compose) and a modern shell on your machine.

1. Install Docker and Docker Compose on your machine according to your operating system’s guidelines. 2. Obtain your Mezmo Service API key from the Mezmo dashboard.

2. Prepare your local environment for running the MCP server.

3. Start the server with Docker Compose. The server runs on port 18080 and includes built-in time window handling, retry logic, and error handling.

Configuration and runtime

Two ways to run the MCP server are provided: a remote HTTP endpoint and a local, stdio-based runtime. Use the HTTP option when you want to connect to a remote server via a URL. Use the stdio option when you want to run the server locally inside a container and invoke it directly.

Security and secrets

Never commit your API key. Store sensitive values in a local .env file and reference them at runtime. If authentication is enabled, keep tokens secret and rotate them as needed.

Commands

# Start the server locally via Docker Compose
docker-compose up -d

# Stop the server
docker-compose down

# View logs in real time
docker-compose logs -f

Troubleshooting

If the server container won’t start, verify that your .env contains the correct API key and review the logs for startup errors. If you cannot connect from an MCP client, ensure the container is running and restart the client after configuration changes.

Notes and examples

The server provides a default 6-hour window for log queries and returns 10 logs per request by default. Begin with a small discovery set (3–5 logs) to identify available apps and log schemas, then filter by app and log levels (ERROR/WARNING) before increasing the count.

Available tools

get_logs

Tool to retrieve logs from Mezmo via MCP with configurable filters such as count, apps, levels, and time window.