Mezmo MCP exposes a remote Model Context Protocol server that lets AI assistants and IDE chat agents interact with the Mezmo observability platform. Through MCP, you can perform advanced root-cause analysis on recent logs, list and describe pipelines, and export logs using Mezmo's powerful query syntax. Clients can connect via MCP to issue tool calls like runRootCauseAnalysis, listPipelines, describePipeline, and exportLogs against your Mezmo instance. The server acts as a bridge between MCP clients and Mezmo services, enabling analyses and data retrieval without requiring direct user interaction with the Mezmo UI.

To use it, connect your MCP client to the Mezmo MCP server endpoint, authenticate with the provided tokens or environment-based credentials, and invoke the available tools. Root-cause analysis helps trace errors or incidents across recent logs, pipeline tooling enables discovery and inspection of pipelines, and the logs export tool provides filtered log retrieval for downstream processing or reporting.

Prerequisites:

• Node.js v14+ installed on your system
• npm or yarn for package installation
• Access credentials for Mezmo (API token, organization ID, project ID)

Installation steps:

1. Clone the repository or obtain the Mezmo MCP server package: git clone https://github.com/your-org/mezmo-mezmo-mcp.git cd mezmo-mezmo-mcp

2. Install dependencies: npm install

   or

   yarn install

3. Configure environment variables (see env vars below) or add a .env file with the required values.

4. Start the server: npm start

   or the equivalent node command if you run directly

5. Verify the server is running by connecting your MCP client to the endpoint and issuing a simple tool call, such as listing pipelines.

Optional: If you prefer Docker, build and run a container with the same environment variables and exposed port as documented in the Mezmo MCP docs.

Environment variables: MEZMO_API_TOKEN, MEZMO_ORG_ID, MEZMO_PROJECT_ID are required for authenticating with Mezmo. Ensure these are kept secure and not committed to version control.

Common issues:

• Node version mismatches: ensure you’re using Node.js 14+. Upgrade if necessary.
• Authentication failures: verify API token and IDs are correct and have required permissions.
• Network access: ensure outbound access to Mezmo APIs is allowed from your host or container.

Configuration tips:

• You can extend the env block with additional Mezmo endpoints or feature flags as described in the official Mezmo MCP documentation.
• If you need to run multiple MCP servers, add additional entries under mcpServers with unique keys.