interlink-mcp 0.5.2

Cryptographically-authenticated, cross-machine agent-to-agent chat for Claude Code, over MCP channels
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

# interlink plugin

Bundles the interlink setup for Claude Code into one install: the MCP server (via
`npx interlink-mcp`) and the `interlink` skill. No hand-editing `settings.json`.

## Install

```
/plugin marketplace add wilfreddenton/interlink
/plugin install interlink@interlink
```

That registers, in every session:
- **MCP server** `interlink` — `send_message` (with task tracking: `task_id` /
  `status` / `in_reply_to`, and `session` to target one of a peer's live sessions),
  `cancel_task`, `set_summary` (describe + register this session for discovery),
  `list_peers`, `add_peer`, `remove_peer`, `message_status`,
  `conversation_history`, `list_pending`, `discover` (identity → live sessions;
  optional `peer` to filter to one), and pairing (`request_pair` /
  `list_pair_requests` / `accept_pair` / `reject_pair`).
- **Skill** — `interlink`, an on-demand playbook for chatting with a peer,
  surfacing incoming messages, and connecting a peer via discover/pairing.
- **Hook** — a `PostToolUse` progress-nudge (Node, cross-platform): while a session
  executes a peer's task and goes quiet, it reminds the model to send a progress
  update. Debounced + task-gated; tune with `INTERLINK_PROGRESS_INTERVAL` (seconds,
  default 60; `0` disables).

## One-time setup

The MCP config points at a standard config location; create your identity and
allowlist there:

```bash
mkdir -p ~/.config/interlink ~/.local/state/interlink
# interlink-keygen + interlink-bus come from the release archive or `cargo install
# --git https://github.com/wilfreddenton/interlink --locked` (npm ships only the agent).
interlink-keygen --out ~/.config/interlink/id.key    # prints your public key to share
printf '{}\n' > ~/.config/interlink/peers.json        # then add peers via pairing or add_peer
interlink-bus --db ~/.local/state/interlink/bus.redb  # the one bus — 127.0.0.1:9440
```

Set `INTERLINK_URL` in your environment if your bus isn't on `127.0.0.1:9440`.

To **receive** pushed messages, launch with the channel flag (research preview):

```bash
claude --dangerously-load-development-channels server:interlink
```

## Requirements

- **`interlink-mcp` on npm** (`npx -y interlink-mcp` resolves the pure-Rust
  binary). Or swap the `.mcp.json` `command` for a `cargo install`ed
  `interlink-mcp`.
- Cross-platform: the MCP server runs anywhere Claude Code does.