Add ability to query alertmanager

[tiny-pangolin]

I'm using the Victoriametrics MCP-server to query the current alerts in my environment, and it is correctly showing all alerts that are in a firing state, but it does not take into account silenced or inhibited alerts since the MCP server is unable to query alertmanager.

[Amper]

Hey @tiny-pangolin.

The problem is that for the vmalert API, VictoriaMetrics instances proxy with the -vmalert.proxyURL flag, but there is no same feature for Alertmanager in VictoriaMetrics.

Therefore, to implement such a feature in MCP VictoriaMetrics we have two options:

• Implement something like -alertmanager.proxyURL in VictoriaMetrics (in this case you should discuss it with the guys on your meetings)
• Add separate parameter to MCP with Alertmanager entrypoint and add Alertmanager API support. But I think it doesn't make sense because it's the same as a separate MCP Alertmanager that already exists.

What do you think about it?

[tiny-pangolin]

I'll test query results with both the alertmanger mcp and Victoriametrics mcp servers enabled and if that works would we just add a note in the readme about integrating with alertmanger. I think it would be great to have the alert show as silenced in vmalert UI but that is much bigger change than adding a second mcp server and updating docs.

[tiny-pangolin]

I was able to use the alertmanager-mcp-server along with the Victoriametrics mcp server to query silences