About Mezmo MCP
Mezmo MCP is an MCP server published by mezmo in the Developer Tools category: mezmo MCP: A remote Model Context Provider (MCP) for AI assistants and IDEs to interact with the Mezmo observability platform—enabling pipeline management, log querying, and root-cause analysis via the Model Context Protocol. It has been installed 0 times through Conduid.
The repository has 5 stars and 3 forks, with the last commit 6 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.
Install
npx mezmo-mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Mezmo MCP
Powered by Claude · Grounded in docs
Security checks
- ·README presentNot checked yet.
- ·License declaredNot checked yet.
- ·Tests presentNot checked yet.
- ·Dependencies pinnedNot checked yet.
- ·No dynamic code executionNot checked yet.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
README
Mezmo MCP Server (Model Context Protocol)
Mezmo MCP is a remote Model Context Protocol (MCP) server that lets AI assistants and IDE chat agents interact with the Mezmo observability platform via the Model Context Protocol. Use it for streamlined observability, log analysis, and root-cause analysis in your favorite tools.
Add Mezmo MCP and you can:
- 🕵️ Run advanced Root-cause analysis over recent logs
- 📦 List and describe Pipelines
- 📤 Export and filter Logs with powerful query syntax
Overview
Mezmo MCP is a remote MCP server that connects AI assistants and IDE chat to Mezmo so you can run advanced root-cause analysis, discover pipelines, and export logs without hosting anything yourself. It's built for observability use cases and works across many popular MCP clients.
Documentation
For the latest documentation — including available tools, installation instructions, client configurations, best practices, and troubleshooting — visit the official docs:
README mirrored from the source repository 3 months ago. The original is authoritative.