JumpServer MCP integration for AI agents.
Connect AI agents to JumpServer through 6 structured actions, including accounts accounts list, assets assets list, and assets nodes list. Review authenticat…
- ACTION CONTRACTS
- 6
- AUTHENTICATION
- Custom credentials
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the JumpServer integration exposes
The JumpServer Agent App exposes 6 provider-backed actions for developer tools, infrastructure, and security work. Its current contract lets an authorized agent list managed accounts visible to the configured jumpserver token, list assets visible to the configured jumpserver token, with optional pagination and search, and list asset nodes visible to the configured jumpserver token. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses Custom credentials. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected JumpServer account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real JumpServer capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
accounts_accounts_listREADList managed accounts visible to the configured JumpServer token.
INPUTS: limit / offset / search
assets_assets_listREADList assets visible to the configured JumpServer token, with optional pagination and search.
INPUTS: limit / offset / search
assets_nodes_listREADList asset nodes visible to the configured JumpServer token.
INPUTS: limit / offset / search
perms_asset_permissions_listREADList asset permission rules visible to the configured JumpServer token.
INPUTS: limit / offset / search
terminal_sessions_listREADList historical and active terminal sessions visible to the configured JumpServer token.
INPUTS: limit / offset / search
users_users_listREADList JumpServer users visible to the configured token.
INPUTS: limit / offset / search
INPUT CONTRACTS
Know what the action needs before it runs.
accounts_accounts_list
limitOPTIONAL- Maximum number of records to return.
offsetOPTIONAL- Number of records to skip before returning results.
searchOPTIONAL- Search text applied to fields supported by this JumpServer resource.
assets_assets_list
limitOPTIONAL- Maximum number of records to return.
offsetOPTIONAL- Number of records to skip before returning results.
searchOPTIONAL- Search text applied to fields supported by this JumpServer resource.
assets_nodes_list
limitOPTIONAL- Maximum number of records to return.
offsetOPTIONAL- Number of records to skip before returning results.
searchOPTIONAL- Search text applied to fields supported by this JumpServer resource.
perms_asset_permissions_list
limitOPTIONAL- Maximum number of records to return.
offsetOPTIONAL- Number of records to skip before returning results.
searchOPTIONAL- Search text applied to fields supported by this JumpServer resource.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Accounts Accounts List
List managed accounts visible to the configured JumpServer token. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
accounts_accounts_listVerify with Assets Assets List
List assets visible to the configured JumpServer token, with optional pagination and search. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
assets_assets_listSAFETY BOUNDARY
Operate JumpServer with explicit limits
- Authorize JumpServer with Custom credentials and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned JumpServer data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in JumpServer rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the JumpServer task completed successfully.
CONNECTION MODEL
Custom credentials
JumpServer uses Custom credentials. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 6
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by JumpServer.