Conversational Experience Router
Related Servers
Alternatives to Conversational Experience Router
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables product discovery, session-scoped carts, and confirmation-gated checkout through natural language, with deterministic routing and safety features.5 npmISC
- AlicenseNot gradedqualityBmaintenanceEnables an assistant to turn noisy speech into three confirmable action candidates, then execute only the user-selected candidate after a one-time nonce is verified through a paired device. It also records consent receipts and supports Alexa+ account linking and card-based interaction.MIT
- AlicenseNot gradedqualityCmaintenanceBehavioral governance layer for AI assistants that monitors for hallucination, inconsistency, and unsafe reasoning patterns while managing stateful AI sessions.26 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables a user's AI to exchange messages with people they already know and those people's AIs in DMs and group chats, handle routine communication, and flag only items needing attention. It supports OAuth sign-in and private invite-based connections without a directory or search.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables an Alexa+-style assistant to run household routines with cross-session memory of members, allergies, budgets, curfews and past decisions, autonomously re-planning when new observations contradict the original plan. It also serves card and carousel UI resources for screen detail and gates any spending behind an explicit spoken confirmation.Apache 2.0
- AlicenseAqualityCmaintenanceConnects conversational AI agents to live inventories of verified neighborhood retail stores through GPS-radius catalog search, zero-PII order reservations with direct merchant checkout links, real-time fulfillment tracking, and store trust reporting. Shoppers settle payment directly with merchants while orders trigger counter terminals and courier dispatch slips.241MIT
TDQS
Scored across 21 tools
Each tool targets a clearly distinct resource and action: experience discovery/launch/session lifecycle, public topic/room operations, moderation, consent, and context envelopes are well separated. While there are several discovery and creation tools, their descriptions make the boundaries explicit, so an agent can reliably choose the right one.
All 21 tools use consistent snake_case with a verb_noun pattern (e.g., discover_experiences, create_public_topic, get_public_room, launch_experience). The domain-specific prefixes like 'public' and 'experience' group related tools without breaking the predictable convention.
21 tools is on the heavy side for a single MCP server, falling into the 16–25 range that the rubric describes as borderline. While the surface covers multiple sub-domains (experiences, public rooms, moderation, consent), some tools could potentially be consolidated without losing functionality.
The experience lifecycle (discover, prepare, launch, continue, submit event, finish, consent status, revoke) and public interaction/moderation workflows are well covered. Minor gaps exist, such as no tool to update or delete public topics/messages, and context envelopes have only a create operation with no retrieval or management counterpart.