hwp-live-safe
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HWP_LIVE_PROFILE_DIR | No | Legacy environment variable for the profile directory, accepted for migration from the pre-release project name. Still honored if HWP_LIVE_SAFE_PROFILE_DIR is not set. | |
| HWP_LIVE_SAFE_PROFILE_DIR | No | Path to a local directory containing profile files. Overrides the default profile directory. The older HWP_LIVE_PROFILE_DIR is accepted for migration. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hwp_statusA | Check whether the local Hancom 2022 automation bridge is ready. This does not launch Hancom, edit a document, or access a user file. |
| hwp_start_new_documentA | Launch Hancom and create a brand-new unsaved document owned by HWP Live. It never attaches to or changes an already-open user document. |
| hwp_read_contextA | Read text from HWP Live's current unsaved document and return its revision. |
| hwp_profile_listA | List configured local profile keys without returning any profile value. This does not open Hancom, read a document, or write a profile. It only exposes profile/key labels and whether each value is configured. |
| hwp_preview_profile_insertA | Preview inserting one local profile value at the current HWP Live caret. Values stay inside the local server and are not returned in the preview. First call hwp_read_context, place or confirm the visible caret, then ask for approval before applying the returned plan. |
| hwp_preview_editsA | Create a 60-second, non-mutating preview for text or table insertions. Call hwp_read_context first and pass its revision. Show the preview and obtain the user's approval before calling hwp_apply_preview. |
| hwp_apply_previewA | Apply exactly one fresh preview to the visible, automation-owned document. |
| hwp_undo_lastB | Undo HWP Live's immediately preceding change if the document is unchanged. |
| hwp_foreground_statusA | Show the experimental foreground-typing session state without touching Hancom. |
| hwp_foreground_list_windowsA | List visible Hancom window titles for an explicit experimental typing choice. This does not read document text or edit anything. Window titles can reveal file names, so call it only when the user asks to target an already-open Hancom window and is comfortable identifying it. |
| hwp_foreground_select_windowA | Select one short-lived Hancom-window candidate for foreground typing. This does not activate or edit the window. The user must explicitly identify the desired listed window and active tab before it is selected. |
| hwp_foreground_preview_textA | Preview literal text typed at a user-confirmed caret in the selected window. The mode cannot read the document or verify selection state. Set user_confirms_collapsed_caret true only after the user explicitly confirms that the intended Hancom tab has one collapsed caret, not selected text. |
| hwp_foreground_preview_profile_insertB | Preview a local profile value typed at a user-confirmed foreground caret. The profile value is resolved only inside the local server and is never included in the MCP response. This is experimental and has no automatic document read-back or Undo. |
| hwp_foreground_apply_previewA | Activate the selected Hancom window and type exactly one fresh foreground preview. This never saves or closes a document. It has no read-back or automatic Undo, so use it only after the user has approved the preview. |
| hwp_foreground_disconnectB | Forget the selected foreground window without changing Hancom. |
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 15 tools
The hwp_ foreground prefix cleanly separates the experimental foreground-typing flow from the normal HWP Live document flow, and each tool corresponds to a distinct lifecycle step. Some confusion is possible among the several preview/apply tools, but the descriptions and prefixes make the boundaries clear enough.
All tools share the hwp_ prefix and snake_case, giving a coherent namespace, but the internal convention varies: verb-first names like read_context and apply_preview mix with noun-first names like profile_list and foreground_status. Some compound names such as preview_profile_insert and foreground_preview_profile_insert are awkward and not consistently verb_noun.
15 tools is at the upper end of the well-scoped range, and each tool represents a distinct state transition or query for either the normal or foreground workflow. Despite the two parallel modes, no tool feels redundant.
The core safe document workflow is well covered: start, read, preview, apply, and undo, plus experimental foreground operations and profile-value insertion. Obvious gaps like saving or closing documents and managing profile values are absent, but the safety-focused design appears to intentionally exclude them.