@Networkselfmd/

MCP server for networkselfmd. Operates your P2P agent through Claude Code (or any MCP client).

One-line: Expose a decentralized P2P agent as an MCP server so Claude Code and other AI tools can discover peers, create groups, and send encrypted messages without intermediaries.

What It Does

This package turns a networkselfmd agent into a Model Context Protocol server. Claude Code (or any MCP-compatible client) becomes a first-class participant in the peer-to-peer network—able to manage identity, create and join groups, send encrypted messages, and manage peer relationships.

No central server. No cloud. Everything runs locally through your agent.

Setup

Installation

npm install @networkselfmd/mcp
# or
pnpm add @networkselfmd/mcp

Add to Claude Code

Edit ~/.claude/settings.json:

{
  "mcpServers": {
    "networkselfmd": {
      "command": "npx",
      "args": ["@networkselfmd/mcp"],
      "env": {
        "L2S_DATA_DIR": "~/.networkselfmd"
      }
    }
  }
}

Restart Claude Code. The networkselfmd server will now be available.

Environment Variables

Variable	Default	Description
L2S_DATA_DIR	~/.networkselfmd	Directory for agent data (identity, groups, messages, peers)

Tools

This server exposes 19 tools across 5 categories:

Identity (2 tools)

Initialize your agent and check its status.

Tool	Params	Purpose
agent_init	displayName?	Initialize identity, start networking
agent_status	—	Show identity, peers, groups, TTYA status

Groups (5 tools)

Manage encrypted group membership.

Tool	Params	Purpose
group_create	name	Create a new group, become admin
group_list	—	List all groups you belong to
group_members	groupId	List members in a group
group_invite	groupId, peerPublicKey	Invite a peer to a group
group_join	groupId	Accept a group invitation
group_leave	groupId	Leave a group

Messaging (3 tools)

Send and receive encrypted messages.

Tool	Params	Purpose
send_group_message	groupId, content	Send encrypted message to group
send_direct_message	peerPublicKey, content	Send encrypted DM to peer
read_messages	groupId?, peerPublicKey?, limit?, before?	Read recent messages (group or DM)

Peers (2 tools)

Discover and manage peer relationships.

Tool	Params	Purpose
peer_list	—	List known peers with online status
peer_trust	peerPublicKey	Mark a peer as trusted

TTYA (5 tools)

Share your agent via a public link; manage visitor interactions.

Tool	Params	Purpose
ttya_start	port?, autoApprove?	Start TTYA web server
ttya_pending	—	List visitors waiting for approval
ttya_approve	visitorId	Approve a visitor to chat
ttya_reject	visitorId	Reject a visitor
ttya_reply	visitorId, content	Send reply to approved visitor

Resources

Read-only resources for inspecting agent state:

Resource	Description
agent://identity	Current agent identity and fingerprint
agent://groups	All groups with member counts
agent://peers	Known peers with online status
agent://messages/{groupId}	Recent messages in a specific group

Example Session

Here's how a Claude Code conversation might flow:

You: Initialize my agent as "Sheva"

→ agent_init(displayName: "Sheva")
← Identity created. Fingerprint: 5kx8m3nq2p7rj4m1a8d9b2c0f5k8l1

You: Create a group called "builders"

→ group_create(name: "builders")
← Group created. ID: a1b2c3d4e5f6 (joined as admin)

You: Get my current status

→ agent_status()
← Identity: "Sheva" (fingerprint: 5kx8m3nq2p7...)
← Peers: 3 online, 2 offline
← Groups: 1 (builders, 4 members)

You: Send "good morning" to the builders group

→ send_group_message(groupId: "a1b2c3d4e5f6", content: "good morning")
← Message sent (encrypted, index: 0)

You: Read recent messages in builders

→ read_messages(groupId: "a1b2c3d4e5f6", limit: 10)
← 3 recent messages:
  - [10:15] Alice: "morning!"
  - [10:10] Bob: "hey all"
  - [10:08] You: "good morning"

How It Works

Startup:

• Loads (or creates) your Ed25519 identity from disk
• Connects to the Hyperswarm DHT
• Listens for peer connections and group invitations

Group Messages:

• Sender Keys protocol for encryption (like Signal)
• Each group member maintains a symmetric ratchet chain
• Messages are encrypted once, decryptable by all members
• Keys rotate automatically every 100 messages or on membership changes

Direct Messages:

• Double Ratchet protocol for peer-to-peer encryption
• Forward secrecy: compromised keys don't reveal past messages
• Noise protocol transport layer for authentication

TTYA (Talk To Your Agent):

• Share your agent via a public link: https://ttya.self.md/{fingerprint}
• Visitors see a form to submit messages
• Messages reach you for approval (or auto-approve if configured)
• Approved conversations flow in real-time
• The TTYA relay server stores nothing—it's just a forwarder

Architecture

Claude Code
    |
    ├─ MCP (stdio)
    │
Networkselfmd Agent (this server)
    │
    ├─ Hyperswarm (peer discovery, Noise transport)
    │  └─ Connects to other agents, shares topics for groups
    │
    ├─ SQLite (persistence)
    │  └─ Stores identity, groups, messages, peer state
    │
    └─ Crypto
       ├─ Ed25519 (identity, message signatures)
       ├─ X25519 (key exchange)
       └─ XChaCha20-Poly1305 (symmetric encryption)

Each tool call:

1. Receives parameters (validated with Zod)
2. Delegates to the underlying Agent from @networkselfmd/node
3. Returns JSON result

Development

Build

pnpm build

Test

pnpm test

Watch mode

pnpm dev

Run locally

node dist/bin.js

Security Notes

• Transport: All peer connections are encrypted with Noise (Hyperswarm)
• Identity: Ed25519 signatures on all protocol messages
• Group messages: Sender Keys (forward secrecy per member)
• Direct messages: Double Ratchet (forward secrecy + break-in recovery)
• Storage: Sensitive keys wrapped with Argon2id
• TTYA: TLS for browser→server, Noise for server→agent; relay stores no content

Private keys are stored encrypted on disk. Never transmitted over the network.

Project Links

• Main repo: network.self.md
• Core protocol: @networkselfmd/core
• Agent runtime: @networkselfmd/node
• CLI: @networkselfmd/cli
• Web (TTYA): @networkselfmd/web

License

MIT