MCP Container

mezmo-mcp

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.

GitHub

GitHub Stars

2

User Rating

Not Rated

Forks

0

Issues

0

Views

2

Favorites

0

README
Mezmo MCP

Mezmo MCP is a remote Model Context Provider (MCP) that lets AI assistants and IDE chat agents interact with the Mezmo platform via the Model Context Protocol.

Add Mezmo MCP and you can:

  • 📦 List and describe Pipelines
  • 📤 Export and filter Logs with powerful query syntax
  • 🕵️ Run advanced Root-cause analysis over recent logs
Table of Contents
Installation
Requirements
  • 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}"
Security

Mezmo MCP uses HTTPS for secure data transmission and requires authentication via Service Key. Customer data is encrypted in transit and not stored beyond 30 days (with options for archiving to your preferred cloud storage). Mezmo complies with standards like SOC 2 Type 2, GDPR, HIPAA, and PCI-DSS. For full details, see Mezmo's Compliance & Security page.

Client Configurations

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

Install in Cursor

Cursor natively supports remote MCP servers, so you only need a remote configuration.

Install MCP Server

Clicking the Install MCP Server badge opens Cursor and automatically adds the mezmo entry to your ~/.cursor/mcp.json with a placeholder for the Service Key. After it’s created, edit the file and replace <SERVICE KEY> with your actual Mezmo service key. Restart Cursor for changes to take effect. The final configuration should look like the example below.

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

Windsurf also supports remote servers via the serverUrl field.

{
  "mcpServers": {
    "mezmo": {
      "serverUrl": "https://mcp.mezmo.com/mcp",
      "headers": {
        "Authorization": "Bearer <SERVICE KEY>"
      }
    }
  }
}
Install in Trae 
{
  "mcpServers": {
    "mezmo": {
      "url": "https://mcp.mezmo.com/mcp",
      "headers": {
        "Authorization": "Bearer <SERVICE KEY>"
      }
    }
  }
}
Install in VS Code

VS Code’s Copilot Chat supports remote MCP servers with HTTP transport.

"mcp": {
  "servers": {
    "mezmo": {
      "type": "http",
      "url": "https://mcp.mezmo.com/mcp",
      "headers": {
        "Authorization": "Bearer <SERVICE KEY>"
      }
    }
  }
}
Install in Visual Studio 2022 
{
  "mcp": {
    "servers": {
      "mezmo": {
        "type": "http",
        "url": "https://mcp.mezmo.com/mcp",
        "headers": {
          "Authorization": "Bearer <SERVICE KEY>"
        }
      }
    }
  }
}
Install in Zed

Zed does not support remote URLs yet, so use the mcp-remote bridge.

{
  "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": {}
    }
  }
}
Install in Gemini CLI 
{
  "mcpServers": {
    "mezmo": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.mezmo.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer <SERVICE KEY>"
      }
    }
  }
}
Install in Claude Code

Claude Code supports remote URLs:

claude mcp add --transport http mezmo https://mcp.mezmo.com/mcp \
  --header "Authorization: Bearer <SERVICE KEY>"
Install in Claude Desktop 
{
  "mcpServers": {
    "Mezmo": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.mezmo.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer <SERVICE KEY>"
      }
    }
  }
}
Install in BoltAI 
{
  "mcpServers": {
    "mezmo": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.mezmo.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer <SERVICE KEY>"
      }
    }
  }
}
Install on Windows (cmd) 
{
  "mcpServers": {
    "mezmo": {
      "command": "cmd",
      "args": [
        "/c",
        "npx",
        "mcp-remote",
        "https://mcp.mezmo.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer <SERVICE KEY>"
      }
    }
  }
}
Install in Augment Code

Add a new MCP and enter:

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

Roo Code supports remote URLs:

{
  "mcpServers": {
    "mezmo": {
      "type": "streamable-http",
      "url": "https://mcp.mezmo.com/mcp",
      "headers": {
        "Authorization": "Bearer <SERVICE KEY>"
      }
    }
  }
}
Install in Zencoder 
{
  "command": "npx",
  "args": [
    "mcp-remote",
    "https://mcp.mezmo.com/mcp",
    "--header",
    "Authorization:${AUTH_HEADER}"
  ],
  "env": {
    "AUTH_HEADER": "Bearer <SERVICE KEY>"
  }
}
Install in Amazon Q Developer CLI 
{
  "mcpServers": {
    "mezmo": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.mezmo.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer <SERVICE KEY>"
      }
    }
  }
}
Install in Qodo Gen

Qodo Gen supports remote URLs:

{
  "mcpServers": {
    "mezmo": {
      "url": "https://mcp.mezmo.com/mcp",
      "headers": {
        "Authorization": "Bearer <SERVICE KEY>"
      }
    }
  }
}
Install in JetBrains AI Assistant 
{
  "mcpServers": {
    "mezmo": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.mezmo.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer <SERVICE KEY>"
      }
    }
  }
}
Install in Warp 
{
  "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
  }
}
Install in Opencode

Opencode supports remote URLs:

"mcp": {
  "mezmo": {
    "type": "remote",
    "url": "https://mcp.mezmo.com/mcp",
    "headers": {
      "Authorization": "Bearer <SERVICE KEY>"
    },
    "enabled": true
  }
}
Troubleshooting
1. npx argument-escaping bug

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>"
  }
}
2. Lost connection to the Mezmo MCP server

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.

Next Steps

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

  • list all my pipelines
  • show me details for pipeline <pipeline title>
  • export error logs from the last 30 minutes for app "my-app-frontend"
  • analyze my <app name> error logs with the query “tag:prod” from the last 30 minutes and determine root cause

Enjoy streamlined observability with Mezmo + AI! 🎉

Author Information
mezmo
mezmo
GitHub

0

Followers

0

Repositories

0

Gists

0

Total Contributions

Threads