Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Mezmo MCP Servershow me the last 5 error logs for the billing-service"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Mezmo MCP Server
A Model Context Protocol (MCP) server for retrieving logs from Mezmo. Quota-conscious design with intelligent defaults - just add your API key and run!
⚡ Smart Defaults
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)
Recommended Workflow:
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!
🚀 Quick Start
1. Get Your API Key
Get your Mezmo Service API key from the Mezmo dashboard.
2. Run with Docker
3. Configure Your MCP Client
For Cursor (add to .cursor/mcp.json):
For Claude Desktop (add to MCP settings):
4. Start Using
Restart your MCP client and you'll have access to the get_logs tool!
📋 Usage
The get_logs tool automatically retrieves logs from the last 6 hours when no time range is specified - perfect for debugging while conserving quota.
Step 1: Discover available apps (3-5 logs):
Step 2: Filter by specific app:
Advanced filtering (scale up only after filters work):
Custom time range (use sparingly - impacts quota):
💡 Quota-Conscious Tips
Always filter by app when 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 window unless you need wider historical data
🔐 Security / Secrets
Never commit (it contains your
MEZMO_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.
🛠️ Commands
🐛 Troubleshooting
Container won't start?
Check your
.envfile hasMEZMO_API_KEY=your_actual_keyView logs:
docker-compose logs
Can't connect from MCP client?
Ensure container is running:
docker-compose psRestart your MCP client after configuration changes
That's it! The server runs on port 18080 and automatically handles time windows, retries, and error handling.