Conversational Experience Router
Related Servers
Alternatives to Conversational Experience Router
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables product discovery, session-scoped carts, and confirmation-gated checkout through natural language, with deterministic routing and safety features.6 npmISC
- AlicenseNot gradedqualityCmaintenanceBehavioral governance layer for AI assistants that monitors for hallucination, inconsistency, and unsafe reasoning patterns while managing stateful AI sessions.10 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to register instances, send and receive persistent messages, and communicate across platforms and sessions using natural language commands.-
- AlicenseBqualityDmaintenanceEnables AI assistants to discover and control IoT devices on local networks and via Bluetooth LE.71MIT
- AlicenseNot gradedqualityBmaintenanceEnables personal AI agents to sense ambient attention cues, compute intent probabilities, and execute reversible guarded dry-run actions without prompting. It routes routine reflexes through a fast System-1 decision layer backed by decaying episodic memory and strict safety and privacy guardrails.7MIT
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.