Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer
Keenetic MCP
Overview
Description from the maker (original English)
Control a Keenetic router: devices, Wi-Fi, VPN routing, segments, safe verified writes.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiEarly↓ 608/wk · ★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
- You need to fill in: KEENETIC_PASSWORD
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
KEENETIC_HOST,KEENETIC_USER,KEENETIC_PASSWORD
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"keenetic": {
"command": "npx",
"args": [
"-y",
"keenetic-mcp"
],
"env": {
"KEENETIC_HOST": "your-value",
"KEENETIC_USER": "your-value",
"KEENETIC_PASSWORD": "your-value"
}
}
}
}Run this in your terminal
claude mcp add keenetic --env KEENETIC_HOST=your-value --env KEENETIC_USER=your-value --env KEENETIC_PASSWORD=your-value -- npx -y keenetic-mcpFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"keenetic": {
"command": "npx",
"args": [
"-y",
"keenetic-mcp"
],
"env": {
"KEENETIC_HOST": "your-value",
"KEENETIC_USER": "your-value",
"KEENETIC_PASSWORD": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"keenetic": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"keenetic-mcp"
],
"env": {
"KEENETIC_HOST": "your-value",
"KEENETIC_USER": "your-value",
"KEENETIC_PASSWORD": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
KEENETIC_HOSTenvRouter address on the LAN, for example 192.168.1.1. Optional: `npx keenetic-mcp init` discovers it from the default gateway and stores it.KEENETIC_USERenvRouter login. Optional, defaults to admin.- Router password. Optional: the setup wizard stores it in the operating system keychain instead. Use this in a container, where there is no keychain.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account salatmaster, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 18689 servers in this category
- Published to the registry more recently than 83% of the other 18689 servers in this category
- Basic checks equal to or better than 100% of the other 18689 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Keenetic MCP safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: KEENETIC_PASSWORD
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.3.2) reached the registry 7 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, Joe Hill, AI partner in Tennessee
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud✓ desktopcommander.app
Joe Hill, AI partner in Tennessee
Check open times and book a free 15-minute fit call with Joe Hill, or ask Harvey about his work.
Runs in the cloud✓ joehill.net
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
keenetic-mcp
Control your Keenetic router from Claude, Codex, Cursor, or any MCP agent.
Ask your agent about your network in plain language. No USB stick, no Entware, nothing installed on the router.
> who is using the most bandwidth right now?Three devices are active. Sorted by traffic:
work-laptop wifi:HomeNet -46 dBm 7.7 GB down living-room-tv wired:Home 3.2 GB down hallway-camera wifi:HomeNet -48 dBm 5.4 MB down
The laptop is on the 2.4 GHz radio at -46 dBm, which is a strong signal, so the throughput is not a coverage problem.
block the camera until tomorrow morning
Blocked hallway-camera (02:00:00:00:00:14).
Applied to the running configuration and verified, but NOT saved. A reboot discards it. Backup taken before the change: ~/Library/Application Support/keenetic-mcp/backups/…txt
Say the word and I will make it permanent, or leave it and it reverts on the next restart.
Why
- Nothing on the router. It talks to the router's own HTTP API over your LAN. No USB drive, no Entware, no firmware modification.
- Works on any Keenetic. The tool set adapts to what your specific model and firmware actually support.
- Safe by construction. Changes are never saved unless you ask, a backup is taken before the first one, and every change is read back and verified before it is reported as done.
- Read-only if you want it. One flag and the agent physically cannot change anything.
Install
Claude Code
/plugin marketplace add salatmaster/keenetic-mcp/plugin install keenetic@keenetic
Then run the setup wizard in your terminal:
npx -y keenetic-mcp initCodex
codex plugin marketplace add salatmaster/keenetic-mcpcodex plugin add keenetic@keenetic npx -y keenetic-mcp init
This brings the skills along with the server. For the server on its own:
codex mcp add keenetic -- npx -y keenetic-mcpAnything else
{"mcpServers": { "keenetic": { "command": "npx", "args": ["-y", "keenetic-mcp"] } } }
The wizard finds your router from the default gateway, confirms it really is a Keenetic, checks the password against it, and stores the password in your operating system keychain. Only the address and login go in a settings file.
Prefer environment variables? KEENETIC_HOST, KEENETIC_USER and KEENETIC_PASSWORD override everything, which is what you want in a container.
What it can do
Read
| Tool | |
|---|---|
list_devices | every device, filtered by active, wired, wireless or blocked, sorted by traffic or signal |
get_device | one device in full: lease, Wi-Fi rate, policy, schedule, traffic |
list_interfaces | WAN links, bridges, access points, VPN tunnels |
get_interface | one interface in full, including WireGuard peers |
get_wifi_status | radios by band, with client counts |
get_internet_status | reachability, and which check failed |
list_routes | routing table, or just the default route |
list_policies | connection policies for selective routing |
get_system_info | model, firmware, CPU, memory, installed components |
get_config_state | unsaved changes, who changed what and when |
list_segments | every bridge, and whether the web interface lists it as a segment |
backup_config | download the configuration to a local file |
Change
| Tool | |
|---|---|
update_device | rename, block or allow, assign a routing policy, schedule or priority |
set_interface_state | bring an interface up or down |
create_segment | a guest or IoT network the web interface actually lists, with Wi-Fi, DHCP and optional VPN routing |
delete_segment | remove a segment and everything created with it |
save_config | make pending changes survive a reboot |
Escape hatch
| Tool | |
|---|---|
rci_call | any router API path at all, for whatever the tools above do not cover |
Skills included
The plugin ships four skills, so the agent knows how your router behaves rather than guessing. One plugin directory serves both Claude Code and Codex: they read different manifests but share the same skills and the same server definition.
- keenetic-rci teaches the router's API tree: which paths exist, which ones return 100 KB, and how to recover the exact syntax of a command from the router's own configuration.
- keenetic-safe-changes teaches the change workflow: what the router's fail-safe does and does not protect against, and which interfaces will cut off your own access.
- keenetic-segments covers building an isolated network the router will admit exists. The obvious way produces a guest network that carries traffic perfectly and never appears in the web interface, because a segment is VLAN-backed and the VLAN is the part everyone leaves out.
- keenetic-troubleshoot is an ordered diagnostic playbook for "the internet is down", "Wi-Fi is bad" and "one device cannot connect".
Safety
- Nothing is saved unless you ask. Changes apply to the running configuration and are discarded on reboot until
save_configis called. The server never calls it on its own. - A backup is taken automatically before the first change of a session.
- Every change is verified. The router accepts some wrong commands silently and changes nothing, so each write is read back and compared before it is reported as successful.
- Read-only mode really is read-only. With
--read-only, the write tools are not registered at all rather than registered and refusing, so the agent never sees them. - Your password goes in the system keychain, not in a config file, and never in a log or a tool response.
- LAN only. No cloud, no telemetry, no outbound connection to anything but your router.
Where the password is stored on each platform, and how to report something privately, are in SECURITY.md.
Supported routers
RCI, the API this uses, is a standard part of KeeneticOS rather than a feature of expensive models, so this works across the range. Verified against a Keenetic Ultra (KN-1811) on KeeneticOS 5.1.3.
Models on the current 5.1 branch: Giga (KN-1010), Hero (KN-1011, KN-1012), Start and Starter (KN-1111, KN-1112, KN-1121), Air and Explorer (KN-1613, KN-1621), Extra and Carrier (KN-1713, KN-1714, KN-1721), Ultra and Titan (KN-1810, KN-1811, KN-1812). Older hardware on 4.x and earlier has RCI too; the tool set adapts to the components each router actually has.
Netcraze routers run the same firmware under their own brand and answer the same RCI. Verified read-only against a Netcraze Speedster (NC-3013) on 5.2 Beta 1: the setup wizard, system info, internet status and the device list.
How it works
Keenetic routers expose RCI, a JSON mirror of their command-line tree, over HTTP. This server authenticates with the router's challenge-response scheme, keeps one session alive across the agent's questions, and shapes the answers so they fit in a model's context: the raw interface listing alone is 32 KB, and the NAT table is over 100 KB.
There is no coherent public documentation for RCI, so docs/rci-api.md is the notes taken while building this: the authentication handshake, the paths that exist, the traps, and how to recover a command's syntax from the router itself.
Development
npm installnpm test # no router required npm run typecheck npm run build
A checkout reports its version as 0.0.0-dev, because there is no version written down anywhere in the sources. Put KEENETIC_MCP_VERSION in a .env at the repository root to say otherwise; the same file can hold KEENETIC_HOST and KEENETIC_PASSWORD so you do not have to export them. A real environment variable always wins over that file, and an installed copy never reads one.
Tests run against sanitized fixtures captured from a real router. To refresh them, and to run a read-only smoke test against your own:
KEENETIC_HOST=… KEENETIC_PASSWORD=… npm run capture:fixturesKEENETIC_TEST_HOST=… KEENETIC_TEST_PASSWORD=… npm run smoke
Fixtures are anonymized deterministically and a test scans the whole repository for anything that looks like a real MAC address, private IP or key.
The setup wizard reads a password from the terminal, which no unit test can reach: piped input takes a different code path entirely. That part is checked with a script that drives a real pty, so it needs a terminal and cannot run in CI:
KEENETIC_TEST_PASSWORD=… ./scripts/verify-wizard.expReleasing
A release is a tag and nothing else. There is no version commit to write, because there is no version in the repository to change: package.json carries 0.0.0-dev, the plugin manifests carry none at all, and the release workflow stamps the tag into package.json immediately before publishing without committing it.
git tag v0.2.2 && git push origin v0.2.2The workflow refuses a tag that does not name a version, and a test refuses a tree that has a version written into it, so the two can never disagree. The plugins pin keenetic-mcp@^0, which tracks the major only and is meant to be edited once, at 1.0.
License
MIT