Iptime Mcp
Manage ipTIME routers through a local, safety-gated MCP server with firmware-aware capabilities.
English | 한국어
iptime-mcp
A safety-gated Model Context Protocol (MCP) server for operating ipTIME routers without repeatedly opening the web admin panel.
It can inspect router state, discover which catalogued operations a specific model and firmware support, and perform confirmed changes across networking, Wi-Fi, NAT, firewall, VPN, DDNS, USB/NAS, system, and automation features.
This is an unofficial community project and is not affiliated with EFM Networks or ipTIME. Router APIs are firmware-dependent and are not published as a stable public contract.
Highlights
- 13 focused MCP tools instead of hundreds of top-level tools
- 334 catalogued router operations: 171 reads and 163 writes
- Runtime capability checks on iUX3 through the router's
api/hasmethod - Detection for iUX3, Mobile iUX, and classic CGI interfaces
- Read-only operations can run directly
- Every router change uses a short-lived, reviewable plan without confirmation tokens
- Configuration backup, restore planning, and firmware upgrade planning
- Single-router and multi-router profiles
- Credential and session-value redaction
- Public plain HTTP blocked by default
The catalog covers administration, firmware, backup and restore, WAN/LAN/DHCP/DNS, routing and switching, wireless and EasyMesh, NAT and port forwarding, firewall, QoS, VPN, DDNS, USB/NAS services, routines, history, logs, host scanning, and Wake-on-LAN.
Compatibility
| Interface | Support |
|---|---|
| iUX3 | Uses /cgi/service.cgi JSON RPC and checks each known method with api/has |
| Mobile iUX | Exposes only explicitly mapped read operations |
| Classic CGI | Exposes only explicitly mapped read operations |
The fixed operation catalog is based on methods observed in an iUX3 application shipped with firmware 15.36.6. A method appearing in the catalog does not mean every router supports it. Always use iptime_capabilities for the target router before choosing an operation.
Firmware 16.00.0 introduced ipTIME ID, EasyMesh client connection pinning, and paginated system logs (official release notes). These additions have not been validated against this catalog. This server connects directly to the configured router; it does not authenticate through ipTIME ID or provide its cloud relay. Do not infer support for new features from a firmware version or from a successful status query. For logs, inspect the actual response and firmware-specific pagination before treating a result as complete. Only verified methods are exposed, and unknown write capabilities remain blocked.
For firmware 16.00.4, the official A2004SE UI bundle was inspected: the ACS CA certificate uses the existing cwmp/set method with acs.cacert containing PEM text (up to 8192 bytes; "" removes the certificate). The UI sends the complete active/acs/cpe configuration. Certificate changes therefore require all these fields, including the actual ACS/CPE credentials; partial configurations and [redacted] placeholders are rejected. cwmp.get hides passwords and cannot be copied back as-is. If you cannot safely supply the complete intended configuration, stop without applying the change. The plan remains critical-risk and reads back through cwmp/get. HTTPS ACS servers with a private CA require the corresponding certificate; do not disable verification. This is interface-contract verification, not a live-router compatibility certification for every model. ipTIME ID/passkey login and new EasyMesh controls remain unsupported until separately verified.
Shared configuration methods accept no configuration parameters through iptime_read; those parameters can perform writes. Use the corresponding write operation through a change plan instead. The observed ddns.config selector "iptime" remains allowed for reads.
From the project's README.