Skip to main content
Glama
debugging.md962 B
# Debugging ## MCP Inspector You can interactively test the MCP server using the official inspector: ```bash npx @modelcontextprotocol/inspector ``` Then open the URL it prints (e.g., http://localhost:5173) and connect: - Transport: STDIO - Command: `prometheus-mcp` - Args (optional): `--mcp --prometheus-url http://localhost:9090` Click Connect, then use the Tools tab to list and call the Prometheus tools. ::: tip If the inspector can’t connect, try running the binary directly in a separate terminal to confirm it starts without errors. ::: ## Logs The process appends JSON-RPC request/response lines to `/tmp/mcp.jsonl`. ```bash tail -f /tmp/mcp.jsonl ``` ## Common issues ::: warning - Connection refused: verify `--prometheus-url` and network reachability (Docker vs host networking). - 401/403 from Prometheus: configure Basic Auth via env or flags. - Time format: prefer RFC3339 (e.g., 2025-09-27T12:00:00Z) or Unix epoch seconds. :::

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/brenoepics/prometheus-rs'

If you have feedback or need assistance with the MCP directory API, please join our Discord server