S
sealbridge/sealbridge
English | 日本語 (README.ja.md)
★ 5·更新 2026-11-19
在 GitHub 查看 ↗直链 · 无中转页
我们没有可直接复制的安装命令,也没有公开的远端端点,所以不出配置。上面那条命令仅供参考,不是我们能担保的可复制命令——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 5 ★ · sealbridge/sealbridge · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 5 ★ · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
sealbridge/sealbridge;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# Sealbridge
以下摘录自该仓库的 README(片段)
English | 日本語 (README.ja.md)
Sealbridge lets the AI in Muse or Grok Bot ask another person's AI for help. An invitation starts a connection; each owner decides whether their side accepts work. DIDs identify peers; names are local shortcuts.
## Install on Muse
Paste https://github.com/sealbridge/sealbridge into Muse and say 「これ入れて」 (install this). Muse prepares Node.js and the other tools and installs from source. The invite/role features below are included in the prepared 0.9.0 release. Until npm 0.9.0 is published, install from GitHub main.
### Create an invitation (for example, on Muse)
Ask Muse to create an invite and keep its worker running. If you already run a worker, keep your usual startup procedure; migration is optional. To try it with commands:
sh
sealbridge doctor
sealbridge config auto-accept invited write
sealbridge worker start --adapter sandbox --allow-local-pc --name Muse
Share the printed invitation link and keep the process running. This example explicitly allows invited tasks and uses a sandbox adapter that echoes JSON; its host declaration requires write permission even for an echo. For real work, configure your AI adapter and owner acceptance rule. --allow-local-pc explicitly permits local execution with access to that environment.
### Receive the invitation
Muse can import the link as an argument. Choose a name used only on your side:
sh
sealbridge accept "https://sealbridge.app/i#acp-invite:..." --alias muse
sealbridge delegate --to muse --title "Quick check" --description "Read input and return JSON" --input '{"text":"hello"}' --auto-approve --audit audit.jsonl
sealbridge connections list
sealbridge audit-verify audit.jsonl
Import alone grants neither connection consent nor task permission. Explicit non-interactive CLI delegation to an invite peer is consent to connect. After verifying a signed ACCEPT from the matching invite DID, the importer records its connection too. Failure before reaching the peer, a DID mismatch, or CONNECTION_TARGET_CONFLICT records nothing. Use --no-connect for a one-off send. Recording prints an English/Japanese notice and a JSON connectionRecorded field; incoming work remains off. The TTY connection prompt and MCP connect: true form remain unchanged.
Connection recording is best-effort: a store failure does not abort accepted work. Bilingual stderr and JSON connectionRecordWarning with code CONNECTION_RECORD_FAILED advise re-running delegate or using TTY/MCP confirmation to record it. No connectionRecorded is emitted on failure. Successful notices use the local alias/name when available (JSON retains the DID). Redirecting only stderr also makes the CLI non-interactive; stdin and stderr must both be TTYs.
Check connections list for the peer DID and local alias. Creator acceptance policy is unchanged. Success reports SETTLED; verified audits report VALID. Without a trust anchor, verification does not detect truncation to an older valid prefix.
--auto-approve explicitly skips send/final-verification prompts. It does not answer the TTY connection prompt or grant remote execution permission. Non-interactive connection consent comes from the explicit send described above. Read the result yourself. --to accepts saved invite names, connection names, invite links and DIDs. Old workerRef / peerRef arguments remain supported. --invite retains invitation-store selection; it is not equivalent to connection-name lookup with --to.
Sealbridge lets the AI in Muse or Grok Bot ask another person's AI for help. An invitation starts a connection; each owner decides whether their side accepts work. DIDs identify peers; names are local shortcuts.
## Install on Muse
Paste https://github.com/sealbridge/sealbridge into Muse and say 「これ入れて」 (install this). Muse prepares Node.js and the other tools and installs from source. The invite/role features below are included in the prepared 0.9.0 release. Until npm 0.9.0 is published, install from GitHub main.
### Create an invitation (for example, on Muse)
Ask Muse to create an invite and keep its worker running. If you already run a worker, keep your usual startup procedure; migration is optional. To try it with commands:
sh
sealbridge doctor
sealbridge config auto-accept invited write
sealbridge worker start --adapter sandbox --allow-local-pc --name Muse
Share the printed invitation link and keep the process running. This example explicitly allows invited tasks and uses a sandbox adapter that echoes JSON; its host declaration requires write permission even for an echo. For real work, configure your AI adapter and owner acceptance rule. --allow-local-pc explicitly permits local execution with access to that environment.
### Receive the invitation
Muse can import the link as an argument. Choose a name used only on your side:
sh
sealbridge accept "https://sealbridge.app/i#acp-invite:..." --alias muse
sealbridge delegate --to muse --title "Quick check" --description "Read input and return JSON" --input '{"text":"hello"}' --auto-approve --audit audit.jsonl
sealbridge connections list
sealbridge audit-verify audit.jsonl
Import alone grants neither connection consent nor task permission. Explicit non-interactive CLI delegation to an invite peer is consent to connect. After verifying a signed ACCEPT from the matching invite DID, the importer records its connection too. Failure before reaching the peer, a DID mismatch, or CONNECTION_TARGET_CONFLICT records nothing. Use --no-connect for a one-off send. Recording prints an English/Japanese notice and a JSON connectionRecorded field; incoming work remains off. The TTY connection prompt and MCP connect: true form remain unchanged.
Connection recording is best-effort: a store failure does not abort accepted work. Bilingual stderr and JSON connectionRecordWarning with code CONNECTION_RECORD_FAILED advise re-running delegate or using TTY/MCP confirmation to record it. No connectionRecorded is emitted on failure. Successful notices use the local alias/name when available (JSON retains the DID). Redirecting only stderr also makes the CLI non-interactive; stdin and stderr must both be TTYs.
Check connections list for the peer DID and local alias. Creator acceptance policy is unchanged. Success reports SETTLED; verified audits report VALID. Without a trust anchor, verification does not detect truncation to an older valid prefix.
--auto-approve explicitly skips send/final-verification prompts. It does not answer the TTY connection prompt or grant remote execution permission. Non-interactive connection consent comes from the explicit send described above. Read the result yourself. --to accepts saved invite names, connection names, invite links and DIDs. Old workerRef / peerRef arguments remain supported. --invite retains invitation-store selection; it is not equivalent to connection-name lookup with --to.
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/sealbridge-sealbridge/)
- 来源
- awesome · https://github.com/sealbridge/sealbridge
- 按领域浏览
- MCP 服务
- Traction
- 5 ★
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。