AiJumpOps MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JMS_URL | Yes | The base URL of the JumpServer instance. | |
| JMS_PASSWORD | No | JumpServer password for username/password authentication. | |
| JMS_USERNAME | No | JumpServer username for username/password authentication. | |
| JMS_TOTP_SECRET | No | Optional TOTP secret for automatic RFC 6238 two-factor authentication code generation. | |
| JMS_ACCESS_KEY_ID | No | Access key ID for HTTP Signature (httpsig) authentication. | |
| JMS_PRIVATE_TOKEN | No | Static private token for JumpServer authentication. | |
| JMS_ACCESS_KEY_SECRET | No | Access key secret for HTTP Signature (httpsig) authentication. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jms_overviewA | Get a complete overview of JumpServer (detected API version, total/active assets, nodes, users, MFA coverage, permission rules, and live terminal sessions). |
| jms_auth_otpA | Complete a pending 2FA/TOTP authentication challenge when JumpServer returns MFA_OTP_REQUIRED, using the 6-digit code provided by the user. |
| jms_assets_listB | List or search JumpServer assets (servers/hosts) with their IP addresses, platform, protocols, nodes, and active status. |
| jms_asset_inspectA | Inspect a specific JumpServer asset (by name, partial name, IP, or ID), listing its available system accounts (e.g. root, ubuntu) and all permission rules granting access to it. |
| jms_asset_createA | Register/create a new server asset in JumpServer. Always call with confirm=false first to preview and ask user confirmation! |
| jms_nodes_listC | List JumpServer asset tree nodes (e.g. /Default/Production, /Default/Staging) and asset counts. |
| jms_users_listB | List or search JumpServer users with their username, email, role, groups, active status, and 2FA/MFA status. |
| jms_user_groups_listC | List all JumpServer User Groups and member counts. |
| jms_user_actionA | Inspect a user's permissions, or perform a user lifecycle action (enable, disable, add-to-group, remove-from-group, create). For mutating actions, ALWAYS call with confirm=false first! |
| jms_permissions_listA | List JumpServer AssetPermission (authorization) rules, optionally filtered by user, asset, or search query. |
| jms_check_accessA | Check whether a specific JumpServer User currently has access to a specific Asset, and show which permission rules, accounts (e.g. root, ubuntu), and actions apply. |
| jms_permission_grantA | Grant a JumpServer User (or User Group) access to an Asset (or Node). Always run with confirm=false first to preview available accounts on the asset, ask the user which account (root/ubuntu/@ALL), actions (connect/transfer/all), and expiry duration they want, and only set confirm=true after explicit user approval. |
| jms_permission_revokeA | Revoke a user's access to an asset, or delete an entire AssetPermission rule. Always call with confirm=false first to preview affected rules! |
| jms_sessions_activeB | List currently active live SSH/RDP terminal sessions on JumpServer, or terminate a live session (with confirm=true after preview). |
| jms_audit_logsB | Query JumpServer security audit logs: executed shell commands ('commands'), user login events ('logins'), historical terminal sessions ('sessions'), or admin changes ('operations'). |
| jms_security_auditA | AI Security Auditor: Scan JumpServer for users without 2FA/MFA, overprivileged permission rules (e.g. @ALL or root across broad nodes), expired rules, and unassigned assets. |
| jms_backupA | Create a full JSON snapshot backup of all JumpServer AssetPermission rules and user states before making changes. |
| jms_revertA | Revert JumpServer AssetPermission rules back to a backup snapshot. Always call with confirm=false first to preview the exact diff! |
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 18 tools
Most tools map to a distinct resource plus action (assets, users, groups, permissions, sessions, audit, backup). Minor overlap exists between jms_asset_inspect (which lists permission rules for an asset) and jms_check_access (which checks a user-asset pair), and the 'audit' pair jms_audit_logs vs jms_security_audit requires reading descriptions to separate scanning from log querying.
All names share the jms_ prefix and snake_case, but the ordering convention flips between noun-first listers (jms_assets_list, jms_users_list, jms_permissions_list) and noun_verb commands (jms_asset_create, jms_permission_grant, jms_check_access). Singular/plural also drifts (jms_assets_list vs jms_asset_inspect, jms_permissions_list vs jms_permission_grant), though everything stays readable.
18 tools is on the heavy side for one server, but the domain genuinely spans assets, users, permissions, sessions, audit, and backup/restore, and each tool has a distinguishable job. No obvious filler tools inflate the count.
The lifecycle is well covered: list/inspect/create assets, grant/revoke permissions, session termination, audit queries, and backup/revert safety net. Gaps remain around asset update/delete, node creation, and editing an existing permission rule rather than revoke-and-regrant, but these are workable via the exposed tools.