ACS MCP Server
The ACS MCP Server enables remote management of a TR-069/CWMP Auto Configuration Server over SSH, providing a comprehensive suite of tools for server and device administration.
Server Lifecycle Management: Start, stop, restart, and check status of the ACS server, with options for port, mass mode, and silent operation.
Device Management: List all known devices, view current device details, find devices by serial number, reboot devices, and retrieve supported RPC methods.
Connection Requests: Trigger devices to immediately connect to the ACS by sending connection requests, either to a specific serial number or the currently selected device.
Script Management: Full CRUD operations for TR-069 Lua scripts, run scripts on demand, and manage script execution sequences.
Device Parameter Operations: Get and set TR-069 parameter values on devices, reboot devices remotely, and list supported RPC methods.
Configuration Deployment: Download and upload configuration files to/from devices, set push flags for automatic deployment on next connection, immediately push configurations, and perform one-click deployment of local
.cfgfiles via temporary HTTP hosting.Logging and Debugging: Retrieve boot, trace, and error logs, clear trace logs, and execute raw shell commands on the remote ACS server for advanced troubleshooting.
Server Configuration: View and dynamically update the MCP server’s connection settings (host, port, credentials, ACS base path) without restarting.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ACS MCP Server list all devices currently connected to the ACS"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ACS MCP Server
Arcadyan miniACS MCP Server — 通过 SSH 远程管理 CWMP/TR-069 ACS(Auto Configuration Server)的 MCP 服务器。
快速开始
编译
# 安装依赖
npm install
# 编译 TypeScript
npm run build
# 或直接使用 tsc
npx tsc编译后 dist/index.js 即为 MCP 入口文件。
stdio 模式运行
用于 VS Code 等本地 MCP 客户端,通过标准输入输出通信:
# 直接运行
node dist/index.js
# 或通过 npx(安装为全局包后)
npx acs-mcp-serverHTTP 模式运行
启动 HTTP + SSE 服务器,支持远程 MCP 客户端连接:
# Windows
set ACS_TRANSPORT=http && set ACS_HTTP_PORT=3000 && set ACS_HTTP_HOST=0.0.0.0 && node dist/index.js
# Linux / macOS
ACS_TRANSPORT=http ACS_HTTP_PORT=3000 ACS_HTTP_HOST=0.0.0.0 node dist/index.js端点:
MCP 端点:
POST http://localhost:3000/mcp— Streamable HTTP + SSE健康检查:
GET http://localhost:3000/health
.mcp.json 配置示例
项目根目录提供了 .mcp.json.example 示例文件,包含 stdio 和 HTTP 两种模式的 MCP 配置模板。该配置格式适用于以下 MCP 客户端:
客户端 | 配置路径 | 说明 |
VS Code | 项目根目录 | Copilot Chat 自动加载,也可通过 |
VS Code Insiders | 项目根目录 | 同上 |
Claude Desktop |
| 全局 MCP 配置 |
使用方法:复制 .mcp.json.example 为 .mcp.json,将 <your-acs-server-ip> 和 <your-ssh-password> 替换为实际值即可。
cp .mcp.json.example .mcp.json
# 编辑 .mcp.json 填入真实 IP 和密码⚠️
.mcp.json包含敏感信息,已在.gitignore中排除,请勿提交到版本库。
Related MCP server: SSH MCP Server
功能概述
该 MCP Server 提供以下工具分类:
🖥️ 服务器生命周期管理
工具 | 描述 |
| 获取 ACS 运行状态 |
| 启动 ACS 服务器 |
| 停止 ACS 服务器 |
| 重启 ACS 服务器 |
📱 设备管理
工具 | 描述 |
| 列出所有已知设备 |
| 获取当前设备信息 |
| 按 SN 查找设备 |
🔗 Connection Request
工具 | 描述 |
| 向指定设备发送 Connection Request |
| 向当前设备发送 Connection Request |
📜 脚本管理
工具 | 描述 |
| 列出所有 TR-069 脚本 |
| 查看脚本内容 |
| 创建/更新脚本 |
| 删除脚本 |
| 运行脚本 |
⚙️ 设备参数操作
工具 | 描述 |
| 获取设备参数值 |
| 设置设备参数 |
| 重启设备 |
| 获取设备支持的 RPC 方法 |
📦 配置下发/上传
工具 | 描述 |
| 向设备下发配置文件 |
| 从设备上传配置文件 |
| 设置 Push 标志 |
| 立即推送配置 |
📋 日志与调试
工具 | 描述 |
| 获取 boot 日志 |
| 获取 trace 日志 |
| 获取 error 日志 |
| 获取脚本执行序列 |
| 设置脚本执行序列 |
| 执行原始 shell 命令 |
安装
# 设置私有 registry
npm config set registry http://10.118.81.229:4873/
# 创建安装目录
mkdir acs-server && cd acs-server
# 初始化项目
npm init -y
# 安装 ACS MCP Server
npm install acs-mcp-server安装后目录结构:
acs-server/
├── node_modules/
│ └── acs-mcp-server/
│ └── dist/
│ └── index.js ← MCP 入口
└── package.json配置
通过环境变量配置 ACS 服务器连接和传输模式:
变量 | 默认值 | 描述 |
|
| ACS 服务器 IP |
|
| SSH 端口 |
|
| SSH 用户名 |
|
| SSH 密码 |
|
| ACS 安装路径 |
|
| 传输模式: |
|
| HTTP 模式监听端口 |
|
| HTTP 模式监听地址 |
传输模式
stdio 模式(默认)
用于 VS Code 等本地 MCP 客户端,通过标准输入输出通信:
{
"mcpServers": {
"acs-mcp-server": {
"command": "npx",
"args": ["acs-mcp-server"],
"env": {
"ACS_TRANSPORT": "stdio"
}
}
}
}HTTP + SSE 模式
启动 HTTP 服务器,支持远程 MCP 客户端通过 HTTP + SSE 连接:
ACS_TRANSPORT=http ACS_HTTP_PORT=3000 ACS_HTTP_HOST=0.0.0.0 npx acs-mcp-server端点:
MCP 端点:
POST/GET http://host:3000/mcp— Streamable HTTP + SSE健康检查:
GET http://host:3000/health
远程客户端配置示例:
{
"mcpServers": {
"acs-mcp-server": {
"url": "http://192.168.1.100:3000/mcp"
}
}
}MCP 客户端配置
VS Code / Claude Desktop(stdio 模式)
{
"mcpServers": {
"acs-mcp-server": {
"command": "npx",
"args": ["acs-mcp-server"],
"env": {
"ACS_HOST": "<your-acs-server-ip>",
"ACS_PASSWORD": "<your-ssh-password>"
}
}
}
}远程客户端(HTTP 模式)
先在服务器上启动 HTTP 模式:
ACS_TRANSPORT=http ACS_HTTP_PORT=3000 ACS_HTTP_HOST=0.0.0.0 npx acs-mcp-server客户端配置:
{
"mcpServers": {
"acs-mcp-server-http": {
"url": "http://<server-ip>:3000/mcp"
}
}
}架构
┌─────────────────────────────────────────────────────────┐
│ MCP Client │
│ (VS Code / Claude Desktop / 远程客户端) │
└─────────┬──────────────────────────────┬────────────────┘
│ stdio (JSON-RPC) │ HTTP + SSE
┌─────────▼──────────┐ ┌──────────────▼───────────────┐
│ StdioServerTransport│ │ StreamableHTTPServerTransport │
└─────────┬──────────┘ └──────────────┬───────────────┘
│ │
┌─────────▼──────────────────────────────▼───────────────┐
│ ACS MCP Server │
│ ┌───────────────────────────────────────────────────┐ │
│ │ index.ts (MCP Server) │ │
│ │ - 注册 26 个 Tools │ │
│ │ - 双传输模式:stdio / http+sse │ │
│ └──────────────────────┬────────────────────────────┘ │
│ │ │
│ ┌──────────────────────▼────────────────────────────┐ │
│ │ acs-client.ts (SSH Client) │ │
│ │ - SSH 连接管理 │ │
│ │ - 远程命令执行 │ │
│ │ - ACS 操作封装 │ │
│ └──────────────────────┬────────────────────────────┘ │
└─────────────────────────┼──────────────────────────────┘
│ SSH (port 22)
┌─────────────────────────▼──────────────────────────────┐
│ Remote ACS Server │
│ (<your-acs-server-ip>) │
│ ┌────────────────────────────────────────────────┐ │
│ │ /root/Downloads/acs-tools/miniACS/Linux/ │ │
│ │ ├── acs (主程序) │ │
│ │ ├── connreq (Connection Request) │ │
│ │ ├── acscmd (命令行工具) │ │
│ │ ├── Tr69-Scripts/ (Lua 脚本库) │ │
│ │ ├── DeviceList.json │ │
│ │ └── Current.json │ │
│ └────────────────────────────────────────────────┘ │
└────────────────────────────────────────────────────────┘使用示例
查看 ACS 状态
> acs_status
{
"running": true,
"pid": "132140",
"port": 8080,
"logFile": "/root/Downloads/acs-tools/miniACS/Linux/boot.log"
}列出所有设备
> acs_list_devices
[
{ "SN": "<device-sn>", "CRURL": "http://<acs-ip>:7547/...", ... },
...
]向设备推送配置
> acs_set_push_flag <device-sn>
Push flag set for <device-sn>. Config will deploy on next connection.技术栈
Runtime: Node.js (ESM)
Language: TypeScript
MCP SDK:
@modelcontextprotocol/sdkSSH:
ssh2
Available Tools
32 toolsacs_clear_trace_logA
清空 ACS trace 日志文件(trace.log)。配合 acs_connection_request 使用:先清空 → 发 CR → 再查看 trace.log 获取本次 Inform 的干净日志
Inputs: no named parameters.
acs_connection_requestC
向设备发送 Connection Request,触发设备连接 ACS
Inputs: sn, url, password, username.
acs_connection_request_currentA
向 Current.json 中的当前设备发送 Connection Request
Inputs: no named parameters.
acs_create_scriptB
创建或更新一个 TR-069 Lua 脚本
Inputs: name (required), content (required).
acs_delete_scriptB
删除一个 TR-069 脚本
Inputs: name (required).
acs_deploy_configA
一键下发配置文件到设备。传入 ACS 服务器本地 .cfg 文件路径,自动起 HTTP 服务托管 → TR-069 Download RPC 下发到设备 → 返回结果。sn 可选,不传则用 Current.json 中的当前设备。
Inputs: filePath (required), sn, fileType.
acs_download_configA
向设备下发配置文件(TR-069 Download RPC)。设备会从 fileUrl 下载文件。⚠️ fileUrl 必须是设备可访问的 HTTP/HTTPS URL,不是 ACS 服务器本地路径。
Inputs: sn (required), fileUrl (required), fileType, password, +1 more.
acs_exec_rawA
在 ACS 服务器上执行原始 shell 命令(用于高级调试)
Inputs: command (required), timeout.
acs_find_deviceA
根据 SN(序列号)查找设备信息
Inputs: sn (required).
acs_get_boot_logB
获取 ACS boot 日志
Inputs: lines.
acs_get_configA
获取当前 ACS MCP Server 的连接配置(host/port/username/acsBasePath,密码脱敏)
Inputs: no named parameters.
acs_get_current_deviceA
获取当前正在处理的设备信息(来自 Current.json)
Inputs: no named parameters.
acs_get_error_logC
获取 ACS error 日志
Inputs: lines.
acs_get_parametersA
获取设备参数值(通过临时脚本调用 GetParameterValues)
Inputs: sn (required), paramPath (required).
acs_get_rpc_methodsA
获取设备支持的 RPC 方法列表
Inputs: sn (required).
acs_get_scriptA
查看指定脚本的内容
Inputs: name (required).
acs_get_sequenceA
获取当前脚本执行序列(seq.txt)
Inputs: no named parameters.
acs_get_trace_logC
获取 ACS trace 日志
Inputs: lines.
acs_list_devicesA
列出 DeviceList.json 中所有已知设备(SN、CRURL、最后连接时间)
Inputs: no named parameters.
acs_list_scriptsA
列出所有可用的 TR-069 脚本
Inputs: no named parameters.
acs_push_configA
立即推送配置(执行 push 脚本)
Inputs: no named parameters.
acs_reboot_deviceC
重启设备
Inputs: sn (required).
acs_restartB
重启 miniACS 服务器
Inputs: mass, port, silent.
acs_run_scriptC
运行一个 TR-069 脚本
Inputs: name (required).
acs_set_parametersB
设置设备参数值(通过临时脚本调用 SetParameterValues)
Inputs: sn (required), params (required).
acs_set_push_flagA
设置 Push 标志,设备下次连接时自动下发配置
Inputs: sn.
acs_set_sequenceC
设置脚本执行序列
Inputs: scripts (required).
acs_startC
启动 miniACS 服务器
Inputs: mass, port, silent, logFile.
acs_statusA
获取 miniACS 服务器运行状态(是否运行、PID、端口)
Inputs: no named parameters.
acs_stopA
停止 miniACS 服务器
Inputs: no named parameters.
acs_update_configA
动态修改 ACS 服务器连接配置,无需重启 MCP Server。修改连接参数后会自动重连
Inputs: host, port, password, username, +1 more.
acs_upload_configB
从设备上传配置文件(Upload RPC)
Inputs: sn (required), uploadUrl (required), fileType, password, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 32 tools
Each tool targets a distinct resource and action. While download_config, deploy_config, and push_config have related purposes, their descriptions and distinct parameters (fileUrl vs local path vs push flag) make them separable. No two tools appear to do the same thing.
All tools share the acs_ prefix and mostly follow verb_noun structure. Some stand-alone verbs (start, stop, restart) and nouns (status, connection_request) are minor deviations but the pattern is predictable and readable.
32 tools is heavy for a single server. While the domain is complex (devices, scripts, config, logs), the count exceeds the 25+ threshold and many tools overlap in purpose (e.g., three config-push mechanisms), suggesting some consolidation is possible.
The surface covers server lifecycle, device discovery, script management, parameter access, config deployment, and logging. Minor gaps include no explicit device add/remove or script enable/disable, but core workflows (device connect, configure, reboot) are fully supported.
Related MCP Connectors
Manage servers through SSH.
Manage remote servers, SSH terminals, files, databases and proxies with scoped access and approvals.
Scoped, audited SSH exec, sessions, and SFTP on your saved servers without exposing credentials
SSH client, server management and one remote MCP URL for your machines, with human approvals.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables SSH connections and remote command execution with persistent session management and real-time browser-based terminal monitoring. Supports multiple simultaneous SSH sessions with command history tracking and live WebSocket streaming of terminal output.6MIT
- AlicenseAqualityDmaintenanceEnables remote server management through SSH and SFTP, supporting command execution, file transfers, and interactive shell sessions. It allows for multiple concurrent connections using either password or SSH key authentication.1121 npm5MIT
- FlicenseBqualityDmaintenanceEnables secure SSH connections to remote servers for executing shell commands and managing active sessions. It supports authentication via passwords or private keys and provides optional host-based access control.4-
- FlicenseNot gradedqualityDmaintenanceEnables remote management and debugging of AstrBot servers via SSH, including log monitoring, status checks, and command execution.-