Zellij MCP C5fdc414

MCP运维云端

提供方 LumenYoung

运维云端 未标注 会话登录 社区 / 第三方

用于通过in-repo后端安全地与Zellij窗格进行代理交互的Rust MCP守护进程。

一句话选型结论

按资料字段整理

Zellij MCP C5fdc414 属于运维云端类 MCP 服务器,传输方式未标注,会话登录,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类运维云端 传输方式未标注 鉴权会话登录 部署方式未标注
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 8 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

运维云端
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量8暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

适用场景

ZellijRust本地部署终端管理SSH远程操作窗格交互

安装与配置

未标注 会话登录
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 8 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
云资源查询

查实例、存储、账单等云上资源状态。

部署与发布

把部署、重启、回滚这类操作接进对话。

监控与告警

拉取监控指标,异常时让模型帮你判断。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 8 个工具,职责相对集中,接入后不容易误操作。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在运维云端场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Zellij MCP C5fdc414当前 8 未标注 未标注 无 2026-05-17
lobehub 未标注 stdio · 本地进程 本地部署 有 2026-04-11
TrendRadar 未标注 stdio · 本地进程 本地部署 有 2026-04-13
Ui Tars Desktop 8a825770 未标注 stdio · 本地进程 本地部署 有 2026-05-17
ruflo 未标注 stdio · 本地进程 本地部署 有 2026-04-13
FastGPT 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

运维云端
字段来自项目仓库与公开索引,中文说明由本站标注
提供方LumenYoung上游标注的维护方 LumenYoung
分类运维云端本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式会话登录远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

11.9 KB
来自项目仓库与上游目录的原文,未做删改

Zellij MCP

Rust MCP daemon for safe agent interaction with Zellij panes through an in-repo backend.

Current release line: 0.1.0

What it provides

The daemon exposes these MCP tools:

  • zellij_spawn
  • zellij_attach
  • zellij_discover
  • zellij_send
  • zellij_wait
  • zellij_capture
  • zellij_close
  • zellij_list

It keeps agent-facing handles stable, persists lightweight state, and adds capture semantics (full, delta, current) on top of raw pane access.

Recent spawn hardening:

  • zellij_spawn(wait_ready=true) may return status="busy" when the pane is real but rendered-screen idle detection does not settle within the bounded wait window
  • the daemon now persists spawned handles before post-launch probing so a real launch is not lost just because follow-up readiness or capture work degrades
  • default interactive spawn_target="new_tab" now binds the new tab's default terminal pane instead of implicitly creating a second shell pane
  • default planner behavior prefers reusing the obvious single shell-like terminal pane in a requested tab and now rejects ambiguous multi-pane tabs instead of silently picking one

Wrapped command presentation:

  • fish-backed wrapped submit flows use a clean __zellij_mcp_run_b64 entrypoint instead of printing the full inline interaction script into the pane
  • the daemon embeds the canonical fish wrapper implementation into the binary and lazily bootstraps it into fish panes when needed, so runtime does not depend on the repo checkout or dotfiles being present
  • scripts/__zellij_mcp_run_b64.fish remains the repo-owned source artifact for the wrapper contract and still supports -p preview mode so users can inspect the decoded command without executing it
  • if wrapper validation, bootstrap, or clean invocation still fails at runtime, the daemon falls back to the legacy inline wrapper so the command still runs

Requirements

  • Rust toolchain
  • Zellij session with the required plugin approved for daemon RPC use

Normal daemon operation uses the in-repo backend directly. You do not need to install or invoke an external zjctl wrapper for the local MCP flow.

Build```bash

cargo build --release
cargo build-plugin


Binary path:```text
target/release/zellij_mcp

Plugin artifact path:```text
target/wasm32-wasip1/release/zrpc.wasm


## Run manually

The daemon serves MCP over stdio.```bash
ZELLIJ_MCP_STATE_DIR=/home/yang/.local/state/zellij-mcp-opencode \
./target/release/zellij_mcp

Manual smoke testing

mcp2cli is optional. It is useful for manual local verification, but OpenCode does not need it for normal usage.

Example:```bash
mcp2cli --mcp-stdio "./target/release/zellij_mcp" --list


## OpenCode setup on this machine

OpenCode is configured from:```text
/home/yang/dotfiles/opencode/opencode.json

This machine now uses a local MCP entry named zellij that launches the daemon on demand.

Important consequence:

  • you do not need to pre-spawn the daemon before agent usage in OpenCode
  • OpenCode starts it when the MCP tools are needed
  • mcp2cli is only for manual testing, not required for OpenCode agent use

Remote over SSH

The current model keeps a single local MCP daemon and lets selection tools opt into a remote target.

  • omit target to use the local backend
  • set target on zellij_spawn, zellij_attach, zellij_discover, or zellij_list to select an SSH target alias such as aws
  • the target value can be a bare alias like aws, and the daemon resolves it canonically to ssh:aws
  • follow-up tools such as zellij_send, zellij_wait, zellij_capture, and zellij_close do not need target; the daemon routes them by the persisted handle binding
  • remote backend commands and zellij are executed over SSH by the local daemon

Runtime configuration is daemon-side through ZELLIJ_MCP_TARGETS.

The current shape is layered, with shared defaults and optional per-alias partial overrides:

Example:```bash
ZELLIJ_MCP_TARGETS='{"defaults":{"remote_zjctl_bin":"zjctl","remote_zellij_bin":"zellij","remote_env":{"ZELLIJ_SESSION_NAME":"remote"},"ssh_options":["-o","BatchMode=yes"]},"overrides":{"aws":{"host":"aws","remote_env":{"ZELLIJ_SESSION_NAME":"aws"}},"a100":{"host":"a100","remote_env":{"ZELLIJ_SESSION_NAME":"a100"}}}}' \
./target/release/zellij_mcp


In that layered form, each alias starts from `defaults`, then only the fields present under its override replace or extend them. The daemon also keeps accepting the older legacy map shape for backward compatibility, but the layered `defaults` plus `overrides` form is the intended alias-only setup.

Readiness and remediation:

- the daemon checks remote SSH targets before it tries to use them, then classifies the target as `Ready`, `AutoFixable`, or `ManualActionRequired`
- `AutoFixable` means the daemon can safely apply bounded remediation, such as copying the repo-built `zrpc.wasm` into the standard plugin directory, starting a detached helper client, and retrying readiness exactly once
- `AutoFixable` is used specifically for missing binaries, helper-client absence, and RPC-not-ready drift that can still be recovered through deterministic user-space setup
- missing plugin artifacts are reported distinctly from those retryable states, because launching the plugin cannot repair a host that does not have the expected `zrpc.wasm` installed yet
- when the remote command path does not already include it, the daemon prepends `$HOME/.local/bin` for non-interactive SSH probing and execution so ordinary hosts do not need per-host binary paths
- `ManualActionRequired` covers the remaining non-auto-fixable cases, including unmanaged plugin approval prompts and daemon/plugin protocol-version skew that requires matching artifacts before retrying
- readiness does not claim zero-touch success for every host, it only fixes the safe, bounded cases automatically

Freshness and diagnosability:

- startup now logs daemon instance id, package version, build stamp, pid, and started-at timestamp to stderr
- every successful MCP tool response now includes `_daemon` metadata with the same identity fields so stale local processes are visible per request
- MCP error data now includes daemon identity as well, which makes mixed local/remote failures easier to attribute to the right running binary

Practical setup note:

- if a locally copied Linux binary fails on the remote host with a glibc version error, build it natively on the remote host in user space and install it into the remote `~/.local/bin`
- the daemon normalizes the remote HOME and PATH for non-interactive SSH probing and execution, so remote tools installed in `~/.local/bin` are found without per-host path overrides
- the plugin RPC path still needs an attached Zellij client, so a headless remote host may still need a user-space helper such as a detached `tmux` session running `zellij attach `

Bootstrap helper:```bash
./scripts/zellij-mcp-bootstrap-ssh a100 --session a100

The bootstrap helper stays entirely in user space. It installs Rust if needed, syncs this repo, clones or updates the compatibility helper repo, builds zellij_mcp, the optional compatibility zjctl binary used by the backend layer, and the repo-owned zrpc.wasm natively on the remote host, copies the plugin artifact into the standard Zellij plugin directory, starts a detached helper client, and finishes by running the current readiness check.

The final bootstrap output is repo-owned and intentionally compact:

  • readiness_state=READY means the remote host finished the current bootstrap path and the repo-owned RPC probe succeeded
  • readiness_state=AUTO_FIXABLE means the host still needs bounded remediation such as helper-client or RPC recovery and the MCP-facing class is still PLUGIN_NOT_READY
  • readiness_state=MANUAL_ACTION_REQUIRED means the host needs human action or matching artifacts before retrying; readiness_reason distinguishes missing plugin, plugin approval, and protocol/version skew
  • mcp_error_code mirrors the daemon-facing error family you should expect next: PLUGIN_NOT_READY, PROTOCOL_VERSION_MISMATCH, or ZJCTL_UNAVAILABLE

The script no longer treats raw zjctl doctor text as the final source of truth. It ends with a bounded repo-owned readiness probe (zjctl panes ls --json plus this repo's readiness classification rules) so the bootstrap output matches the daemon's actual error model.

Operational helper note:

  • scripts/zellij-mcp-ssh remains useful for smoke testing or fallback operations
  • it is no longer the primary remote architecture or the recommended OpenCode MCP shape

Path note:

  • prefer absolute remote paths or plain executable names that already resolve on the remote non-interactive PATH
  • do not rely on ~ expansion in helper-script arguments; the wrapper intentionally quotes remote tokens before handing them to SSH

Important constraint:

  • this does not create a detached network daemon on the remote host; the local daemon still initiates remote operations over SSH on demand
  • if you later want the remote daemon to stay reachable without any SSH transport, that becomes a separate transport feature
  • this also does not remove Zellij's own requirement for a connected client when the remote plugin RPC path is in use
  • zellij_discover now degrades preview failures to metadata-only candidates instead of failing the whole call, but metadata-only discovery can still be the cleaner choice on very busy live panes

Target and handle semantics:

  • the canonical target id stored in responses and bindings is ssh:
  • selection tools accept the alias form from the user, while follow-up calls keep using the persisted handle binding
  • that separation keeps the single local MCP architecture intact and avoids nested remote daemons

Configured runtime values on this machine:

  • ZELLIJ_MCP_STATE_DIR=/home/yang/.local/state/zellij-mcp-opencode

Recommended agent flow

For existing user panes:

  1. zellij_discover
  2. zellij_attach
  3. zellij_wait
  4. zellij_capture
  5. zellij_send

For new agent-owned panes:

  1. zellij_spawn
  2. if spawn returns status="busy", keep the returned handle and follow with zellij_wait or zellij_capture
  3. zellij_capture
  4. zellij_send
  5. zellij_close

Notes:

  • wait_ready=true is a convenience idle probe, not a process-start or app-ready guarantee
  • a later zellij_list revalidation can upgrade a spawned handle from busy to ready once the pane selector is reachable again; use zellij_capture when you need a fresh output baseline

Remote troubleshooting quick map

  • TARGET_NOT_FOUND: the selected alias is unknown or the remote pane selector no longer resolves; verify ZELLIJ_MCP_TARGETS, the session name, and whether the pane still exists
  • CAPTURE_FAILED: the handle exists but the capture path degraded; retry with the same handle, then use zellij_list to revalidate ownership before assuming the pane is gone
  • PLUGIN_NOT_READY: the host is reachable but plugin/runtime preconditions are missing; distinguish missing plugin artifacts, manual plugin approval, helper-client absence, and RPC-not-ready drift before retrying
  • PROTOCOL_VERSION_MISMATCH: the daemon and loaded zrpc plugin disagree on PROTOCOL_VERSION; rebuild or reload matching artifacts before retrying because helper/plugin relaunch alone will not fix skew
  • ZJCTL_UNAVAILABLE: the transport or remote binary path is the problem; verify SSH reachability, native remote install, and that the required remote binaries resolve in the non-interactive remote PATH

When you use scripts/zellij-mcp-bootstrap-ssh, those same readiness families are surfaced explicitly as readiness_state, readiness_reason, and mcp_error_code, so shell bootstrap and MCP runtime diagnostics use the same repo-owned vocabulary.

More detail

  • docs/architecture.md
  • docs/mcp-contract.md
  • docs/ssh-remote-design.md
    zellij_discover returns live pane metadata plus attach-ready selector values. zellij_attach then requires one exact selector so the daemon can bind one specific pane and return a stable handle for later send, wait, capture, and close calls.

常见问题

5 问
答案由本站依据条目字段整理,不引用上游原文
Zellij MCP C5fdc414 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Zellij MCP C5fdc414 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Zellij MCP C5fdc414 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Zellij MCP C5fdc414 需要 API Key 吗?

资料标注需要会话登录认证,使用前准备好对应凭据,并按最小权限配置。

Zellij MCP C5fdc414 能提供哪些能力?

资料显示约 8 个工具;能力标签包括 Rust、云端部署、Docker。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。