{"serverInfo":{"name":"evlog MCP","homepage":"https://www.evlog.dev","documentation":"https://www.evlog.dev/reference/mcp"},"endpoints":[{"type":"streamable-http","url":"https://www.evlog.dev/mcp"}],"authentication":{"required":false},"capabilities":{"tools":{"listChanged":false},"resources":{"listChanged":false,"subscribe":false},"prompts":{"listChanged":false},"logging":{}},"tools":[{"name":"get-page","description":"Retrieves the full markdown of one evlog documentation page.\n\nWHEN TO USE: you know the exact path of the page. Common cases:\n- \"How do I install evlog?\" → /start/installation\n- \"What is a wide event?\" → /learn/wide-events\n- \"How do I add evlog to Nuxt?\" → /integrate/frameworks/nuxt\n- You found a path with list-pages and want the content\n\nWHEN NOT TO USE: you do not know the path yet. Call list-pages first.\n\nWORKFLOW: returns title, description, the full markdown, and the canonical URL. Paths have no locale prefix and no trailing .md."},{"name":"list-pages","description":"Lists every evlog documentation page with its title, path, description, and URL.\n\nWHEN TO USE: you need to find the page for a topic and do not know its path. Common cases:\n- \"Which frameworks does evlog support?\" → pages under /integrate/frameworks/\n- \"Where are the drains for Axiom or Sentry?\" → pages under /integrate/adapters/\n- \"How does evlog compare with pino?\" → /compare/pino\n- You want the shape of the docs before answering\n\nWHEN NOT TO USE: you already know the path, e.g. /start/installation. Call get-page directly.\n\nWORKFLOW: pick the relevant paths from this list, then call get-page on each one you need.\n\nOUTPUT: one entry per page:\n- title: page name\n- path: exact path for get-page\n- description: one-line summary\n- url: full URL"},{"name":"estimate-log-cost","description":"Estimates what a month of logs costs today against what the same traffic costs with evlog, which emits one wide event per request instead of one line per step.\n\nWHEN TO USE: someone asks whether evlog would lower their log bill, how much they would save at their traffic, or how consolidation compares against their provider's pricing.\n\nHOW IT WORKS: the byte counts are measured, not assumed. Serializing the same checkout request gives 184 B per pino line against 322 B for one evlog event, so consolidation removes duplicated envelope (level, timestamp, host, request bindings) rather than payload. Which figure moves a bill depends on the provider: most meter gigabytes, so the byte saving applies; a provider that also bills per million events indexed rewards the event count instead.\n\nPass a provider id to start from its published list rate, or pass perGb and perMillionIndexed directly. Rates were read on 14 August 2026 and vendors change pricing without notice, so an explicit rate always beats the stored one. Sampling is applied to both shapes through keepPercent, because any logger can drop events: it lowers each bill without changing the ratio between them."}],"resources":[],"prompts":[]}