home / mcp / ludusmcp mcp server
Provides a Model Context Protocol server to manage Ludus lab environments via natural language prompts and tool support.
Configuration
View docs{
"mcpServers": {
"darkstar326-ludusmcp": {
"command": "ludus-mcp",
"args": []
}
}
}You run an MCP server locally to manage Ludus lab environments through natural language commands. This server hosts the Model Context Protocol integration, enabling your MCP client to securely access Ludus capabilities from your workstation.
Start your MCP client (for example Claude Desktop). The client automatically launches the Ludus-MCP server, loads credentials from your OS credential store, fetches latest configurations and schemas, tests connectivity to the Ludus server, and then enables tool communication through the MCP protocol. You can perform range management, configuration changes, and Ludus documentation searches via prompts built into your client.
Prerequisites you must have before installing the MCP server:
- Node.js 18.0.0 or higher
- npm package manager
- Ludus CLI binary installed and in PATH on the host with the MCP client
- Active Ludus server environment and network access to Ludus server
- WireGuard VPN or SSH access to Ludus server
Install globally to make the ludus-mcp command available system-wide
npm install -g ludus-mcp@latest
ludus-mcp --setup-keyringIf you prefer developing from source, clone the project and install dependencies locally
git clone https://github.com/NocteDefensor/LudusMCP.git
cd LudusMCP
npm install
npx ludus-mcp --setup-keyringUpdate the MCP server when new versions are available
npm install -g ludus-mcp@latestInitial setup securely stores credentials and configures how you connect to Ludus. Run the setup wizard to configure credentials:
npx ludus-mcp --setup-keyringDuring setup you will be prompted for the connection method (WireGuard VPN or SSH tunnel), your Ludus Admin Username, your Ludus API key, SSH credentials, and optionally the WireGuard config path.
Update existing credentials later if needed
npx ludus-mcp --renew-keyringThe MCP client manages connectivity. If WireGuard is available, the server connects directly for non-admin operations. For admin operations, an SSH tunnel is used. If WireGuard is not available, the SSH tunnel remains the fallback and is automatically managed by the MCP server.
Common issues include connectivity problems, credential problems, and configuration validation failures. Start by ensuring the WireGuard tunnel is active, verify SSH access, and check the API key. Validate configurations before deployment and inspect logs for detailed error messages.
All credentials are stored in your OS credential manager. Use secure dialogs for credential collection and avoid exposing sensitive values in command lines.
You can access a range of Ludus-related prompts, including guided range creation, secure command execution, configuration reading/writing, and documentation searches. Use the MCP prompts available in your client to begin these workflows.
Deploy virtualized training environment. Creates and provisions the necessary VMs and resources for the range.
Check deployment status and VM states for a given range.
List all ranges available to the current user.
Download RDP/VPN connection files for accessing deployed VMs.
Permanently delete a deployed range and its virtual machines.
Stop a deployment that is stuck or failing.
Start or stop range VMs to control resource usage.
Read the current range configuration.
Create or modify range configurations.
Validate YAML syntax and schema for a range configuration.
Browse available range configuration templates.
Get the currently active configuration.
Set an active configuration for deployment.
Search Ludus documentation for quick reference.
Intelligent assistant for planning range requirements and deployments.
Search available Ludus roles.
Find environment setup guides.
Network configuration help.
View the schema for range configurations.
Validate a range configuration against deployment requirements.
View role/collection schemas.
List all available role/collection schema files.
Execute arbitrary Ludus CLI commands.
Get help for Ludus commands.
List all Ludus users (admin only).
Securely collect user credentials.
Inject credentials into configurations (note: credential handling occurs via the OS credential manager).
Read and validate MCP server configuration files.