Overview
What is JumpServer MCP Server?
JumpServer MCP Server is a Model Context Protocol server that connects to JumpServer via its Swagger JSON API. It enables large language model clients to interact with JumpServer resources using a Bearer token for authentication.
How to use JumpServer MCP Server?
Configure an environment file with jumpserver_url and optionally api_token, then run the Docker container using docker run -d -it -p 8099:8099 --env-file .env --name jms_mcp ghcr.io/jumpserver/mcp:latest. Configure the MCP client with SSE transport pointing to http://127.0.0.1:8099/sse and include an Authorization: Bearer <token> header.
Key features of JumpServer MCP Server
- SSE (Server-Sent Events) transport for real-time communication
- Bearer token authentication via JumpServer API
- Deployable as a lightweight Docker container
- Exposes JumpServer functionality through MCP tools
Use cases of JumpServer MCP Server
—
FAQ from JumpServer MCP Server
What prerequisites are needed to run JumpServer MCP Server?
A running JumpServer instance, a valid Bearer token (obtained via the JumpServer authentication API), and Docker to run the container.
How do I create a Bearer token for the server?
Send a POST request to http://jumpserver_host/api/v1/authentication/auth/ with username and password in JSON format, then extract the token field from the response.
What transport does JumpServer MCP Server use?
It uses SSE (Server-Sent Events) as the transport protocol, configured with the URL http://127.0.0.1:8099/sse and an Authorization header.
What environment variables are required?
The .env file should contain jumpserver_url (required) and optionally api_token for the Bearer token.
Is there any known limitation about data location?
Not specified in the README. Data resides in the configured JumpServer instance.
