About JumpServer MCP Server
JumpServer MCP Server connects to a JumpServer instance using its URL and optional API bearer token. The README documents Docker deployment and an SSE MCP endpoint for client configuration.
Key features
- 01JumpServer URL configuration
- 02Optional API bearer token
- 03Docker container startup
- 04SSE endpoint configuration
Use cases
- 01Run the server in a Docker container
- 02Configure a JumpServer API token
- 03Connect an MCP client over SSE
MCP support
Provides an SSE MCP endpoint at `/mcp` for clients, configured with a Bearer authorization header. The README does not specify which JumpServer operations are exposed.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
docker run -i --rm ghcr.io/leeeirc/jumpserver-mcp-server:latestLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
ghcr.io/leeeirc/jumpserver-mcp-server:lateststdioTools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEJumpServer MCP Server
Configure JumpServer Environment File (.env)
# Bearer token to access the JumpServer SWAGGER JSON API, optional
api_token=xxxxxxx
jumpserver_url=http://jumpserverhost
Start Docker Container
docker run -d -it -p 8099:8099 --env-file .env --name jms_mcp ghcr.io/leeeirc/jumpserver-mcp-server:latest
Create JumpServer API Bearer Token for MCP Server
TOKEN=$(curl -s -X POST http://jumpserver_host/api/v1/authentication/auth/ \
-H "Content-Type: application/json" \
-d '{
"username": "admin",
"password": "xxxx"
}' \
--insecure | jq -r '.token')
echo "Your Bearer token: $TOKEN"
MCP Server Configuration
{
"type": "sse",
"url": "http://127.0.0.1:8099/mcp",
"headers": {
"Authorization": "Bearer xxxxxxxx"
}
}
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.