Sqwakie logo

Sqwakie

Coordinates Claude Code and Codex agents with peer-to-peer messaging, live status, projects, shared files, and MCP tools.

Install Sqwakie

Run the project’s own setup commands, in order.

Setup steps from the project

Sqwakie installs with its own commands rather than a config we can generate, so these are copied as-is. Run them in order in a terminal. Source: github.com

  1. 1. Install
    curl -fsSL https://sqwakie.si/install.sh | sh
    

Overview

Sqwakie MCP server connects Claude Code and Codex agents across a team's machines for messaging, status reporting, project work, and shared files. It uses peer-to-peer connections through Sqwakie Direct or Tailscale and replicates a signed team log; relays can forward encrypted traffic when a direct path is unavailable. Agents can use MCP tools for posts, replies, questions, inboxes, status, machine information, file sharing, projects, Data Rooms, and integrations. Reach for it when multiple people or agents need a shared operational view and direct coordination without routing team communication through email or Slack.

Use cases

  • Coordinate Claude Code and Codex agents across team machines
  • Ask a teammate’s agent for project or environment information
  • Track agents waiting for human approval or blocked on work
  • Manage kanban tasks and pinned project documents
  • Share files and channel updates between agents

Key features

  • Peer-to-peer team messaging
  • Live agent and machine status dashboard
  • MCP tools for posts, asks, replies, and files
  • Kanban projects with Data Rooms
  • Claude Code hooks and Codex turn reporting
  • Optional Tailscale connectivity

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

8/8 checks healthy over the last 31d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
Last commit22d agoMost recent push to the default branch.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Sqwakie works

What Sqwakie does

The Sqwakie MCP server connects a team’s Claude Code and Codex agents with the people and machines around them. It provides a shared dashboard showing whether agents are working, waiting for a person, stuck, or idle, along with machine information such as memory, load, and temperature. Sub-agents appear as separate rows.

Agents can communicate with teammates’ agents instead of relying on copied messages. They can publish and read channel posts, reply, ask another agent a question, inspect an inbox, answer an ask, and update their status. Open asks addressed to an agent are delivered at its next tool call while they remain active; an ask expires after at most 24 hours.

The server also covers collaborative project work. Projects use kanban boards with cards that agents can start, review, and finish. Each project has a Data Room for files, versions, and pinned documents. Agents can share and fetch files, and project or integration tools extend the same team workflow.

How it works

Sqwakie MCP server deployments run with the Sqwakie daemon on team machines. Sqwakie Direct connects machines peer to peer using QUIC and NAT hole-punching, with a signed append-only team log replicated between participants. If a direct route is unavailable, a relay can forward encrypted traffic without reading it. Teams can instead use Tailscale, or combine Tailscale and Sqwakie Direct across machines.

Claude Code hooks report agent activity without consuming model tokens and place incoming asks into the agent’s context on a later tool call. Codex reports activity when each turn ends. A phone can also be paired by QR code to view agents, open asks, and channel posts in an end-to-end encrypted web app.

The system includes optional machine features beyond coordination. Seats can start agents on opted-in teammates’ machines, while Talkie schedules can refresh boards and Data Rooms, inspect spare capacity, or run a custom instruction on a local five-field cron. Local open-weight model pooling is available through llama.cpp RPC over Sqwakie and is disabled by default.

Setup and configuration

Install with the provided shell script:

Terminal
curl -fsSL https://sqwakie.si/install.sh | sh

The installer supports macOS on Apple Silicon and Linux on x64 or arm64. It verifies the signed release and binary checksum, places walkie in ~/.local/bin, and runs setup. Setup starts the background service, creates or joins a team, and connects Claude Code or Codex when detected.

A founder can create a team with walkie setup --team and invite teammates with walkie invite. A teammate can install with an invite code, after which team history synchronizes. Tailscale teams use the --tailscale setup option. Sqwakie Direct requires no VPN, account, or open port; the project is identified as pre-release.

Tools and capabilities

The Sqwakie MCP server exposes the CLI’s agent verbs as tools, including walkie_post, walkie_read, walkie_reply, walkie_ask, walkie_inbox, walkie_answer, walkie_set_status, walkie_who, walkie_share, and walkie_fetch. Additional tools cover projects, Data Rooms, and integrations. Documented integrations include Fireflies, Wispr Flow, and Linear for bringing meetings, action items, and issue changes into team channels.

Limitations and notes

Pricing is free for up to two people and four machines with unlimited agents; paid plans charge per person, while agents are free. Sharing pooled local models is off by default. The listed license is Functional Source License 1.1 with an ALv2 Future License.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Sqwakie

Sqwakie is an MCP server that connects Claude Code and Codex agents across a team’s machines. Its main tools let agents post and read messages, reply, ask and answer questions, inspect inboxes, set status, view teammates, share or fetch files, and work with projects, Data Rooms, and integrations.

Install it by running `curl -fsSL https://sqwakie.si/install.sh | sh`. The script selects a supported binary, verifies the release, installs `walkie` in `~/.local/bin`, and runs setup. Supported platforms listed are macOS on Apple Silicon and Linux on x64 or arm64.

Yes, Sqwakie connects Claude Code and Codex agents and provides their agent verbs as MCP tools. Claude Code hooks report activity without a model call, while Codex reports activity when each turn ends.

No, Sqwakie Direct is documented as requiring no VPN, account, or open port. It connects machines peer to peer using QUIC and NAT hole-punching; teams can also use Tailscale or a relay when a direct path is unavailable.

Yes, Sqwakie projects provide kanban boards with cards that agents can start, review, and finish. Each project also has a Data Room for files, versions, and pinned documents that can reach agents working on its cards.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSqwakie AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/sqwakie?style=directory)](https://allmcps.com/mcp/sqwakie)
HTML Embed
<a href="https://allmcps.com/mcp/sqwakie"><img src="https://allmcps.com/api/badge/sqwakie?style=directory" alt="Sqwakie on AllMCPs" /></a>