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

• Mezmo MCP Server (Model Context Protocol)
  • Table of Contents
  • Overview
  • Available Tools & Examples
  • Best Practices
  • Installation
    • Requirements
  • Client Configurations
  • Troubleshooting
    • 1. npx argument-escaping bug
    • 2. Lost connection to the Mezmo MCP server
    • 3. 401/403 authentication errors
  • Next Steps

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.

• analyze_logs_for_root_cause_relative_time: analyze logs over a relative window
  • Example: analyze my logs from the last 30 minutes and determine root cause for any issues that you find
• analyze_logs_for_root_cause_time_range: analyze logs between specific timestamps
  • Example: analyze errors between 2025-01-01T10:00:00Z and 2025-01-01T11:00:00Z
• deduplicate_logs_relative_time: deduplicate similar logs over a relative window
  • Example: deduplicate error logs from the last hour for app "checkout-service"
• deduplicate_logs_time_range: deduplicate similar logs between specific timestamps
  • Example: deduplicate logs from 2025-01-01T10:00:00Z to 2025-01-01T11:00:00Z
• export_logs_relative_time: export raw logs over a relative window
  • Example: export error logs from the last 30 minutes for app "my-app-frontend"
• export_logs_time_range: export raw logs between specific timestamps
  • Example: export logs from 2025-01-01T10:00:00Z to 2025-01-01T11:00:00Z with level error
• list_pipelines: list all pipelines
  • Example: list all my pipelines
• get_pipeline: get details for a pipeline by ID
  • Example: show me details for pipeline <pipeline id>

• Start broad for root-cause analysis
  • If the query is too narrow, our RCA can't do its thing. Cast a wide net, and if needed, specify app/service/level in subsequent queries.
• Prefer analyze_logs_for_root_cause or deduplicate_log tools for insights
  • These tools deduplicate and groups similar logs for better summaries, allowing the results to fit into finite LLM context windows.
• Use relative time ranges
  • Prefer values like last_15_minutes, last_hour when supported.
• Keep prompts simple; add filters gradually
  • Add app, host, level, and query filters step by step.
• Use export_logs for raw data only
  • For dashboards or offline analysis, use export_logs; otherwise prefer RCA.

• A Mezmo Service Key (generate one in your Mezmo dashboard under Settings > API Keys; see Mezmo docs for details)
• Node.js ≥ 18 (only needed for clients that use the mcp-remote bridge)
• One of the supported MCP clients below

For every client we follow a simple rule:

1. Supports remote URL? → configure it with a url that points to https://mcp.mezmo.com/mcp and include the Authorization header.
2. StdIO-only client? → use the mcp-remote bridge:

AUTH_HEADER="Bearer <SERVICE KEY>" npx mcp-remote https://mcp.mezmo.com/mcp \
  --header "Authorization:${AUTH_HEADER}"

Expand a section below to see setup instructions for your preferred editor or tool.

{
  "mcpServers": {
    "mezmo": {
      "url": "https://mcp.mezmo.com/mcp",
      "headers": {
        "Authorization": "Bearer <SERVICE KEY>"
      }
    }
  }
}

{
  "mcpServers": {
    "mezmo": {
      "serverUrl": "https://mcp.mezmo.com/mcp",
      "headers": {
        "Authorization": "Bearer <SERVICE KEY>"
      }
    }
  }
}

{
  "mcpServers": {
    "mezmo": {
      "url": "https://mcp.mezmo.com/mcp",
      "headers": {
        "Authorization": "Bearer <SERVICE KEY>"
      }
    }
  }
}

"mcp": {
  "servers": {
    "mezmo": {
      "type": "http",
      "url": "https://mcp.mezmo.com/mcp",
      "headers": {
        "Authorization": "Bearer <SERVICE KEY>"
      }
    }
  }
}

{
  "mcp": {
    "servers": {
      "mezmo": {
        "type": "http",
        "url": "https://mcp.mezmo.com/mcp",
        "headers": {
          "Authorization": "Bearer <SERVICE KEY>"
        }
      }
    }
  }
}

{
  "context_servers": {
    "Mezmo": {
      "command": {
        "path": "npx",
        "args": [
          "mcp-remote",
          "https://mcp.mezmo.com/mcp",
          "--header",
          "Authorization:${AUTH_HEADER}"
        ],
        "env": {
          "AUTH_HEADER": "Bearer <SERVICE KEY>"
        }
      },
      "settings": {}
    }
  }
}

{
  "mcpServers": {
    "mezmo": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.mezmo.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer <SERVICE KEY>"
      }
    }
  }
}

claude mcp add --transport http mezmo https://mcp.mezmo.com/mcp \
  --header "Authorization: Bearer <SERVICE KEY>"

{
  "mcpServers": {
    "Mezmo": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.mezmo.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer <SERVICE KEY>"
      }
    }
  }
}

{
  "mcpServers": {
    "mezmo": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.mezmo.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer <SERVICE KEY>"
      }
    }
  }
}

{
  "mcpServers": {
    "mezmo": {
      "command": "cmd",
      "args": [
        "/c",
        "npx",
        "mcp-remote",
        "https://mcp.mezmo.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer <SERVICE KEY>"
      }
    }
  }
}

AUTH_HEADER="Bearer <SERVICE KEY>" npx mcp-remote https://mcp.mezmo.com/mcp \
  --header "Authorization:${AUTH_HEADER}"

{
  "mcpServers": {
    "mezmo": {
      "type": "streamable-http",
      "url": "https://mcp.mezmo.com/mcp",
      "headers": {
        "Authorization": "Bearer <SERVICE KEY>"
      }
    }
  }
}

{
  "command": "npx",
  "args": [
    "mcp-remote",
    "https://mcp.mezmo.com/mcp",
    "--header",
    "Authorization:${AUTH_HEADER}"
  ],
  "env": {
    "AUTH_HEADER": "Bearer <SERVICE KEY>"
  }
}

{
  "mcpServers": {
    "mezmo": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.mezmo.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer <SERVICE KEY>"
      }
    }
  }
}

{
  "mcpServers": {
    "mezmo": {
      "url": "https://mcp.mezmo.com/mcp",
      "headers": {
        "Authorization": "Bearer <SERVICE KEY>"
      }
    }
  }
}

{
  "mcpServers": {
    "mezmo": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.mezmo.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer <SERVICE KEY>"
      }
    }
  }
}

{
  "Mezmo": {
    "command": "npx",
    "args": [
      "mcp-remote",
      "https://mcp.mezmo.com/mcp",
      "--header",
      "Authorization:${AUTH_HEADER}"
    ],
    "env": {
      "AUTH_HEADER": "Bearer <SERVICE KEY>"
    },
    "working_directory": null,
    "start_on_launch": true
  }
}

"mcp": {
  "mezmo": {
    "type": "remote",
    "url": "https://mcp.mezmo.com/mcp",
    "headers": {
      "Authorization": "Bearer <SERVICE KEY>"
    },
    "enabled": true
  }
}

Some clients pass command-line arguments to npx without quoting spaces. This can split the Authorization header (e.g. Bearer and the token become separate arguments) and cause authentication failures.

Work-around: store the header in an environment variable and pass it without spaces:

{
  "command": "npx",
  "args": [
    "mcp-remote",
    "https://mcp.mezmo.com/mcp",
    "--header",
    "Authorization:${AUTH_HEADER}"
  ],
  "env": {
    "AUTH_HEADER": "Bearer <SERVICE KEY>"
  }
}

If your client shows an error such as “server disconnected” or stops responding to MCP commands:

1. Disable or remove the Mezmo MCP entry in your client settings.
2. Re-enable (or re-add) the same entry, or simply restart the client.

This forces the client to establish a fresh connection to the Mezmo MCP backend.

• Verify the Authorization header is present and formatted as Bearer <SERVICE KEY>.
• If using npx mcp-remote, prefer the environment variable approach to avoid splitting the header.
• Regenerate your Service Key in Mezmo and try again if issues persist.

Once your client is configured you can immediately run natural-language commands such as

• analyze my logs from the last 30 minutes and determine root cause for any issues that you find
• list all my pipelines
• show me details for pipeline <pipeline title>
• export error logs from the last 30 minutes for app "my-app-frontend"

Enjoy streamlined observability with Mezmo + AI! 🎉