mlgym-deploy

MCP (Model Context Protocol) server for GitLab Backend - User creation and project deployment.

Installation

``bash
npm install -g mlgym-deploy
`

Usage

$3

Configure in your MCP client settings:

`json
{
"mcpServers": {
"mlgym": {
"command": "npx",
"args": ["-y", "mlgym-deploy"]
}
}
}
`

$3

- mlgym_user_create - Create a new user with GitLab, Coolify, and SSH key setup
- mlgym_project_init - Initialize a project with GitLab repository and Coolify deployment

Configuration

$3

Set the backend URL via environment variable:

`bash
export MLGYM_BACKEND_URL=https://backend.eu.ezb.net
`

$3

When developing locally, you'll need to configure the MCP server with absolute paths. Configuration files are user-specific and not tracked in git.

1. Copy example files to create your local config:

`bash
cp cursor-config.json.example cursor-config.json
cp mcp.json.example mcp.json
cp claude-desktop-config.json.example claude-desktop-config.json
cp ADD_TO_CURSOR_SETTINGS.json.example ADD_TO_CURSOR_SETTINGS.json
`

2. Update the path in your config file with your absolute path:

`json
{
"mcpServers": {
"gitlab-backend": {
"command": "node",
"args": ["/your/absolute/path/to/mcp-server/index.js"],
"env": {
"GITLAB_BACKEND_URL": "https://backend.eu.ezb.net",
"GITLAB_URL": "https://git.mlgym.io",
"COOLIFY_URL": "https://coolify.eu.ezb.net"
}
}
}
}
``

Note: Absolute paths are required because the IDE launches the MCP server from its own working directory, not the project directory. Relative paths won't work.

License

MIT