LidGuard: Skill for Codex

LidGuard MCP Runtime

Regular MCP Server

• Host the regular stdio MCP server through lidguard mcp-server.
• mcp-status inspects the provider's global/user MCP configuration and reports whether the lidguard server entry is present and still points at the current LidGuard executable plus mcp-server.
• mcp-install and mcp-remove register or remove the user/global LidGuard stdio MCP server named lidguard for Codex, Claude Code, GitHub Copilot CLI, and OpenCode.
• mcp-install refreshes an existing managed LidGuard MCP registration, including one that points at an older LidGuard executable, by removing the existing provider entry first, then reinstalling it with the current command and arguments.
• Windows WSL MCP management mirrors regular MCP management with WSL-side provider CLIs and config files, but the registered command must be the current Windows lidguard.exe converted through wslpath. Supported commands are wsl-mcp-status/install/remove [codex|claude|copilot|opencode|all] plus wsl-codex-mcp-*, wsl-claude-mcp-*, wsl-copilot-mcp-*, and wsl-opencode-mcp-* aliases.
• OpenCode MCP management edits the OpenCode JSON/JSONC config directly under the mcp object using a local command array instead of calling an OpenCode CLI registration command. OpenCode MCP status should only report the managed server as installed when the entry is type = local, not disabled, points at the current LidGuard executable, and contains mcp-server in the command array.
• Prefer the current lidguard.exe path over the Windows .cmd shim when registering stdio MCP servers, because shim wrapper processes can remain visible under MCP clients and should not be mistaken for agent work.
• Expose get_settings_status, list_sessions, update_settings, remove_session, set_session_soft_lock, and clear_session_soft_lock.
• Make list_sessions return the active session list plus runtime lid/session state without the full settings payload.
• Make update_settings accept multiple setting fields in a single request and persist them together.
• Expose inactive session timeout through sessionTimeoutMinutes, accepting off or an enabled minute count of at least 1.
• Expose server runtime cleanup delay through serverRuntimeCleanupDelayMinutes, accepting off to keep the runtime alive, 0 for immediate exit, or a positive minute count to wait.
• Expose post-session-end webhook URL through postSessionEndWebhookUrl, accepting an empty string to clear it.
• Expose the ask-before-sleep reply webhook URL through closedLidStopFollowUpWebhookUrl, accepting an empty string to clear it.
• Expose ask-before-sleep reply wait through closedLidStopFollowUpDelaySeconds, defaulting to 180; 0 disables reply waiting, and values 1 through 19 are saved but become configuration errors when the URL is configured.
• Expose ask-before-sleep reply wait sound through closedLidStopFollowUpSound, accepting off, an empty string, a supported system sound name, or a playable .wav path.
• Expose ask-before-sleep reply wait sound volume override through closedLidStopFollowUpSoundVolumeOverridePercent, accepting off or an enabled percent from 1 through 100.
• Expose repeated ask-before-sleep reply behavior through repeatClosedLidStopFollowUp, defaulting to true.
• Make remove_session manually remove active sessions by session identifier and optionally narrow removal to one provider and one MCP provider name.
• Keep set_session_soft_lock and clear_session_soft_lock general-purpose by accepting provider and session identifier inputs, so non-MCP providers can also use MCP-driven soft-lock control when they can supply those values.
• Use the same named-pipe client and settings store for MCP settings updates that the CLI uses.
• Do not launch run-server from MCP settings updates when no runtime is listening.
• Keep MCP server logging on stderr so stdio tool traffic remains clean.