silab-mcp
README.md
# silab-mcp
An MCP server that lets Claude (or any MCP client) control SILAB (SecuryTik MikroTik lab) labs: labs, nodes,
cables, power, PCs, ping/trace, bulk actions, snapshots and courses.
## Install
```bash
git clone https://github.com/mohammed-w-mosabeh/silab-mcp.git
claude mcp add -s user silab -e SILAB_USER=admin -e SILAB_PASSWORD='your-password' \
-- uv run --directory /path/to/silab-mcp silab-mcp
```
## Configuration (environment)
| Variable | Default | Meaning |
|---|---|---|
| `SILAB_URL` | `http://127.0.0.1:8088` | SILAB web UI |
| `SILAB_USER` | `admin` | SILAB web user |
| `SILAB_PASSWORD` | — (required) | SILAB web password |
| `SILAB_HOST` | host of `SILAB_URL` | Host used to reach lab routers |
| `WINBOX_MCP_CONFIG` | `~/.config/winbox-mcp/routers.json` | Where `silab_routers_to_winbox` writes |
CLI-backed tools (`silab_link_impair`, `silab_lab_file`, `silab_node_power cycle`, `silab_cli status`) need
your user in the `silab` group: `sudo usermod -aG silab $USER`, then log out and back in.
## Typical flow
`silab_status` → `silab_labs` / `silab_lab_open` or `silab_lab_new` → `silab_node_add` (router|switch|hub|pc|internet)
→ `silab_link_add` → `silab_lab_up` → configure routers (`silab_bulk_run`, or `silab_routers_to_winbox` then the
[winbox-mcp](https://github.com/mohammed-w-mosabeh/winbox-mcp) tools) → `silab_ping` / `silab_trace`.
## License
[MIT](LICENSE)
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues