Conversational Experience Router
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXPERIENCE_PORT | No | Set EXPERIENCE_PORT to pin the port for the localhost-only experience web server and public-topics HTTP API (default is 4317; if the port is taken, an available port is chosen automatically and returned in the launch_experience entrypoint field). | |
| EXPERIENCE_TRUSTED_KEYS | No | Set EXPERIENCE_TRUSTED_KEYS at runtime so public discovery can identify trusted publishers. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discover_experiencesB | 根据用户当前明确表达的意图，推荐可立即开始的体验模块。宿主应先准备授权并获得用户同意，再启动体验。 |
| list_public_modulesC | 展示本地注册表中的公开体验模块，包括版本、权限、风险、发布者和签名状态。 |
| discover_public_topicsB | 根据用户明确提供的兴趣发现公开话题；结果不包含私密匹配或自动私信。 |
| create_public_topicC | 创建一个公开话题。发布前应向用户展示公开可见范围和内容审核规则。 |
| join_public_roomC | 按需加入某个公开话题的讨论房间；房间只支持公开发言，不开启私信。 |
| get_public_roomB | 读取一个公开讨论房间及当前可见消息。被拉黑的参与者内容不会返回。 |
| post_public_messageB | 在公开讨论房间发言。内容会进入公开审核队列，当前不提供私信。 |
| report_public_contentB | 举报公开话题或公开消息；举报进入审核队列，不会自动将内容判定为违规。 |
| list_public_reportsC | 读取本地公开内容审核队列，供明确授权的审核者处理。 |
| review_public_reportC | 由审核者对公开内容举报作出驳回、隐藏或恢复决定。 |
| block_public_actorB | 隐藏指定参与者在公开话题和房间中的内容，并阻止双方继续互动。 |
| unblock_public_actorC | 恢复查看和参与指定公开参与者内容的能力。 |
| create_context_envelopeB | 把用户明确选择共享的兴趣、时间和内容片段封装为可迁移的 Context Envelope。它不读取宿主的完整历史记录。 |
| prepare_experience_launchA | 为用户选择的体验模块生成一次性、限时授权请求。宿主应先向用户展示权限范围，得到明确同意后再调用 launch_experience。 |
| launch_experienceA | 使用 prepare_experience_launch 返回的一次性授权令牌启动体验，并创建一个有状态的本地会话。 |
| continue_experienceA | 读取体验会话的当前状态，用于在对话或网页之间继续一次体验。 |
| submit_experience_eventC | 向有状态的体验提交一个受限事件，例如答案、提示请求或重新开始。 |
| finish_experienceC | 结束一个体验会话并返回最终状态。 |
| get_consent_statusB | 查询一次体验授权的当前状态、模块和权限范围，不返回 bearer token。 |
| revoke_consentC | 撤销尚未使用的体验授权。已使用的会话不会被此工具伪装成未使用。 |
| create_experience_draftB | 用安全的声明式模板生成一个私人体验草稿。草稿只描述能力和边界，不执行用户提供的代码。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.