Hwip MCP Server
Officialby hwipit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HWIP_WS_URL | No | Deprecated. WebSocket endpoint for the hook-response fast path. `wsUrl` in ~/.hwip/config.json wins over it and is where the value belongs; this is read only when the file has none. Has to be a `ws://` or `wss://` URL without a space or `#fragment` | |
| HWIP_API_KEY | No | API key from Settings > API Keys. Only needed as an environment variable to override the credentials the server otherwise reads from ~/.hwip/config.json (written by `hwip install` / `hwip login`) — no env vars are needed at all if that file exists. An API key that cannot be sent as a header (a line break or another control character inside it, or a character no key has) stops the server at start, with a message saying where the key is set and nothing of the key; so does an `apiKey` in ~/.hwip/config.json that is not text | |
| HWIP_HOOK_ID | No | Hook ID (optional — only needed for `hwip_ask`). Can also come from `hookId` in ~/.hwip/config.json; the environment variable wins | |
| HWIP_BASE_URL | No | API base URL (default: https://api.hwip.app/v1). A base URL that answers with a redirect is refused (`REDIRECT_REFUSED`): requests that carry your API key never follow one | https://api.hwip.app/v1 |
| HWIP_DEVICE_ID | No | Default target device for `hwip_notify`, `hwip_clipboard` and `hwip_file` (each call's `targetDeviceId` wins). Omit to send to all devices. `hwip_ask` does not use it. Can also come from `deviceId` in ~/.hwip/config.json; the environment variable wins | |
| HWIP_SESSION_ID | No | Override the session id attached to pushes (grouping in the app). Auto-detected from the newest Claude Code transcript when unset | |
| HWIP_DISABLE_SESSION_CACHE | No | Set to `1`/`true` to skip writing the session-id handoff file under `~/.cache/hwip/`. Useful for read-only filesystems, ephemeral CI runners, or sandboxed envs that audit filesystem writes |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed