netxops/docs/INSTALL.md
oliver ed219842d3 Call netx REST from native netx__* tools.
Drop the local python -m netx_mcp / mcp-client path so terminal users only need API URL + token.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-09-04 23:38:24 +08:00

1.9 KiB

Install Netx Ops on DeepSeek Harness

What dsh plugin add gives you

One install wires all of:

Piece How you use it
Host tools native netx__* tools → netx REST (Bearer token)
Plugins card Settings → Plugins → Netx Ops (URL / lang / token)
Agent preset + skills Settings → Agent presets → Custom → Netx Ops (copied into ~/.dsh/.agent-presets on first boot)

You do not run link-preset.ps1 for normal use. That script is only a manual fallback.

Still required outside the npm package

  1. netx API reachable (default http://127.0.0.1:8890) — the data plane.
  2. API token with scopes matching the tools you use (alarms:read, ne:read, ne:exec, sql:query, …).

No local Python / netx_mcp install is required for DSH. (OpenClaw and other MCP hosts can still use python -m netx_mcp separately.)

Install

dsh plugin --profile web add github:hansjone/netxops
# or from DeepSeekHarness source:
# pnpm dsh plugin --profile web add github:hansjone/netxops
dsh web   # or: pnpm dsh web
  1. Settings → Plugins → Netx Ops → API URL (+ token if the field is enabled).
    Token fallback: scripts/set-netx-token.ps1 / .sh.
  2. Restart or open Settings → Agent presets → Custom → Netx Ops should appear after the host plugin has activated once.
  3. New session → preset Netx Ops → ask e.g. Critical Top / single-host alarms.

Verify

  1. Plugins card Netx Ops visible.
  2. Agent presets → Custom → Netx Ops.
  3. Tools include netx__queryUmeAlarms.

See TOOL_MAP.md.

Path / local checkout (developers)

dsh plugin --profile web add D:\path\to\netxops
powershell -File .\scripts\link-dsh-peers.ps1   # only for path/link: installs

See examples/local-debug/README.md.