Log inSubmit server
Keenetic MCP logo

Keenetic MCP

Control Keenetic router devices, Wi-Fi, interfaces, segments, routes, and policies through verified local MCP operations.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Keenetic MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "keenetic-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "keenetic-mcp"
      ],
      "env": {
        "KEENETIC_HOST": "YOUR_VALUE_HERE",
        "KEENETIC_USER": "YOUR_VALUE_HERE",
        "KEENETIC_PASSWORD": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 18 tools correctly (9d ago).

Overview

keenetic-mcp MCP server connects an MCP client to a Keenetic router over its local HTTP RCI API. It exposes read tools for devices, interfaces, Wi-Fi, routes, policies, segments, system state, and configuration, plus verified tools for selected changes. Use it when an agent needs to inspect or manage a Keenetic network without installing software on the router. Configuration changes remain unsaved until explicitly committed, and read-only mode removes write tools entirely.

Use cases

  • Inspect connected devices and current bandwidth
  • Check Wi-Fi radios, signal details, and client counts
  • Block or allow devices without immediately saving changes
  • Create isolated guest or IoT segments
  • Diagnose internet and interface problems locally

Key features

  • Local Keenetic RCI access over HTTP
  • Device, Wi-Fi, interface, route, and policy inspection
  • Verified writes with automatic session backups
  • Read-only mode without registered write tools
  • Segment creation with DHCP and optional VPN routing
  • Low-level rci_call access to router API paths

Tools18

What Keenetic MCP lets your agent do. Expand a tool for its parameters.

Verified live~2.4k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

6/6 checks healthy over the last 51d

What it can do

From the 18 tools this server returned when we ran it; 18 declare their own safety hints.

Can delete or modify data · 6Makes network requests · 1Read-only tools · 12
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age74 days
Maintainers1

Observed 2026-10-20 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 16d ago via OSV.dev · keenetic-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars28Stargazers on the source repository.
npm downloads923Package downloads in the last 30 days.
Last commit2mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed18Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Keenetic MCP works

What keenetic-mcp MCP server does

The keenetic-mcp MCP server gives an MCP-compatible agent access to a Keenetic router’s local management API. It can inspect connected devices, interface and Wi-Fi status, internet reachability, routes, connection policies, system information, configuration state, and network segments. It can also save a local configuration backup.

Write operations cover device names and access state, routing policies, schedules and priorities; interface state; segment creation and deletion; and saving the running configuration. The rci_call tool provides access to other router API paths when the purpose-built tools do not cover a needed operation.

How it works

The server communicates with KeeneticOS through RCI, a JSON representation of the router’s command tree exposed over HTTP. It authenticates using the router’s challenge-response flow and maintains a session while the agent continues making requests. Responses are shaped before being returned so large router listings fit more usefully in the model context.

The keenetic-mcp MCP server runs on the machine hosting the MCP client and does not install packages, firmware, USB software, or Entware on the router.

By default, changes affect the running configuration only. Before the first change in a session, the server creates a backup. Each write is read back and checked before the operation is reported as successful. Calling save_config is a separate step that makes pending changes survive a reboot.

Setup and configuration

Install the package with npx -y keenetic-mcp, or add it to an MCP client configuration as a stdio server. Claude Code and Codex also have documented plugin installation commands, while Codex can register the standalone command directly.

Running npx -y keenetic-mcp init starts a setup wizard. It discovers the router through the default gateway, confirms that the device is Keenetic, tests the password, and stores that password in the operating system keychain. The settings file contains the router address and login rather than the password.

For containerized or non-interactive deployments, KEENETIC_HOST, KEENETIC_USER, and KEENETIC_PASSWORD override the saved settings. The server also supports a --read-only option; in that mode, write tools are not registered with the client.

Tools and capabilities

Read-oriented tools include list_devices, get_device, list_interfaces, get_interface, get_wifi_status, get_internet_status, list_routes, list_policies, get_system_info, get_config_state, list_segments, and backup_config.

Mutation tools include update_device, set_interface_state, create_segment, delete_segment, and save_config. Segment creation can include Wi-Fi, DHCP, and optional VPN routing. rci_call acts as a lower-level escape hatch for supported router API paths not represented elsewhere.

Limitations and notes

Compatibility depends on the router’s KeeneticOS components. The project was verified on a Keenetic Ultra KN-1811 running KeeneticOS 5.1.3 and lists multiple models on the 5.1 branch; older routers with RCI may expose a different tool set. The keenetic-mcp MCP server is intended for LAN access, not remote cloud administration.

The router may accept an invalid command without applying it, which is why writes are verified. Unsaved changes disappear after a reboot. Segment behavior depends on the router configuration, including the VLAN-backed setup required for a segment to appear in the web interface.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Keenetic MCP

keenetic-mcp is an MCP server that connects AI clients to Keenetic routers through the local HTTP RCI API. Its main tools inspect devices, interfaces, Wi-Fi, routes, policies, segments, and system state, while selected tools update devices, interfaces, segments, and saved configuration.

Install it with `npx -y keenetic-mcp` and add that command as a stdio MCP server. You can run `npx -y keenetic-mcp init` to discover the router, validate credentials, and store the password in the operating system keychain.

Yes, keenetic-mcp works with Cursor through its MCP server configuration. Register the server with the `npx` command and `keenetic-mcp` package, then provide router credentials through the setup wizard or supported environment variables.

Run the server with `--read-only`. The server omits write tools instead of exposing tools that reject changes, so the agent can inspect the router without being given mutation capabilities.

No, keenetic-mcp does not save changes automatically. Writes affect the running configuration, are backed up and verified, and remain temporary until the `save_config` tool is called; a reboot discards unsaved changes.

Related MCP servers

All in Home Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewKeenetic MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/keenetic-mcp?style=directory)](https://allmcps.com/mcp/keenetic-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/keenetic-mcp"><img src="https://allmcps.com/api/badge/keenetic-mcp?style=directory" alt="Keenetic MCP on AllMCPs" /></a>