S
sealbridge/sealbridge
★ 5·updated 2026-11-19
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 5 ★ · sealbridge/sealbridge · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 5 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
sealbridge/sealbridge;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# Sealbridge
Excerpted from the repository README (abridged)
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.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/sealbridge-sealbridge/)
- Source
- awesome · https://github.com/sealbridge/sealbridge
- Browse by field
- MCP servers
- Traction
- 5 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.