flow-router
Related Servers
Alternatives to flow-router
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server that answers typed noul/choice/score questions about a given state with probability distributions and confidence, for routing, escalation, and gating decisions. It runs on pluggable backends (local Needle 3 or Laya models, or any OpenAI-compatible endpoint) and logs every decision so recorded ground truth can be used to track calibration.3MIT
- AlicenseBqualityDmaintenanceA configurable MCP server that intelligently routes natural language queries to the appropriate microservice endpoint based on user-defined service configurations.85 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server that routes natural language requests to structured tool calls using a LoRA-tuned small language model, with built-in validation, retry, and fallback recovery.MIT
- AlicenseCqualityCmaintenanceAn MCP server that records the decision and categorisation steps inside agent workflows — inputs, choice and outcome — then serves confident decisions without an LLM call, routing uncertain ones to a hosted model and only training a private probe when reports show it's warranted. It reports agreement, coverage, savings, drift and hosted spend, and includes a drop-in gateway so pipelines making separate LLM classification calls can be answered without code changes.26MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to route multi-model AI agent steps through cost-aware tier selection, confidence-gated cascade escalation, circuit-breaker failover, semantic caching, and tenant/workflow budget enforcement. Exposes tools for routing, task complexity classification, endpoint health inspection, and budget status checks.MIT
- AlicenseAqualityDmaintenanceMCP server for a production-shaped service-business agent, enabling grounded knowledge search, intake collection, and human escalation with deterministic safety boundaries.3MIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong one. Its purpose—routing a Chinese request to a predefined flow, or abstaining—is unambiguous within itself.
The single tool 'route' is a clean, lowercase verb that accurately describes its action. With one name there is no convention mixing to penalize.
A router naturally collapses to one decision point, so the minimal surface is defensible rather than accidental. It is still thin overall—there are no supporting tools for inspecting the flow catalog the router chooses from.
The core decision operation exists, but there is no tool to list or describe the available predefined flows, so an agent cannot learn the valid targets or verify a returned flow id. This is a notable discoverability gap for a routing domain.