mcp-jumpserver
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JUMPSERVER_URL | Yes | The URL of the JumpServer instance, e.g. https://jumpserver.example.com | |
| JUMPSERVER_ORG_ID | No | The organization UUID in JumpServer, if required. Optional. | |
| JUMPSERVER_PASSWORD | Yes | The password for the JumpServer service account. | |
| JUMPSERVER_USERNAME | Yes | The username for a dedicated JumpServer service account with minimal permissions. | |
| JUMPSERVER_VERIFY_SSL | No | Whether to verify SSL certificates. Defaults to 'true'. Set to 'false' to disable verification. | true |
| JUMPSERVER_DATABASE_ASSETS | No | A JSON array of database asset names (e.g. '["DB-正式mysql-A", "DB-正式mysql-B"]') used by get_jumpserver_configured_database_credentials. Optional if you only use the single-asset tool. |
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 |
|---|---|
| test_jumpserver_loginA | Verify URL and username/password authentication without returning the API token. |
| list_jumpserver_databasesA | List JumpServer database assets. Optionally filter by name or address. |
| list_jumpserver_database_accountsA | List non-secret accounts for an exact database asset name, address, or UUID. |
| get_jumpserver_temporary_database_credentialA | Create temporary database proxy credentials like JumpServer's DB Guide page. The asset must be an exact name, address, or UUID. If multiple stored-secret accounts or database protocols are permitted, pass the account username/UUID and protocol explicitly. The returned connection.username and connection.password are short-lived plaintext credentials for the JumpServer database proxy, not the underlying database account secret. |
| get_jumpserver_configured_database_credentialsA | Create temporary proxy credentials for every configured database asset. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/wejack639/mcp-jumpserver'
If you have feedback or need assistance with the MCP directory API, please join our Discord server