mcp-jumpserver-gui-sucks
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_JUMPSERVER_GUI_SUCKS_ORG_ID | No | Organization ID (optional, defaults to default org) | |
| MCP_JUMPSERVER_GUI_SUCKS_BASE_URL | Yes | Base URL of the JumpServer instance (e.g., https://jumpserver.example.com) | |
| MCP_JUMPSERVER_GUI_SUCKS_LOG_LEVEL | No | Log level (e.g., DEBUG, INFO, WARNING, ERROR) | |
| MCP_JUMPSERVER_GUI_SUCKS_STATE_DIR | No | Override for the state directory path | |
| MCP_JUMPSERVER_GUI_SUCKS_STATE_FILE | No | Override for the state file path | |
| MCP_JUMPSERVER_GUI_SUCKS_VERIFY_TLS | No | Whether to verify TLS certificates (set 'false' to disable) | true |
| MCP_JUMPSERVER_GUI_SUCKS_MAX_TERMINAL_SESSIONS | No | Maximum number of concurrent terminal sessions | 8 |
| MCP_JUMPSERVER_GUI_SUCKS_REQUEST_TIMEOUT_SECONDS | No | Timeout for HTTP requests in seconds | |
| MCP_JUMPSERVER_GUI_SUCKS_TERMINAL_IDLE_TIMEOUT_SECONDS | No | Idle timeout for terminal sessions in seconds | 3600 |
| MCP_JUMPSERVER_GUI_SUCKS_TERMINAL_REAP_INTERVAL_SECONDS | No | Interval between checks for idle terminal sessions in seconds | 30 |
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 |
|---|---|
| jms_pathsA | Show runtime environment keys and resolved state paths. |
| jms_statusA | Probe the local auth state and the current JumpServer session. |
| jms_terminal_usage_guideA | Return the recommended terminal workflow for coding agents using this MCP. |
| jms_sftp_usage_guideA | Return the recommended SFTP workflow and destructive-operation safety rules. |
| jms_profileA | Return the current JumpServer user profile. |
| jms_list_assetsB | List assets through the observed perms endpoint used by the current GUI. |
| jms_get_assetB | Fetch one asset detail through the observed perms endpoint. |
| jms_list_nodesA | List the observed JumpServer node tree exposed to the current user. |
| jms_list_connect_methodsA | List observed JumpServer connect methods, optionally narrowed to one protocol. |
| jms_get_asset_accessC | Summarize accounts, protocols, and connect methods available for one asset. |
| jms_resolve_terminal_targetC | Resolve user-facing asset and account references into the concrete IDs needed by terminal entrypoints. |
| jms_list_connection_tokensB | List active connection tokens without exposing the token secret value. |
| jms_create_connection_tokenC | Create a connection token using a concrete account ID or a user-facing account reference. |
| jms_expire_connection_tokenC | Expire one connection token explicitly. |
| jms_probe_koko_terminalC | Probe KoKo terminal access using a concrete account ID or a user-facing account reference. |
| jms_acquire_terminal_sessionB | Resolve a target and get or reuse one managed KoKo shell for that asset/account pair. |
| jms_refresh_terminal_authB | Refresh the persisted cookie-backed terminal session if it is still valid, or report that re-login is required. |
| jms_list_terminal_sessionsA | List active managed KoKo terminal sessions in the current MCP server process. |
| jms_send_terminal_inputC | Send raw input to a managed KoKo terminal session. |
| jms_read_terminal_outputC | Read buffered output from a managed KoKo terminal session until idle or timeout. |
| jms_run_terminal_commandC | Run one command through an already acquired managed KoKo shell. |
| jms_get_terminal_identityB | Verify and return the effective operating-system user in a managed shell. |
| jms_switch_terminal_userA | Switch to a verified remote user within the existing JumpServer shell. Use |
| jms_exit_terminal_userB | Exit one MCP-managed user shell and verify restoration of the previous user. |
| jms_interrupt_terminal_sessionC | Interrupt a running command in a managed KoKo terminal session. |
| jms_resize_terminal_sessionC | Resize a managed KoKo terminal session. |
| jms_close_terminal_sessionA | Close a managed KoKo terminal session and expire its underlying connection token. |
| jms_acquire_sftp_sessionC | Resolve a target and get or reuse one managed KoKo SFTP session. |
| jms_list_sftp_sessionsA | List active managed KoKo SFTP sessions in the current MCP process. |
| jms_sftp_statA | Return metadata for one absolute remote path. |
| jms_sftp_listC | List one absolute remote directory path. |
| jms_sftp_mkdirB | Create a remote directory, optionally creating missing parents. |
| jms_sftp_uploadA | Upload a local file; replacing a remote file requires overwrite=true. |
| jms_sftp_downloadA | Download a remote file; replacing a local file requires overwrite=true. |
| jms_sftp_renameA | Rename one remote entry without overwriting an existing sibling. |
| jms_sftp_deleteB | Delete an approved path; directories additionally require recursive=true. |
| jms_close_sftp_sessionA | Close one managed KoKo SFTP session and clean up its connection token. |
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 37 tools
Each tool maps to a distinct resource/action—asset discovery, token lifecycle, terminal session control, or SFTP operations—and even close pairs like probe vs acquire and send_input vs run_command have clearly separated scopes. No two tools appear interchangeable.
The jms_ prefix is used uniformly, and most tools follow a clear verb_noun pattern like list_, get_, create_, acquire_, and close_. A few noun-only names such as jms_paths, jms_status, jms_profile, and the two usage_guide tools break the verb convention, but the overall pattern remains predictable.
At 37 tools, the set exceeds the practical count threshold and will make agent tool selection heavier than necessary. The many terminal and SFTP operations are individually useful, but some session-control and usage-guide tools could have been consolidated.
The tool surface covers the full JumpServer workflow for coding agents: environment/profile discovery, asset and access lookup, connection-token lifecycle, managed KoKo terminal operations, and SFTP file handling. Cleanup operations like expire, close, and exit also prevent dead ends.