wrapguard-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WRAPGUARD_CONFIG | No | Path to a wrapguard.config.json file. Overrides default configuration. | |
| WRAPGUARD_HTTP_HOSTS | No | Comma-separated list of allowed hosts for the remote HTTP server. Must be set when running the remote MCP server. | |
| WRAPGUARD_HTTP_TOKEN | No | Token required to authenticate requests to the remote Streamable HTTP endpoint. Must be set when running the remote MCP server. | |
| WRAPGUARD_SERVER_NAME | No | Overrides the runtime MCP display name (serverName) from the config file. |
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 |
|---|---|
| server_infoA | Show the configured display name, safety policy, and supported languages. |
| audit_pageB | Render a page at multiple widths and report Korean/English mid-word wraps and forced source newlines. |
| detect_midword_breaksB | Return only concrete Korean/English wrap issues measured from grapheme geometry in the browser. |
| inspect_wrap_cssB | Inspect computed wrapping properties and same-origin matching CSS rules for one element. |
| suggest_wrap_fixB | Generate a minimal CSS rule for Korean, English, mixed prose, raw evidence, or code/URL content. |
| verify_wrap_regressionB | Audit a page and evaluate it against explicit error/warning thresholds for CI or release gates. |
| apply_wrap_fixB | Append an idempotent CSS rule. Dry-run is the default; real writes require allowWrites and an allowed root. |
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 7 tools
Most tools target distinct actions: detect, audit, inspect, suggest, apply, verify. The only real overlap is between detect_midword_breaks and audit_page, since both report wrap issues, but audit_page's multi-width rendering and forced-newline reporting help separate them.
Tool names mostly follow a clear verb_noun pattern like detect_, audit_, inspect_, suggest_, apply_, and verify_. The single deviation is server_info, which uses a noun phrase instead of a verb-based name, but the overall convention is consistent.
Seven tools is well-scoped for a focused Korean/English wrapping server. Each tool contributes to a clear workflow without excessive redundancy or an undersized surface.
The set covers the full lifecycle: audit/detect issues, inspect CSS, suggest fixes, apply fixes, and verify regressions. The main minor gap is the lack of an explicit undo/remove operation for applied wrap fixes.