一键在 Manus 中运行任何 Skill

bridge

星标7

分支2

更新时间2026年7月2日 21:39

Use when the user wants to run a command on or manage a remote host over SSH — a server, Raspberry Pi, VM, NAS, network switch, or air-gapped machine. Triggers: "check/manage my server", "run X on host Y", "ssh into / exec on host", "restart nginx on prod", "docker ps / containers on", "kubectl / k8s pods / helm on the cluster", "tail the logs on", "disk usage / cpu / memory / processes on host", "what's listening on port", "is host reachable", "service status", "configure / validate the bridge". Drives the bridge-mcp CLI (476 SSH tools) — guided setup, status checks, and tool execution.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

muchiny

muchiny/bridge-mcp

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

SSH Bridge CLI -- Remote Tool Execution

Execute MCP tools on remote hosts or manage bridge configuration via CLI.

Current state

Host status: !bridge-mcp status 2>/dev/null || echo "bridge-mcp not found -- install with: cargo install --git https://github.com/muchiny/bridge-mcp --features full"

Instructions

No arguments or status

Show host status (above) and available tool groups: !bridge-mcp list-tools --groups-only

Then ask the user what they want to do.

Config mode

Help the user configure the bridge:

Config file: ~/.config/bridge-mcp/config.yaml
Validate: bridge-mcp validate
Example config: see https://github.com/muchiny/bridge-mcp/blob/main/config/config.example.yaml

Adding a host:

hosts:
  my-server:
    hostname: 192.168.1.100
    port: 22
    user: admin
    description: "My server"
    auth:
      type: key
      path: ~/.ssh/id_ed25519

Security modes:

security:
  mode: standard  # strict | standard | permissive

Tool group name (e.g., docker, kubernetes, systemd)

List tools in that group: !bridge-mcp list-tools --group $ARGUMENTS

Search query

Search tools by keyword: !bridge-mcp list-tools --search $ARGUMENTS

Tool name with key=value pairs

Execute the tool: !bridge-mcp --json tool $ARGUMENTS

Workflow reminders

Verify connectivity with status before executing tools
Use --json output for structured parsing
Use --dry-run before destructive operations
Use jq_filter or columns params to reduce output tokens

同仓库更多 Skills

同仓库

ssh-audit

muchiny/bridge-mcp

This skill should be used when the user asks to "run a security scan", "check for vulnerabilities", "audit compliance", "check certificate expiry", "scan open ports", or mentions security reviews, CIS benchmarks, or compliance assessments on remote servers.

2026-07-047

ssh-discover

muchiny/bridge-mcp

This skill should be used when the user asks to "show me the available tools", "what Docker tools exist", "search for kubernetes tools", "explore the tool catalog", or wants to browse the 476 bridge-mcp tools by group or keyword.

2026-07-047

ssh-ops

muchiny/bridge-mcp

This skill should be used when the user asks to "run a command on a server", "check Docker containers", "restart a service", "read a remote file", "check disk usage", or mentions managing remote infrastructure via SSH. Teaches CLI-first workflow with progressive tool discovery.

2026-07-047

discover

muchiny/bridge-mcp

Use when the user wants to explore, search, or learn what bridge-mcp can do: "what tools are available", "list bridge tools", "find a tool for X", "show docker / kubernetes / systemd / network tools", "search tools for logs / firewall / packages / databases", "which tool groups exist", "what can the bridge do". Progressive discovery across the 476 tools and 77 groups, with token-efficient describe-tool output.

2026-07-027

bridge

muchiny/bridge-mcp

Use when the user says "bridge", "remote", "ssh tool", "run on host", "check host", "configure host", "setup bridge", or wants to manage remote servers or bridge config via CLI.

2026-06-037

ssh-deploy

muchiny/bridge-mcp

This skill should be used when the user asks to "deploy to production", "restart a service", "do a rolling update", "canary deploy", "helm upgrade", or "rollout to K8s". Manual-only for safety — requires explicit /ssh-deploy invocation.

2026-06-037

name	bridge
version	1.19.1
description	Use when the user wants to run a command on or manage a remote host over SSH — a server, Raspberry Pi, VM, NAS, network switch, or air-gapped machine. Triggers: "check/manage my server", "run X on host Y", "ssh into / exec on host", "restart nginx on prod", "docker ps / containers on", "kubectl / k8s pods / helm on the cluster", "tail the logs on", "disk usage / cpu / memory / processes on host", "what's listening on port", "is host reachable", "service status", "configure / validate the bridge". Drives the bridge-mcp CLI (476 SSH tools) — guided setup, status checks, and tool execution.
user-invocable	true
argument-hint	[status\|config\|tool-name] [args...]

SSH Bridge CLI -- Remote Tool Execution

Execute MCP tools on remote hosts or manage bridge configuration via CLI.

Current state

Host status: !bridge-mcp status 2>/dev/null || echo "bridge-mcp not found -- install with: cargo install --git https://github.com/muchiny/bridge-mcp --features full"

Instructions

No arguments or status

Show host status (above) and available tool groups: !bridge-mcp list-tools --groups-only

Then ask the user what they want to do.

Config mode

Help the user configure the bridge:

Config file: ~/.config/bridge-mcp/config.yaml
Validate: bridge-mcp validate
Example config: see https://github.com/muchiny/bridge-mcp/blob/main/config/config.example.yaml

Adding a host:

hosts:
  my-server:
    hostname: 192.168.1.100
    port: 22
    user: admin
    description: "My server"
    auth:
      type: key
      path: ~/.ssh/id_ed25519

Security modes:

security:
  mode: standard  # strict | standard | permissive

Tool group name (e.g., docker, kubernetes, systemd)

List tools in that group: !bridge-mcp list-tools --group $ARGUMENTS

Search query

Search tools by keyword: !bridge-mcp list-tools --search $ARGUMENTS

Tool name with key=value pairs

Execute the tool: !bridge-mcp --json tool $ARGUMENTS

Workflow reminders

Verify connectivity with status before executing tools
Use --json output for structured parsing
Use --dry-run before destructive operations
Use jq_filter or columns params to reduce output tokens