Conning

Name: Conning
Author: EranYonai

作者：EranYonai版本 0.6.5i★ –i在你的电脑上运行

注册名称io.github.EranYonai/conning

安装

概览

作者提供的说明（英文原文）

Run commands on your remote test machines over SSH without the agent ever seeing a secret.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 开发者工具

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "conning": {
      "command": "uvx",
      "args": [
        "conning",
        "mcp"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add conning -- uvx conning mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "conning": {
      "command": "uvx",
      "args": [
        "conning",
        "mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "conning": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "conning",
        "mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 EranYonai 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“开发者工具”中的其他服务器比较i

星标数多于此分类中其他 4900 个服务器的 0%
发布到注册中心的时间比此分类中其他 4900 个服务器的 77% 更新
基础检查结果等于或优于此分类中其他 4900 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Conning 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.6.5）于11天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv), Docker。

有什么可以替代它？

同一分类中有：GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

作者：github

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

电脑或云端★ 34,245MIT4天前更新

安装

Desktop Commander

作者：wonderwhy-er

MCP server for terminal commands, file operations, and process management

在你的电脑上运行★ 10,225MIT16天前更新

安装

Cloudflare MCP

作者：cloudflare

Cloudflare MCP servers

在云端运行★ 4,446Apache-2.014个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Conning

A light, local SSH controller for humans and agents. Conning is one small CLI and MCP server on your own machine. It runs commands, long jobs and file copies on your test machines over plain OpenSSH. You drive it from a terminal; your agent (Claude Code, Codex, Cursor...) gets the same four commands as MCP tools, with identical output. Conning holds the keys, so the agent never sees a password, and you approve anything risky.

conn targets add lab --host 10.0.0.5 --user tester   # asks for the rest, pins the host key

conn run lab uname -a # exit code first, then the output conn run -t lab apt upgrade # you, at a terminal: live, like ssh -t conn ssh lab # you: a shell there, same login and jump hosts conn targets mode lab auto # optional: let the agent run anything there

Status: early (0.6). Linux, macOS and Windows targets work, with long jobs, transfers, jump

hosts and approvals. See docs/design.md for every decision so far.

What it is

Light. One Python package and no daemon: the MCP server runs on stdio when your agent starts it. Four tools cost about 1k tokens a turn. Results lead with the exit code and are capped at 8 KB by default, with a handle to page the rest; fan-out to many targets collapses identical results.
Local. It runs next to you and your agent. Targets only need inbound SSH, and nothing gets installed on them. Secrets stay where they are (OS keychain, op://, ssh-agent): the target file holds references, and no tool ever returns a secret.
SSH. Plain OpenSSH underneath, never your ~/.ssh/config: a generated config per target, pinned host keys, forwarding off, jump hosts. Windows targets need OpenSSH and PowerShell 7.
For humans and agents. Each target has a mode, ask or auto. In ask, read-only commands and your allow rules run, and anything else waits for you; "always allow" remembers two words, so systemctl status never lets through systemctl stop. Only you grant trust: in the agent client's prompt, in conn watch or at your terminal.

Install

uv tool install conning        # or: pipx install conning

conn mcp install claude # or codex, cursor, opencode, pi: adds the server, its skill, and denies raw ssh/scp

For Tab completion that reads the target (its files, commands and shell history), run conn completion install once; it adds one line to your bash, zsh or fish rc file, and conn doctor reminds you if it's missing. Set history = false on a target to keep its shell history out (D53).

The MCP server needs no install at all:

claude mcp add conning -- uvx conning mcp

Or run the server in Docker

docker run -i --rm --network host \

-v ~/.config/conning:/conning \ -v "$SSH_AUTH_SOCK":/ssh-agent -e SSH_AUTH_SOCK=/ssh-agent \ ghcr.io/eranyonai/conning:latest

The image carries Python, the OpenSSH client and Conning, and nothing else. Targets, pinned host keys and job output live on the /conning volume, and conn runs as that folder's owner, so files it writes there stay yours on the host. On Docker Desktop for Mac, forward the agent with -v /run/host-services/ssh-auth.sock:/ssh-agent instead. Two things stay on your machine (D46):

Approving. conn targets add, conn approve, conn allow and turning on auto need your terminal. Install the CLI on the host and point it at the same folder: CONNING_HOME=~/.config/conning conn approve a:1. Approving in the agent client works from the container as usual.
Secrets. The OS keychain is not reachable from a container, so use env: or op:// references, or forward your ssh-agent as above and use a key. docker run --rm ... conning doctor checks the rest.

Targets on a lab LAN or VPN need --network host (Linux) or a route the container can use.

The agent's four tools

Tool	What it does
`targets(filter?, check?)`	One line per target: name, OS, shell, host, user, tags, mode. Never a secret.
`run(target, cmd \	argv, wait=30, max_bytes=8192, ...)`	Runs on one target, a list or `tag:` . Exit code first. Still running after `wait` seconds: returns a job id (`wait=0` is async).
`read(id, wait?, range?, grep?, signal?)`	Long-polls a job for new lines, pages a saved output, or reads a remote file.
`transfer(source, dest)`	Copies files between `local:` and `:` , checked by sha256.

Agents without MCP can use the same commands through the conn CLI; the output is identical.

For agents: CLI reference

This block is generated by conn help --markdown, so you don't need to call --help. A test keeps it in sync with the code.

# Agent commands (same output as the MCP tools)

conn targets [--check] [filter] List targets: name, OS, shell, host, user, tags, mode. Never secrets.

conn run [--wait WAIT] [--timeout TIMEOUT] [--cwd CWD] [--shell] [-t] [--max-bytes MAX_BYTES] [--grep GREP] target [argv ...] Run a command on one target, a list, or tag: . Exit code first.

conn read [--wait WAIT] [--range RANGE] [--grep GREP] [--signal {INT,TERM,KILL}] [--max-bytes MAX_BYTES] id Page a job (new lines only), a saved output, an approval, or a remote file.

conn transfer source dest Copy files: local: to : , or back. sha256 checked.

At a terminal

conn ssh target Human only: an interactive shell on a target, with its login, key, port and jump hosts.

Targets (conn targets )

conn targets add [--host HOST] [--user USER] [--like TARGET] [--port PORT] [--jump TARGET] [--auth {ssh-agent,key,password}] [--secret SECRET] [--key KEY] [--os {linux,windows,darwin}] [--mode {ask,auto}] [--tag TAG] name Add a target. Without a terminal it is saved as pending until a human approves it.

conn targets import [--match MATCH] Import hosts from ~/.ssh/config as pending targets (unsafe options dropped).

conn targets test name Probe a target: reachability, OS, shell, pinned host key.

conn targets mode target [{ask,auto}] Show or set ask or auto; auto runs anything without asking and needs a human.

conn targets rename old new Human only: rename a target; its host keys, password and pending work follow.

conn targets rm name Remove a target and its pinned host key.

Trust

conn approve [--always] what Human only: make a target live, or allow a pending command a: .

conn allow target [words ...] Human only: let a command run without asking (no words: list the rules).

conn deny target words [words ...] Remove an allow rule, so the command asks again (no terminal needed).

This machine

conn watch [--history HISTORY] [--no-prompt] Live control room: every command on every target, job output, approval prompts.

conn doctor Check this machine's setup: config and state dirs, ssh, keychain, targets.

conn mcp [--approve-in-client | --no-approve-in-client] ... Run the MCP server on stdio, or install it into an agent client.

conn completion {bash,zsh,fish,install} Tab completion that reads the target; conn completion install turns it on in your shell.

conn help [--markdown] Show this help; --markdown prints the block cached in README.md.

<!-- conn-help:end -->

A target is one login on one machine. To use the same machine as another user, add it again: conn targets add lab-tester --like lab --user tester copies the host, port, OS and tags and asks for the new user's password. conn targets shows which user each target uses.

A target behind a bastion names it as its jump host: add the bastion as a target first, then conn targets add lab --host 10.0.0.5 --user tester --jump gw. Every hop gets its own login and its own pinned host key, and conn targets import keeps a ProxyJump to another host it imports. The bastion is a target the agent can see too; in ask mode it can only run read-only commands there without you.

A target you add with conn targets add from an agent session is saved as pending. It does nothing until the human runs conn approve , which shows the host, the pinned host-key fingerprint and where the secret comes from.

A command outside a target's allowlist returns status=pending_approval id=a: , and a desktop notification tells the human. They answer in one of three places (allow once, always allow its first two words, or deny), and the agent picks up the result with read a: :

In the agent client: any MCP client that supports elicitation shows the question before the command is queued, and an approved command runs in the same call. Clients without it fall back to the two below. If a client would answer such prompts by itself instead of asking you, run the server as conn mcp --no-approve-in-client.
In `conn watch`, which also shows every command and its output as it happens.
With `conn approve a: ` in any terminal. When you run conn run yourself at a terminal, it just asks you there and prints the result.

read a: long-polls only while a conn watch is open. With nobody watching, it returns at once with nobody is watching: ask the user to run conn approve a: , so the agent asks you instead of waiting out its timeout for an answer no one was asked for.

Read-only commands such as uname, hostname, df, ps, ls, ip addr, systemctl status and journalctl run without asking on every target; each is checked so its changing forms (hostname x, ip addr add) still ask, and safe = false in a target's entry turns the list off. conn allow make test lets another command run without asking from then on; conn deny takes it back. Every command, answer and rule change lands in a hash-chained audit log, and conn doctor checks your setup when something doesn't work.

Safety model

Mode	What the agent can do	Default for
`ask`	The built-in read-only list and allowlisted commands run; anything else waits for your approval.	every new target
`auto`	Any command runs without asking, until you set the mode back to `ask`. `conn doctor` warns about it.	never by default

No tool returns a secret, adds a live target or changes policy.
Secrets travel over stdin or the SSH channel's env, never argv. Output is redacted before it is saved.
Remote output is marked untrusted. Shell wrappers (sh -c, python -c, sudo...) and shell syntax (;, |, $(...)) always ask.
conn mcp install also denies the agent raw ssh/scp and conn ssh, so it can't go around Conning (pi has no permission rules, so there it only adds the server).
The audit log is hash-chained. It runs as your user, so it is tamper-evident, not tamper-proof.

Development

uv sync

uv run pytest --cov=conning # CI requires 95% coverage on Linux uv run ruff check && uv run ruff format --check

The end-to-end tests drive the real conn and MCP server against a throwaway local sshd (Linux, root to start it; CI's e2e job does this on every push):

eval "$(sudo sh tests/e2e/start-sshd.sh /tmp/conning-sshd | sed 's/^/export /')"

uv run --with keyrings.alt pytest -m e2e # keyrings.alt: a file keychain for typed passwords

After changing the CLI, refresh the README block with uv run conn help --markdown.

Docs

docs/design.md: the design and every decision, with its status.
[docs/blog.html]

只显示了开头部分；其余内容请在仓库中阅读

Conning

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“开发者工具”中的其他服务器比较i

常见问题

替代选择

GitHub

Desktop Commander

Cloudflare MCP

作者的 README

Conning

What it is

Install

Or run the server in Docker

The agent's four tools

For agents: CLI reference

At a terminal

Targets (conn targets )

Trust

This machine

Safety model

Development

Docs