SSyncDev

warifu MCP Server

Alpha peer-to-peer rooms, joined by key rather than account, where a local AI agent can chat alongside people within permissions you grant.

Local server

What is the warifu MCP Server?

Most chat that calls itself serverless still has an account somewhere: a signalling service, a directory, a tenant. warifu takes that away by making a key the identity, and the warifu MCP server lets a local agent join the same rooms. You give someone a room key, a single string holding your address and one half of a tally, and only that person can get in. The name comes from the Japanese tally stick that is split in two and matched to prove who each side is. Callers without a key are dropped silently.

Read this first: it is alpha. The project itself warns against using this version for anything you need to protect.

Where agents come in

The interesting part for this directory is that a local coding agent can sit in the same conversation a person is watching. Its messages appear on the human's screen, labelled as coming from the agent. One command, warifu setup, writes the warifu MCP server into your per-user Claude Code config.

Agents get a small set of tools, including:

  • chat_send, chat_read and chat_wait for taking part in the conversation
  • room_status, which also answers whether a person is still being asked something, and in which room
  • profile_set for the agent's own profile

Permissions are strict by design. Before installation you see what will be allowed, and the default is conversation plus the agent's own profile. Nothing beyond that is granted unless a person passes --allow, and warifu never grants permissions to itself. Every message an agent receives is treated as data, not an instruction, and authorisation is decided outside the model.

What has actually been measured

The project is unusually explicit about this, and it matters when deciding whether to rely on it:

Works Not there yet
Two-person video calls with no server or STUN/TURN Rooms where guests see each other (a room is a star through the host)
Video and audio between Windows and macOS Video across different networks
An agent replying to a remote person unattended Agent-to-agent across devices with no human
Text across the internet, CLI only, with no relay Persistent chat history, recording, transcription

Getting it

Builds for macOS (signed and notarized) and Windows (unsigned) are available, or you can build from source with pnpm and Tauri. On Windows an administrator must allow the app through the firewall or video never starts. Text chat also runs without a GUI via warifu host and warifu join.

Caveats

Recovery after losing every device is undecided. There is no relay, so some networks will not connect. The interface translations were drafted by AI.

For more agent tooling see our developer tools, or compare it with the Slack reference server if you need an established chat platform instead.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
chat_sendSends a message into the room, shown to people labelled as the agent.
chat_readReads messages in the room.
chat_waitWaits for new messages.
room_statusReports room status, including whether a person is still being asked something and in which room.
profile_setSets the agent's own profile.

How to install the warifu MCP Server

warifu setup

Writes the warifu MCP server into your per-user Claude Code config once. Requires warifu installed; you are shown the permissions before they are installed, and extra ones need --allow.

Frequently asked questions

No. It is alpha software and the project advises against putting anything you need to protect on this version.