kasm-use
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KASM_API_KEY | Yes | The API key | |
| KASM_API_URL | Yes | e.g. https://kasm.example.com | |
| KASM_USER_ID | Yes | The Kasm user sessions are created for | |
| KASM_USE_TOKEN | No | Bearer token clients must send (HTTP only). | |
| KASM_VERIFY_TLS | No | Set to false to accept a self-signed Kasm certificate. Default is true. | true |
| KASM_API_KEY_SECRET | Yes | The API key secret |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kasm_listB | List Kasm workspaces you can start and your running sessions. |
| kasm_startA | Start a Kasm workspace session (e.g. 'Chrome', 'Terminal') as the owner, so they can watch it. Takes ~2 minutes (it installs the input tool). Then call kasm_look. |
| kasm_lookA | Screenshot the Kasm session so you can see it. Always look before clicking, and look again after each action to confirm it worked. |
| kasm_clickB | Click at x,y in the coordinate space of the latest kasm_look image. |
| kasm_typeA | Type text into the focused field of the Kasm session. NEVER type passwords, MFA codes, or payment details — stop and ask the owner to take over the session for those. |
| kasm_keyC | Press keys/shortcuts in the Kasm session, e.g. 'ctrl+l', 'Return', 'Tab', 'Escape'. |
| kasm_scrollB | Scroll the Kasm session, optionally at x,y from the latest kasm_look image. |
| kasm_stopA | Stop (destroy) a Kasm session when the task is finished or the owner asks. |
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 8 tools
Each tool maps to a distinct session action: lifecycle management, visual inspection, clicking, scrolling, text entry, and key presses. kasm_type and kasm_key both provide keyboard input, but they are clearly separated by text entry versus special keys/shortcuts, so the overlap is minimal.
All eight tools follow the same kasm_ prefix followed by a short action-oriented name. This creates a predictable and readable naming convention with no mixed styles.
Eight tools is well-scoped for a remote Kasm session controller, covering lifecycle, observation, and basic input operations. Each tool serves a clear purpose in the interaction loop without obvious bloat.
The set covers starting, listing, and stopping sessions, plus screenshotting, clicking, scrolling, typing, and key presses, which supports many basic remote-control tasks. However, common UI interactions such as mouse move/hover, drag-and-drop, right-click, and clipboard/file transfer are missing, leaving minor gaps that an agent must work around.