mcp-jumpserver
Provides tools for listing MySQL database assets and obtaining temporary credentials (username, password, host, port, database) from JumpServer, enabling secure connections to MySQL databases managed by JumpServer.
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., "@mcp-jumpserver Get temporary database credentials for all configured databases"
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.
mcp-jumpserver
JumpServer STDIO MCP for Codex. Automatically logs in with the JumpServer URL, username, and password and caches the API Token, so there is no need to create a Token manually.
Tools
test_jumpserver_login: Tests username/password login, does not return a Token.list_jumpserver_databases: Queries database assets.list_jumpserver_database_accounts: Queries accounts under an asset, does not return passwords.get_jumpserver_temporary_database_credential: Issues a temporary username and password for the database proxy, consistent with the "Database Connection Info" in the JumpServer Web terminal.get_jumpserver_configured_database_credentials: No parameters, issues temporary usernames and passwords for all database assets in the configuration array at once.
Related MCP server: Supabase MCP Server
Installation
uv syncIt is recommended to use a dedicated JumpServer user with least privilege, not a super administrator. Issuing temporary connection credentials requires that this user has login authorization for the target asset, account, and protocol; the approval or MFA policies of the login ACL still apply. This MCP does not provide a tool for reading static passwords of underlying accounts, nor does it require the accounts.view_accountsecret permission.
Configure Codex
codex mcp add jumpserver -- \
/absolute/path/to/mcp-jumpserver/.venv/bin/mcp-jumpserverYou can also write it into ~/.codex/config.toml:
[mcp_servers.jumpserver]
command = "/absolute/path/to/mcp-jumpserver/.venv/bin/mcp-jumpserver"
startup_timeout_sec = 20
tool_timeout_sec = 60
enabled = true
[mcp_servers.jumpserver.env]
JUMPSERVER_URL = "https://jumpserver.example.com"
JUMPSERVER_USERNAME = "codex-service-user"
JUMPSERVER_PASSWORD = "change-me"
JUMPSERVER_VERIFY_SSL = "true"
JUMPSERVER_DATABASE_ASSETS = '["DB-正式mysql-A", "DB-正式mysql-B"]'
# 可选:JUMPSERVER_ORG_ID = "组织 UUID"After configuration, restart this MCP in the Codex/ChatGPT desktop app, then call test_jumpserver_login.
Get Temporary Database Credentials
For daily use, call it directly without parameters:
调用 get_jumpserver_configured_database_credentialsThe credentials in the result are returned in configuration order; you must confirm errors is empty before consuming them. When you need to temporarily query an asset outside the configuration, call the single-asset tool with the exact asset name:
调用 get_jumpserver_temporary_database_credential:
{"asset":"DB-正式mysql-A","protocol":"mysql"}
调用 get_jumpserver_temporary_database_credential:
{"asset":"DB-正式mysql-B","protocol":"mysql"}The returned connection.username and connection.password are temporary credentials for the JumpServer database proxy; connection.host, connection.port, and connection.database form the full connection address. If an asset has multiple authorized accounts, first specify the username or UUID of account.
Security Notes
The Token is cached only in the MCP process memory and automatically re-logs in once upon receiving HTTP 401.
Logs and exceptions do not output the JumpServer password or Token.
The MCP only issues temporary credentials for the JumpServer database proxy and does not read static passwords of underlying database accounts.
get_jumpserver_temporary_database_credentialreturns short-lived plaintext connection credentials and should only be called with explicit user authorization.
Testing
uv run pytest
uv run ruff check .Available Tools
5 toolsget_jumpserver_configured_database_credentialsA
Create temporary proxy credentials for every configured database asset.
Asset names come from the JUMPSERVER_DATABASE_ASSETS JSON array. Callers must check that
errors is empty before consuming credentials. Each successful item contains short-lived
plaintext connection.username and connection.password values.
Inputs: no named parameters. Returns: object
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.
Inputs: asset (required), account, protocol. Returns: object
list_jumpserver_database_accountsARead-onlyIdempotent
List non-secret accounts for an exact database asset name, address, or UUID.
Inputs: asset (required), limit, search. Returns: object
list_jumpserver_databasesARead-onlyIdempotent
List JumpServer database assets. Optionally filter by name or address.
Inputs: limit, search. Returns: result
test_jumpserver_loginARead-onlyIdempotent
Verify URL and username/password authentication without returning the API token.
Inputs: no named parameters. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a distinct purpose: testing login, listing databases, listing accounts, and two credential-generation tools. The two credential tools differ by scope (single asset vs. all configured assets), which is clear from their descriptions, though they could still be confused at a glance.
All tool names follow a consistent verb_jumpserver_noun pattern using snake_case (test, list, list, get, get). The pattern is predictable and readable, with no mixing of conventions or vague verbs.
With 5 tools, the server is well-scoped for its purpose of managing and retrieving JumpServer database credentials. Each tool fills a clear role without excess or deficiency.
The set covers authentication verification, asset listing, account listing, and credential retrieval for single and bulk scenarios. Missing CRUD operations for databases or accounts are not central to the stated purpose, but a create/delete tool would round out the surface.
Maintenance
Related MCP Connectors
Manage remote servers, SSH terminals, files, databases and proxies with scoped access and approvals.
Scoped, audited SSH exec, sessions, and SFTP on your saved servers without exposing credentials
Issue, rotate and revoke scoped API-key passes for 25+ providers — the agent never sees a real key
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables secure interaction with Supabase databases via the PostgREST API, supporting full CRUD operations and stored procedure calls. It utilizes the Dedalus MCP framework to provide encrypted credential handling and just-in-time token exchange.4MIT
- AlicenseNot gradedqualityDmaintenanceProvides secure access to Supabase databases via PostgREST API and management tools for projects, schemas, branches, logs, and code generation.MIT
- FlicenseNot gradedqualityDmaintenanceEnables remote database access (RDBMS and MongoDB) through MCP tools, supporting read/write queries, schema management, and more.-
- FlicenseNot gradedqualityCmaintenanceEnables MCP clients to safely query one or more PostgreSQL databases with read-only tools and explicitly approved write operations.1-