NetOps Helper
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NETOPS_VAULT_PATH | Yes | Path to the JSON vault file containing target credentials (e.g., `/path/to/vault.json`). Must be mode 600 and contain one target per line inside a single JSON object. | |
| NETOPS_MASTER_ALIAS | Yes | Alias for the primary master target used by the helper (e.g., `netops-runner`). Must match an alias in the target policy and vault. | |
| NETOPS_FORTIGATE_ALIAS | No | Optional alias for a FortiGate device in the target policy and vault, enabling the separate filtered read-only proxy. | |
| NETOPS_KNOWN_HOSTS_PATH | Yes | Path to the SSH known_hosts file with verified host keys for the runner and all targets (e.g., `~/.ssh/known_hosts`). | |
| NETOPS_TARGET_POLICY_PATH | Yes | Path to the target policy JSON file (e.g., `~/.config/netops-helper/target-policy.json`). This file replaces the example alias and defines the narrowest SFTP roots. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues