AFK Mode
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AFK_PORT | No | HTTP/WebSocket server port | 7842 |
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 |
|---|---|
| get_current_web_app_urlA | Returns the connection URL and QR code for the AFK Mode web app. Call this when the user asks for the AFK app link or QR code. |
| get_afk_statusA | Returns the current AFK mode status. Call this before every interaction to decide whether to route through AFK MCP tools or native chat. If afkMode is true and clientConnected is true, route through notify_session_progress / get_user_decision. If afkMode is true but clientConnected is false, fall back to native chat and warn the user. If afkMode is false, use native VS Code chat as usual. |
| notify_session_progressA | Sends a progress update to the connected mobile client. Only call this when AFK mode is active (afkMode: true and clientConnected: true). Returns immediately. Use category 'milestone' for significant steps, 'error' for failures, 'info' for routine updates. |
| get_user_decisionA | Sends a decision request to the mobile client and blocks until the user responds or timeout expires. Only call when AFK mode is active. Use type 'confirm' for yes/no, 'choice' for selecting from options, 'text' for free-text input, 'diff' for approving code changes. |
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 4 tools
Each tool has a distinct and non-overlapping purpose: get_afk_status checks the operational mode, get_current_web_app_url provides connection details, get_user_decision handles user input, and notify_session_progress sends updates. There is no ambiguity in tool selection for an agent.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., get_afk_status, notify_session_progress). The naming is predictable and uniform across all four tools.
With 4 tools, the server is well-scoped for managing AFK mode interactions. Each tool serves a clear role in the workflow, and the count is appropriate without being excessive or insufficient for the domain.
The tool set provides complete coverage for the AFK mode domain: status checking, connection setup, user decision-making, and progress notifications. There are no obvious gaps, and the tools support a full lifecycle from setup to interaction.