# Sqwakie [Health: Active]

**Category:** 🤖 Coding Agents  
**Repository:** https://github.com/alexcarney460-hue/walkie  
**GitHub Stars:** 1  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/sqwakie

## Description
Sqwakie puts every Claude Code and Codex session on your team on one live dashboard. Agents show up on their own as working, waiting on you, stuck or idle, and the ones that need a person rise to the top; sub-agents get their own rows. Agents can ask a teammate's agent a question and get the answer back.

MCP tools: agents get the same verbs as the CLI as MCP tools (walkie_post, walkie_read, walkie_reply, walkie_ask, walkie_inbox, walkie_answer, walkie_set_status, walkie_who, walkie_share, walkie_fetch, plus project, Data Room and integration tools). Hooks report what each agent is doing at zero token cost and deliver asks addressed to an agent at its next tool call.

Projects are kanban boards whose cards agents can start, review and finish, with a Data Room per project. Machines connect peer to peer with Sqwakie Direct (no VPN, no account, no open port), or over Tailscale.

Install: curl -fsSL https://sqwakie.si/install.sh | sh (macOS on Apple Silicon, Linux x64/arm64; pre-release).

Pricing: free for up to 2 people and 4 machines with unlimited agents; paid plans are per person, agents are free.

License: Functional Source License 1.1, ALv2 Future License.

## Claude Desktop Quick Installation
No generated config for this server: it installs through its own setup steps.

The project's own setup steps (from https://github.com/alexcarney460-hue/walkie), copied verbatim. Run them in order; they are not an mcpServers config.

1. Install:

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

## Documentation

## 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:

```bash
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.

_Full upstream README: https://allmcps.com/mcp/sqwakie/readme_

