console-automation-mcp-legacy
Legacy MCP server for console automation that preserves interactive sessions, a 40-tool command/test surface, and legacy protocol adapters for local/remote execution. Intended only for migrations to RunBeacon 3.0.
README
console-automation-mcp-legacy
Maintenance-only compatibility package for the former Console Automation MCP runtime. It preserves the interactive console, 40-tool MCP surface, test framework, and legacy protocol integrations removed from RunBeacon 3.0.
Use RunBeacon and console-automation-mcp@3 for new durable local, SSH, Slurm, Apple-signing, or GitHub jobs. Use this package only while migrating a client that still depends on the old interactive console or protocol APIs.
Support policy
console-automation-mcp-legacy@2.0.x receives only High and Critical security fixes for six months after RunBeacon 3.0 reaches Stable. It receives no new protocols, features, compatibility work, Codex plugin releases, or lower-severity fixes.
The package can execute arbitrary local and remote commands. Keep MCP approvals enabled, use restricted accounts, prefer SSH agents or environment-backed secret references, and install optional integrations only when required. See SECURITY.md.
Installation
npm install console-automation-mcp-legacy@2
The package exposes two equivalent executables:
npx console-automation-mcp-legacy
npx mcp-console
Example MCP configuration:
{
"mcpServers": {
"console-automation-legacy": {
"command": "npx",
"args": ["-y", "console-automation-mcp-legacy@2"]
}
}
}
This repository does not ship the remote-job-monitor Codex plugin and cannot replace RunBeacon's lifecycle daemon, durable Runner, approval dashboard, or credential tools.
Preserved surface
The MCP server retains 40 tools in six groups:
- Session management: create, input, keys, output, streaming, waits, stop, list, and cleanup.
- Command execution: execute, error detection, resource usage, output clearing, state, and history.
- Monitoring: system/session metrics, alerts, dashboard data, and monitoring start/stop.
- Profiles: save, list, remove, and use legacy connection profiles.
- Background jobs: execute, status, output, cancel, list, progress, result, metrics, and cleanup.
- Test automation: output, exit-code, error, snapshot, comparison, and state assertions.
The source also preserves the legacy local, SSH, cloud, container, virtualization, serial, database, and remote-console protocol adapters. Most non-core adapters use optional peer dependencies; install only the peers needed by your deployment.
The complete historical tool and protocol references remain under docs.
Security defaults
- Saved profiles reject inline passwords, passphrases, tokens, and private-key contents.
- File logging is disabled by default in MCP mode and owner-only when explicitly enabled.
- Session persistence is disabled by default because recovery metadata can contain commands, paths, and environment names.
- Xen XAPI requires verified HTTPS.
- VNC challenge authentication is allowed only inside a verified TLS channel.
- Dynamic progress patterns use RE2-compatible matching and bounded input.
Do not publish credentials, host addresses, command output, or production configuration in issues. Use GitHub private vulnerability reporting for security reports.
Development
Node.js 18, 20, and 22 are covered by the maintenance CI matrix.
npm ci
npm run typecheck
npm run build
npm run test:mcp
npm run test:logger
npm run test:package
npm run test:ci
Dependency audit and CodeQL security-extended scanning are required for maintenance releases. Releases are manual; this repository has no automatic npm publication workflow.
Migration
RunBeacon 3.0 intentionally replaces interactive sessions with one durable job lifecycle:
console_create_sessionand background-job polling becomejob_startfollowed by onejob_wait.- Long remote work can use the Go Runner and resume after SSH or coordinator restarts.
- The dashboard watches one task through local long polling without model turns.
- Credentials remain in OS-managed stores or SSH agents.
- Slurm, training, Apple signing, and GitHub publishing have explicit adapters and policy gates.
Pin this package to 2.0.x only for the migration window. Do not add new production dependencies on the legacy surface.
License
MIT. See LICENSE.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。