Readable under load
The surface stays focused on timestamps, severity, stream, host, and message.
live tail // streams // HTTP + Syslog + OTLP + GELF // MCP + AI chat
Centralized logs for
engineering teams.
Ingest logs over HTTP or Syslog, route them into streams, and keep live traffic readable when production starts misbehaving.
Live tail
Readable rows
Named streams
Live demo capture
Fluxtail live tail showing active log rows in the product.
Analysis on the same stream
The same rows can move into analytics, alerts, MCP, and built-in AI chat.
One place for mixed sources
HTTP, Syslog, OTLP, GELF, and collector traffic all land in the same investigation loop.
Readable under load
Read incoming production traffic in a compact view that stays usable during incidents.
Named streams
Split noisy systems into clear streams so triage starts with useful boundaries.
HTTP, Syslog, OTLP, and GELF
Start with explicit receivers and protocol paths instead of hidden setup or black-box routing.
Query logs from AI tools
Connect Fluxtail through MCP and investigate logs from the AI tools your team already uses.
MCP server
Use Fluxtail from AI tools.
Connect the Fluxtail MCP server to MCP-compatible AI tools, log in once, then ask for recent errors, exceptions, or incident windows directly from chat.
Example setup
codex mcp add fluxtail --url https://mcp.fluxtail.io/mcp
codex mcp login fluxtail
After login, an MCP-compatible AI client can query Fluxtail directly instead of relying on copied logs or screenshots.
Example
use fluxtail and query logs for last 3 hrs in fluxtail stream, and find exceptions
Fluxtail queried the stream and found two exception clusters:
1. Timeout exceptions from the API gateway
2. Retry-limit exceptions from a background worker
Next step: pull the last 50 error logs around the busiest window.
Start with a real log stream.
Start free
Create a receiver and send one source.