Home › Cloud & Monitoring › llmxray
llmxray
What went wrong with your own Ollama calls, in sentences with the fix. Local, read-only.
Topics: Monitoring
Connect
Review any command before running it. Package names and URLs come from the server's own registry entry.
Package (npm 0.8.13)
npx -y llmxray@0.8.13
Or add to your MCP client config:
{
"mcpServers": {
"llmxray": {
"command": "npx",
"args": [
"-y",
"llmxray@0.8.13"
]
}
}
}
LLMXRAY_URL— The running LLMxRay server the tools read from (start it with `npx llmxray`).OLLAMA_URL— The Ollama daemon, for the list_local_models tool.
This server takes extra arguments — see its repository.
Related servers
Netdata
Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
Grafana
An MCP server giving access to Grafana dashboards, data and more.
Sentry
MCP server for Sentry - error monitoring, issue tracking, and debugging for AI assistants
homebutler
Tells an agent what changed on a server since it last looked - status, Docker, backups, Proxmox.
mpeirone/zabbix-mcp-server
Zabbix integration for hosts, items, triggers, templates, problems, data and more.
initmax/zabbix-mcp-server
Self-hosted Zabbix integration with 237 tools, multi-server monitoring, problem investigation, graphs, capacity forecasts, PDF reports,…
Listed in punkpeye/awesome-mcp-servers (MIT)
Data from the Official MCP Registry