Nuwax CLI
Nuwax
A CLI deploys Nuwax, where you can expose workflows and data sources as an MCP service for an agent to connect to
- 911 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- The CLI starts and updates infrastructure with Docker access
- Exported MCP tools can run selected workflows using their credentials
- An exposed initial password or connection configuration can grant unauthorized platform access
Install
- Works in
Manual install
./nuwax-cli init
./nuwax-cli auto-upgrade-deploy registry-deployRun in the extracted CLI directory. Requires Docker and downloads backend images.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The CLI starts and updates infrastructure with Docker access
- Exported MCP tools can run selected workflows using their credentials
- An exposed initial password or connection configuration can grant unauthorized platform access
This is third-party code. Review the repository files before installing.
What it does
Nuwax CLI deploys a self-hosted Nuwax platform and manages its services. Within that installation, you can compose an MCP service from selected components and export configuration for an external client. An agent then accesses the chosen workflow or data source. The Nuwax owner selects functions and tests them in the interface. MCP tools can invoke workflows and plugins. Knowledge-store and table operations are also available. The assembled service determines its tools. The CLI installs and maintains the whole platform; agent connection details come from the service export. Those are separate steps. An existing Nuwax installation does not need redeployment for each MCP service.
Who it is for. Nuwax administrators hosting the platform and exposing selected internal workflows to agents through MCP.
Good fit when
- You need a self-hosted platform for several workflows and integrations
- An existing Nuwax workflow needs access from an external agent
- You want to inspect MCP tools before giving connection details to a client
- You need CLI operations for an installation and backups
Not a fit when
- You need one small MCP without a platform deployment
- You lack a separate machine with sufficient resources and Docker
- You need this repository alone to establish that all backend code is open source
Example request
Plan a separate Nuwax installation and MCP export for one test workflow. Show resource requirements and tools before connecting my agent.Limitations
Docker Compose V2 and a separate Linux or macOS environment are required; Windows is not yet supported for this route. For 1–2 users, recommendations are 4 cores, 16 GB RAM and 200 GB disk, with images using about 20 GB. Apache-2.0 covers this repository, while the separately downloaded CLI and server images need their own license review. Change the initial admin password and protect the connection before external access; a localhost or IP address alone does not do this.
How to disable. First remove the exported MCP connection from the agent and stop that service in Nuwax. Use `./nuwax-cli docker-service stop` for the whole installation. Back up data before removing containers or directories. Regenerate connection configuration if it was exposed.
FAQ
Where do I download Nuwax CLI?
`https://nuwax.com/deploy.html` links separate Linux amd64/arm64 and macOS Universal archives. Choose your platform; the frontend repository archive is not the CLI binary.
Which commands begin deployment?
After extraction, run `./nuwax-cli init`, then `./nuwax-cli auto-upgrade-deploy registry-deploy`. The second step downloads images and starts the platform. Check Docker permissions and disk space first.
How do I connect an external agent?
Create a component MCP in service management, test its tools and export the service. Use that configuration for your installation’s actual address and parameters.
Does every MCP need Agent Computer?
No. It supports additional platform features including general agents and skill management. Inspect dependencies for the selected workflow; the core installation does not automatically include every auxiliary service.
Can I update a running installation?
Yes, the CLI provides update and backup commands. Backups can stop services, so agree on a maintenance window and verify recovery first.
Does the code include hosting?
No. Hosting and selected paid services are separate costs.
Discussion
No questions or reviews yet.
Related
CLI toolsNX MCP connects an agent to Siemens NX with 16 typed tools for parts, sketches, extrusions and STEP export.
An MCP server with n8n node and template knowledge: the agent picks nodes, validates configs and, with API access, creates workflows in your n8n
An open-core platform: workflows and actions of connected services are published as MCP tools for Claude, Cursor and Windsurf
MCP server and wincli CLI: agents drive Windows apps by control name through UI Automation instead of screen coordinates
An MCP server for driving Windows: the agent opens apps, clicks and types, reads window and UI state, and works with files and PowerShell
An MCP server for n8n: an assistant creates, runs and deletes workflows through the API, checks executions and tags and requests a security audit
README in short
The repository contains the Nuwax frontend and links to separate deployment packages. The CLI operates platform services; the UI tests and exports MCP components.