Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@NetOps Helper Show interface summary for device 'core'."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Tools that give an AI agent the narrowest possible hands and usable eyes on network devices. Each component is released on its own, from this one repository, under its own tag and its own maturity.
Component | What it does | Released |
Read-only MCP server for bounded network troubleshooting |
| |
Configuration audit; collects the configuration from the device itself |
| |
Shared access layer the other components build on: inventory, credential store, host key trust, SSH transport, audit records |
|
netops-admin (device writes, refuses to start without the auditor) is designed but not built. It will appear under components/ when it carries code; an empty directory guarantees nothing.
Every component has its own version, its own tag prefix netops-<component>/vX.Y.Z, and its own release page with its own assets. The tags v0.1.0, v0.2.0, and v0.2.1 without a prefix are netops-helper history and are never moved. A component release archive is self-contained: it carries the component tree, its own LICENSE, and its own changelog. Repository-level files (this page, SECURITY.md, CONTRIBUTING.md, CI) live here and are not part of a component archive.
Related MCP server: SSH MCP Server
scripts/check_release.py is the gate for the tree as a whole. It fails closed when a tracked file belongs to no component release and to no reviewed repository file, when a component has no release selector or no gate of its own, when a component LICENSE differs from the repository one, when CI does not cover a component, or when any tracked file carries a private address, host name, path, or credential-shaped string. Each component then runs its own gate over its own tree: components/netops-helper/scripts/check_public_release.py, components/netops-auditor/scripts/check_gates.py, and components/netops-core/scripts/check_gates.py.
python3 scripts/check_release.py # whole repository
python3 tests/test_release_gate.py # tests of this gateRead SECURITY.md before deploying anything from here, and the security model of the component you are deploying. Report a vulnerability privately through GitHub Security Advisories; never include live credentials, addresses, configurations, or command output.
MIT licensed.
This server cannot be deployed
Scoped, audited SSH exec, sessions, and SFTP on your saved servers without exposing credentials
Let AI operate servers without SSH. Choose actions, approve risky changes, and audit every step.
Issue, rotate and revoke scoped API-key passes for 25+ providers — the agent never sees a real key
Remote shell and detached long-running jobs on your own machines — no SSH, open ports or VPN.
