AiJumpOps MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@AiJumpOps MCP Server Grant user mohammad access to app-prod-01 for 24 hours"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
🛡️🤖 AiJumpOps (jmsctl)
Universal AI-Native JumpServer Bastion / PAM Copilot — MCP Server, Agent Skill & Safe CLI Engine
دستیار هوشمند، تعاملی و ایمن مدیریت دسترسیها و سرورهای JumpServer (مبتنی بر MCP، Skill و خط فرمان)
🇬🇧 English Documentation • 🇮🇷 مستندات فارسی
🇬🇧 English Documentation
What is AiJumpOps?
AiJumpOps turns your AI coding & DevOps assistant (OpenCode, Claude Code, Claude Desktop, Cursor, Windsurf, or ChatGPT) into a Senior JumpServer PAM & Infrastructure Security Engineer.
Instead of clicking through nested JumpServer menus to find assets, accounts, user groups, and authorization rules, simply instruct your AI in natural language (English, Persian, or any language):
"Grant user
mohammadaccess to serverapp-prod-01for 24 hours""Check who currently has access to
db-masterand with which system accounts""Run a security audit on JumpServer to find users without MFA and overprivileged
rootrules""Show all active live SSH sessions right now and terminate any suspicious session"
"Take a full backup of all JumpServer permission rules before cleanup, and revert if needed"
✨ Key Differentiators & AI Safety Guardrails
Zero-Config JumpServer Version Auto-Detection (
v2/v3/v4):
Automatically detects whether your JumpServer runsv2(system-users) orv3/v4(accounts& host platform schemas) and adapts API payloads transparently.Smart Username/Password + 2FA/TOTP Authentication with Session Caching:
Supports Username & Password login out of the box.
2FA / TOTP Ready: Either provide
JMS_TOTP_SECRETin.envfor 100% zero-touch RFC 6238 TOTP generation, or let the AI prompt you interactively for your 6-digit Authenticator code (./jmsctl auth-otp --code 123456).Once authenticated, the session token/cookies are securely cached (
0600) so subsequent commands execute instantaneously without re-prompting for OTP.Also supports static
JMS_ACCESS_KEY_ID/JMS_ACCESS_KEY_SECRET(HTTP Signaturehttpsig) andJMS_PRIVATE_TOKEN.
Mandatory
PREVIEW_ONLYHuman-in-the-Loop Safety:
Every mutating operation (granting/revoking permissions, creating/deleting assets, enabling/disabling users, killing live sessions, reverting backups) runs in Preview Mode by default. The AI inspects available accounts on the server, asks you clarifying questions via interactive prompts, and only executes with--confirm(confirm=true) after your explicit approval.Instant Permission Snapshot Backup & 1-Click Diff Revert:
Snapshot allAssetPermissionrules and user states to JSON (./jmsctl backup), preview the exact drift diff (./jmsctl revert), and roll back changes in one command (./jmsctl revert --confirm).AI Security Auditor (
security-audit):
Automatically scans your JumpServer organization for active users without 2FA/MFA (especially Admins), overly broad@ALL/rootrules on root nodes, expired rules, and orphaned assets.
🚀 Quick Start
1. Clone & Install
git clone https://github.com/shariatissh/aijumpops.git
cd aijumpops
pip install -e .2. Configure Your JumpServer Connection
Option A: Interactive or Flag-based Setup
./jmsctl initOr non-interactively:
./jmsctl init \ --url "https://jumpserver.example.com" \ --username "admin" \ --password "your_password"Option B: Copy
.env.examplecp .env.example .env chmod 600 .env # Edit .env and set JMS_URL, JMS_USERNAME, JMS_PASSWORD (and optional JMS_TOTP_SECRET)
3. Verify Authentication (and 2FA/TOTP if enabled)
./jmsctl auth-check
# If MFA_OTP_REQUIRED is returned and JMS_TOTP_SECRET is not set:
./jmsctl auth-otp --code 123456🤖 AI Integrations (MCP & Skills)
1. One-Command Auto-Installer (OpenCode & Claude Code)
./install.sh2. Model Context Protocol (MCP) — 17 Built-in Tools
aijumpops_mcp.py is a zero-dependency stdio JSON-RPC 2.0 MCP Server exposing 17 tools:
jms_overview,jms_auth_otpjms_assets_list,jms_asset_inspect,jms_asset_create,jms_nodes_listjms_users_list,jms_user_groups_list,jms_user_actionjms_permissions_list,jms_check_access,jms_permission_grant,jms_permission_revokejms_sessions_active,jms_audit_logs,jms_security_auditjms_backup,jms_revert
Add to OpenCode (~/.config/opencode/opencode.jsonc):
{
"mcp": {
"aijumpops": {
"type": "local",
"command": ["python3", "/absolute/path/to/aijumpops/aijumpops_mcp.py"],
"enabled": true
}
}
}Add to Claude Desktop / Cursor (claude_desktop_config.json):
{
"mcpServers": {
"aijumpops": {
"command": "python3",
"args": ["/absolute/path/to/aijumpops/aijumpops_mcp.py"]
}
}
}🛠️ Complete CLI Reference (./jmsctl)
Category | Command | Description |
Setup & Auth |
| Interactive or flag-based |
| Verify authentication, cached session, and auto-detected API version ( | |
| Complete interactive 2FA/TOTP challenge and cache session | |
Overview |
| Summary of assets, nodes, users, MFA coverage, permissions, and live sessions |
| List all JumpServer organizations | |
Assets & Nodes |
| List or search server assets |
| Smart fuzzy search by hostname, IP, or UUID | |
| Inspect asset details, available system accounts, and matching permission rules | |
| Register a new server asset ( | |
| Delete an asset ( | |
| List asset tree nodes | |
Users & Groups |
| List users with role, groups, active status, and 2FA/MFA state |
| List user groups and member counts | |
| Inspect user details and all permission rules affecting them | |
| Enable or disable a user account ( | |
| Add or remove user from a User Group ( | |
| Create a new user ( | |
Permissions |
| List |
| Verify whether a user has access to an asset and via which accounts/rules | |
| Grant permanent or temporary access ( | |
| Revoke access or delete a permission rule ( | |
Sessions & Audit |
| List currently active live SSH/RDP terminal sessions |
| Kill/terminate a live terminal session ( | |
| Query executed shell commands, login logs, sessions, or admin logs | |
| Scan for users without MFA, overprivileged | |
Backup & Revert |
| Snapshot all permission rules and user states to JSON |
| Preview exact diff and roll back permission rules to backup snapshot | |
| View local chronological audit trail of confirmed changes |
Related MCP server: jumpserver-ssh-mcp
🇮🇷 مستندات فارسی
معرفی AiJumpOps
AiJumpOps یک کوپایلوت هوشمند و ایمن (AI-Native PAM & Bastion Copilot) برای JumpServer است که به مهندسین DevOps، مدیران سیستم و تیمهای امنیت اجازه میدهد سرورها (Assets)، کاربران، مجوزهای دسترسی (Asset Permissions)، سشنهای زنده و ممیزی امنیتی JumpServer خود را به زبان طبیعی (فارسی یا انگلیسی) در OpenCode، Claude (Desktop / Code)، Cursor و ChatGPT مدیریت کنند.
کافیست به دستیار هوش مصنوعی خود بگویید:
«دسترسی سرور
app-prod-01رو توی جامپسرور بده به کاربرmohammad»«چک کن ببین کاربر
aliبه سرورdb-masterدسترسی داره یا نه و با چه اکانتی؟»«الان چه کسانی سشن آنلاین SSH روی جامپسرور دارن؟»
«کل جامپسرور رو ممیزی امنیتی کن ببین کدوم یوزرها MFA ندارن و کدوم قوانین دسترسی بیش از حد باز هستن»
«قبل از تغییر دسترسیها یه بکاپ کامل بگیر تا اگه مشکلی پیش اومد سریع Revert کنیم»
🛡️ ویژگیهای کلیدی و لایههای امنیتی هوشمند
۱. تشخیص خودکار نسخه JumpServer (v2 / v3 / v4):
نیازی به تنظیم دستی نسخه API نیست؛ ./jmsctl بهصورت خودکار تفاوت ساختار نسخههای ۲ (system-users) و نسخههای ۳ و ۴ (accounts و hosts) را تشخیص داده و درخواستها را منطبق میکند.
۲. لاگین با یوزرنیم و پسورد + پشتیبانی کامل از کد دو مرحلهای (TOTP / 2FA) و کش سشن:
حالت اول (کاملاً خودکار بدون توقف): اگر کلید پایه
JMS_TOTP_SECRETرا در.envقرار دهید، کد ۶ رقمی TOTP به صورت خودکار در لحظه تولید و لاگین انجام میشود.حالت دوم (تعاملی): اگر
JMS_TOTP_SECRETتنظیم نشده باشد و روی اکانت شما MFA فعال باشد، دستیار هوشمند کد ۶ رقمی لحظهای را از شما میپرسد و با./jmsctl auth-otp --code 123456وارد میشود.کش هوشمند سشن: پس از یکبار لاگین، توکن و کوکی سشن با دسترسی امن
600کش میشود تا در دستورات بعدی نیازی به وارد کردن مجدد کد دو مرحلهای نباشد.
۳. حالت پیشنمایش اجباری (PREVIEW_ONLY) و جلوگیری از خطای انسانی:
هیچ دستور تغییردهندهای بدون فلگ --confirm اجرا نمیشود. برای مثال هنگام دادن دسترسی به یک سرور، دستیار ابتدا لیست اکانتهای موجود روی آن سرور (root, ubuntu, readonly, @ALL) را بررسی کرده و از شما میپرسد:
با کدام اکانت سیستم؟
چه مجوزهایی؟ (فقط اتصال
connect، انتقال فایلtransferیا دسترسی کاملall)دائمی یا موقت؟ (مثلاً ۲۴ ساعته یا ۷ روزه) و تنها پس از تایید نهایی شما دستور را اجرا میکند.
۴. پشتیبانگیری آنی و بازگردانی یککلیکی (backup & revert):
پیش از هر تغییر مهم، با ./jmsctl backup از تمام قوانین دسترسی و وضعیت کاربران اسنپشات JSON گرفته میشود و در هر زمان با ./jmsctl revert ابتدا تفاوتها (Diff) نمایش داده شده و با --confirm دقیقاً به حالت قبل بازگردانده میشود.
Available Tools
18 toolsjms_asset_createA
Register/create a new server asset in JumpServer. Always call with confirm=false first to preview and ask user confirmation!
Inputs: name (required), address (required), node, port, +4 more.
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.
Inputs: asset (required).
jms_assets_listB
List or search JumpServer assets (servers/hosts) with their IP addresses, platform, protocols, nodes, and active status.
Inputs: node, limit, search.
jms_audit_logsB
Query JumpServer security audit logs: executed shell commands ('commands'), user login events ('logins'), historical terminal sessions ('sessions'), or admin changes ('operations').
Inputs: days, user, asset, limit, +2 more.
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.
Inputs: code (required).
jms_backupA
Create a full JSON snapshot backup of all JumpServer AssetPermission rules and user states before making changes.
Inputs: label.
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.
Inputs: user (required), asset (required).
jms_nodes_listC
List JumpServer asset tree nodes (e.g. /Default/Production, /Default/Staging) and asset counts.
Inputs: search.
jms_overviewA
Get a complete overview of JumpServer (detected API version, total/active assets, nodes, users, MFA coverage, permission rules, and live terminal sessions).
Inputs: no named parameters.
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.
Inputs: days, node, user, asset, +7 more.
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!
Inputs: rule, user, asset, confirm, +1 more.
jms_permissions_listA
List JumpServer AssetPermission (authorization) rules, optionally filtered by user, asset, or search query.
Inputs: user, asset, limit, search.
jms_revertA
Revert JumpServer AssetPermission rules back to a backup snapshot. Always call with confirm=false first to preview the exact diff!
Inputs: file, confirm.
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.
Inputs: no named parameters.
jms_sessions_activeB
List currently active live SSH/RDP terminal sessions on JumpServer, or terminate a live session (with confirm=true after preview).
Inputs: user, asset, confirm, terminate_session_id.
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!
Inputs: name, user, email, group, +3 more.
jms_user_groups_listC
List all JumpServer User Groups and member counts.
Inputs: search.
jms_users_listB
List or search JumpServer users with their username, email, role, groups, active status, and 2FA/MFA status.
Inputs: group, limit, search.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Connect assistants to your company tools with per-person, per-action grants and a full audit log.
Connect AI assistants to your approved computer for files, commands, browser and desktop tasks.
- DNS-DATA RemoteDeprecatedcom.dns-data
Connect AI assistants to authorized Windows and macOS devices for files, commands, and management.
Connect AI assistants to explicitly paired computers, servers, and VMs for permitted remote actions.
Related MCP Servers
- AlicenseBqualityBmaintenanceProvides policy-driven, auditable SSH access to server fleets for AI assistants with zero-trust security controls, command whitelisting, and comprehensive audit logging to safely manage infrastructure.1330Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to securely execute remote commands via SSH or JumpServer, with flexible gateway configuration and plugin-based matchers for JumpServer login interfaces.2Apache 2.0
- AlicenseAqualityDmaintenanceEnables AI agents to execute commands on remote servers via SSH with dynamic host discovery through JumpServer and automatic username fallback.61MIT
- AlicenseBqualityDmaintenanceEnables AI tools to perform server operations such as log inspection, system monitoring, code management, Nginx and certificate management, with support for local and remote SSH modes and built-in security controls.2360 npmMIT