Hatz AI vs LiveAgent
Side-by-side trajectory, velocity, and editorial themes.
Hatz AI is building the AI workspace for MSPs — per-message model routing, tenant tooling, custom MCP.
Hatz AI is shipping at a high cadence across three connected themes. First, model routing: Auto-LLM picks the right model per message based on task and tools, then layered into Lite, Performance, and Turbo tiers; the catalog keeps adding models (Opus 4.7, Gemini 3.5 Flash, Gemini 3.1 Flash Lite, Gemma 4) with per-model credit multipliers surfaced in the UI. Second, MSP control plane: bulk tenant creation via CSV, custom roles with credit limits, workshop access controls, and embedded support chat in the admin dashboard. Third, surface expansion: audio uploads with auto-transcription, image generation in workflows, file output attaching to chats, 60+ supported file types, speech-to-text in chat, and a steady cadence of integrations and custom MCP server improvements.
The product is taking shape as a multi-tenant AI workspace tuned for MSPs and partner-led delivery — the tenant CSV, credit limits, and workshop sharing are unusual for a generalist AI tool and tell you who buys this. Auto-LLM and tiered routing make sense in that context: an MSP needs cost control across many tenants without micromanaging model picks. Custom MCP and the broad integration cadence position Hatz as a tools-aggregator over multiple LLMs rather than a model wrapper.
Expect more MSP-centric controls — per-tenant budgets, white-label theming, billing reconciliation — and Auto-LLM to grow visible routing telemetry so MSP admins can see why a given model was picked. The custom MCP surface is likely to evolve toward a marketplace pattern with shareable MCP packages across tenants.
LiveAgent wires its ticketing engine into the Claude ecosystem via MCP.
LiveAgent is in dense maintenance mode — multiple version trains and a backport branch all shipping fixes and security patches almost daily — but the AI integration thread has sharpened. The 5.64 release adds an AI Agent Work Distributor for tickets, a new add_note MCP tool, and OAuth 2.1 on the MCP server with the explicit goal of letting claude.ai connect as a custom connector. Earlier May releases switched the MCP protocol to Streamable HTTP and renamed MCP tokens for clarity.
The product is positioning MCP as its core integration substrate. Each release adds another MCP refinement — protocol upgrade, naming cleanup, ticket-level AI work distribution — pointing toward a model where Claude or any MCP-aware agent triages and acts on tickets natively. The parallel backport lines (5.62.x, 5.63.x) suggest the AI work is being layered on without forcing customers off the legacy install base.
Expect the AI Agent Work Distributor to grow into more autonomous resolution flows, with new MCP tools added incrementally (search, reply, escalate), and a more explicit Claude-Connector-ready posture in product marketing.
See more alternatives to Hatz AI →
See more alternatives to LiveAgent →