Skip to content

v0.2.0

Choose a tag to compare

View all tags
@salatmaster salatmaster released this 07 Aug 02:44
· 10 commits to main since this release
v0.2.0
05e2cb6
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

First release with a plugin for both agents. One plugin directory serves Claude Code and Codex: they read different manifests but share the same server definition and the same three skills.

Install

Claude Code

/plugin marketplace add salatmaster/keenetic-mcp
/plugin install keenetic@keenetic
npx -y keenetic-mcp init

Codex

codex plugin marketplace add salatmaster/keenetic-mcp
codex plugin add keenetic@keenetic
npx -y keenetic-mcp init

Anything else

{ "mcpServers": { "keenetic": { "command": "npx", "args": ["-y", "keenetic-mcp"] } } }

What is in it

Sixteen tools: eleven that read the router, four that change it, and rci_call for anything the rest do not cover.

Three skills, so the agent knows how the router behaves rather than guessing. keenetic-rci covers the API tree, the paths that return over 100 KB, and how to recover a command's syntax from the router's own configuration. keenetic-safe-changes covers the change workflow and what the router's fail-safe does not protect against. keenetic-troubleshoot is an ordered diagnostic playbook.

npx keenetic-mcp init finds the router from the default gateway, confirms it is a Keenetic, verifies the credentials against it, and stores the password in the system keychain.

Safety

Nothing is saved unless asked: changes apply to the running configuration and are discarded on reboot until save_config runs. A backup is taken before the first change of a session. Every change is read back and compared, because the router accepts some wrong commands silently and changes nothing. Under --read-only the write tools are not registered at all.

Changes since 0.1.1

  • Codex plugin, sharing one directory with the Claude Code plugin
  • the version now lives only in package.json; npm version propagates it to every manifest and to the pin the plugins share
  • releases publish through npm trusted publishing, so no token is stored anywhere

Verified against

Keenetic Ultra (KN-1811) on KeeneticOS 5.1.3. RCI is a standard part of KeeneticOS rather than a feature of high-end models, so this works across the range; the tool set adapts to the components each router reports.

199 tests. Notes on the API itself are in docs/rci-api.md.

Assets 2
Loading