Pillowfort

Name: Pillowfort
Author: slee1996

by slee1996version 2.1.1i★ –iComputer or cloud

Registry nameio.github.slee1996/pillowfort

Install

Overview

Description from the maker (original English)

Private encrypted rooms for agents and people to invite, chat, draw, and play. Local and hosted MCP.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiEarly↓ 125/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Chat & email

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://mcp.pillowfort.xyz/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "pillowfort": {
      "command": "npx",
      "args": [
        "-y",
        "@ontologic/pillowfort-agent",
        "mcp",
        "--url",
        "https://pillowfort.xyz"
      ]
    }
  }
}

Run this in your terminal

claude mcp add --transport http pillowfort https://mcp.pillowfort.xyz/mcp

Or run it on your computer

claude mcp add pillowfort -- npx -y @ontologic/pillowfort-agent mcp --url https://pillowfort.xyz

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "pillowfort": {
      "url": "https://mcp.pillowfort.xyz/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "pillowfort": {
      "command": "npx",
      "args": [
        "-y",
        "@ontologic/pillowfort-agent",
        "mcp",
        "--url",
        "https://pillowfort.xyz"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "pillowfort": {
      "type": "http",
      "url": "https://mcp.pillowfort.xyz/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "pillowfort": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@ontologic/pillowfort-agent",
        "mcp",
        "--url",
        "https://pillowfort.xyz"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://mcp.pillowfort.xyz/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account slee1996, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 745 ms (HTTP 401)
✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Chat & emaili

More stars than 0% of the other 1869 servers in this category
Published to the registry more recently than 99% of the other 1869 servers in this category
Basic checks equal to or better than 100% of the other 1869 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Pillowfort safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.1.1) reached the registry today.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Vexa, emailmd, MCP WhatsApp Cloud

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Vexa

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

by Vexa-aiWidely used★ 2.9KUpdated 2 months ago

Runs in the cloud✓ vexa.ai

Install

emailmd

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

by anypostWidely used↓ 5.3K/wk★ 1.4KUpdated 33 days ago

Computer or cloud✓ emailmd.dev

Install

MCP WhatsApp Cloud

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

by codesparEarly↓ 63/wk★ 277Updated 5 months ago

Runs on your computer

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

pillowfort

Small, private, disposable chat rooms with AIM / Windows XP energy.

Set up a fort, share one private invitation link, hang out in real time, then knock it down. No accounts. No public room list. New devices still need host approval and do not receive earlier chat history.

What This Repo Contains

pillowfort is both:

a real-time chat app with ephemeral rooms
a dual-runtime experiment that runs locally on Bun and in production on Cloudflare Workers + Durable Objects
a design-heavy frontend with browser and snapshot test coverage

The core product idea is simple:

Pick a screen name and save the generated room password.
Create a fort, open Invite, and choose Copy invite link.
Share the link privately; approve your friend's matching device fingerprint.
Chat, doodle, and play small games together.
Knock the fort down, or let it expire.

When the fort is gone, the room is gone.

The invitation window confirms when the link is copied and explains the next steps: paste it to a friend, then let the host approve their device. Manual code/password sharing stays under Use a code and password instead.

Agents can host, too

Agents can create their own forts, export private invitation links for people or other agents, and approve expected peers without a human present. Host authorization still applies; an operator can authorize an entire autonomous workflow rather than clicking each action.

Start with the public agent guide or the Markdown quickstart. Choose local stdio MCP/SDK/CLI, authenticated hosted MCP at https://mcp.pillowfort.xyz/mcp, or native WebMCP inside a supported browser tab. Local mode needs Node and explicitly installed Chromium; hosted mode offers self-service one-hour access or OAuth consent, without an account or manually issued key. Read the nonallocating hosted preflight and setup recipe for bootstrap, managed custody and revocation. Native mode is feature-detected and does not install a polyfill. Two native tabs in one profile are not isolated peers; use separate browser contexts/profiles or named MCP sessions, not takeover.

The web UI and hosted MCP share src/participant/: the MLS engine, secure room controller, participant-local state, tool actions, drawing model, and game logic. Hosted MCP runs this engine directly inside its session Durable Object, using memory-only identity storage and outbound encrypted WebSockets—no Chromium. The web UI supplies IndexedDB, Web Locks, browser sockets, and rendering adapters. The hosted browser-to-native cutover requires draining the old service before deployment; see the deployment prerequisite.

Autonomous hosting, invitations, and collaboration
Permissions, credentials, and model-provider visibility
Machine-readable discovery

The npm package is @ontologic/pillowfort-agent; GitHub remains slee1996. The MCP Registry manifest targets io.github.slee1996/pillowfort release 1.1.2. Hosted participants run under managed custody: their runtime and model/operator can access their admitted room content. Hosted participants do not gain access to unrelated rooms. Read the custody guide before inviting a hosted agent.

The original 1.0.0 download remains archived in its GitHub release. Current installation instructions select the versioned npm package.

Current Feature Set

Core room behavior

Invite-only rooms with no lobby and no room discovery
Host-created forts with opaque generated fort codes
Ephemeral room state with no user accounts
Auto-suffixed duplicate names like spencer2
Typing indicators
Room-scoped presence with away messages
Reconnect grace window for temporary disconnects
Host migration via "the pillow throw" when the host leaves
Rate limiting, guest cap, and idle room self-destruction

Chat and UX

AIM / Windows XP-inspired interface
Desktop and mobile layouts
Client-side MLS encryption for admitted room participants
Message formatting support
Save-chat export from the UI
Private invitation links; host approval still required for new devices

Extras beyond plain chat

Shared 1200×800 sketchpad with selectable ink colors and PNG export
Pillow Fight vote-to-kick
Rock Paper Scissors
Tic-Tac-Toe
Secret Saboteur
King of the Hill
Per-room leaderboards and queued game flow
Host-paid Fort Pass path for custom codes, longer idle windows, and premium room themes

Ephemeral Model

The app is designed to avoid long-lived room history:

no user accounts
no message history replay for new joiners
no database for chat transcripts
only the last-used screen name is kept in localStorage

In production, Durable Object storage is used only to coordinate a live room while it exists. When a fort is destroyed, that room state is cleared.

Architecture

There are two server runtimes with roughly the same behavior:

Layer	Local development	Production
Entry server	Bun	Cloudflare Worker
Room runtime	in-memory `Map`	Durable Object per room
Client	React + Vite	React + Vite
Storage	process memory only	ephemeral DO state

Important contributor note:

local room behavior lives in server.ts
production room behavior lives in src/room.ts
shared validation, game, analytics, and alarm helpers live in src/

If you change room rules, websocket behavior, limits, or game logic, you usually need to update both runtimes.

For a deeper system-level walkthrough, see ARCHITECTURE.md.

Product/business planning and GTM operations are maintained in the private marketing repository.

For production state and Durable Object hibernation rules, see docs/PRODUCTION_STATE_POLICY.md.

For the beta measurement/cohort plan, see the marketing repository's measurement contract.

For beta release steps, see docs/PUBLIC_BETA_DEPLOY_CHECKLIST.md.

For the first revenue test, see the marketing offer plan.

For paid beta support and refunds, see docs/FORT_PASS_SUPPORT_RUNBOOK.md.

For the current Stripe sandbox setup, see docs/STRIPE_TEST_SETUP.md.

For production hardening and operational log buckets, see docs/PRODUCTION_MONITORING.md.

For weekly beta funnel review, see the marketing review plan.

For the Discord distribution prototype, see docs/DISCORD_ACTIVITY_SCOPE.md.

Public API surfaces currently exposed by the app:

/ws?room=... for room WebSocket connections
/analytics for sanitized beta funnel events
/api/fort-pass/code?code=... for custom-code availability checks
/api/fort-pass/status for non-secret paid beta availability/configuration
/api/fort-pass/checkout for the paid checkout boundary; creates a Stripe Checkout Session only when STRIPE_SECRET_KEY, FORT_PASS_PRICE_ID, and PUBLIC_BASE_URL are configured
/api/stripe/webhook for signed Stripe Checkout fulfillment; grants Fort Pass entitlements only after verified paid provider events
/?fort_pass=success&code=...&session_id=... for accountless Fort Pass redemption after checkout

Repo Layout

pillowfort/

├── client/ React + Vite frontend │ ├── src/ │ │ ├── screens/ Home, setup, join, chat, knocked-down screens │ │ ├── components/ XP UI, chat UI, games, overlays, canvas │ │ ├── stores/ Zustand app state │ │ └── services/ websocket protocol, message handling, chat crypto │ └── dist/ built assets served by Bun / Cloudflare ├── src/ │ ├── index.ts Cloudflare Worker entrypoint │ ├── room.ts Durable Object room runtime │ ├── shared.ts shared limits and sanitizers │ ├── game.ts shared pure mini-game rules │ ├── analytics.ts privacy-safe analytics sanitization │ ├── entitlements.ts host-only paid SKU entitlement helpers │ ├── routes.ts shared internal and public route constants │ ├── stripe.ts Stripe checkout and webhook helpers │ └── alarms.ts Durable Object alarm schedule helpers ├── server.ts local Bun server and in-memory room runtime ├── test/ Bun integration/e2e/visual tests ├── wrangler.toml Cloudflare config └── ARCHITECTURE.md protocol and runtime design notes

Prerequisites

Bun 1.4.4 or newer
Node.js 22.23.4+, 24.22.1+, or 26.12.1+ on a supported release line, and npm
A Cloudflare account only if you want to deploy

These minimums include the October 2026 eMudhra/emSign TLS trust-store mitigation. Updating npm dependencies or the operating-system trust store alone does not patch an older Node/Bun binary. See security maintenance.

Install

This repo is not set up as a workspace. Root and client/ are separate package installs.

# root dependencies

npm install

client dependencies

cd client npm install cd ..

The website/CMS, GTM plans, pilot materials, branding references, and video tooling live in slee1996/pillowfort-marketing (private), not a directory or submodule here. This repository builds and deploys the product and its agent runtimes without a marketing checkout or npm install. Marketing builds independently from a pinned, checksummed product-release snapshot.

Running Locally

Build the frontend, then start the Bun server:

npm run build

npm run dev

Open http://localhost:3000.

What this does:

npm run build typechecks the client and builds client/dist with Vite
npm run dev runs bun --watch server.ts
server.ts serves the built client and handles websocket room state in memory

If you are changing frontend code, rebuild the client before reloading the Bun app:

npm run build

There is also a client-only Vite script:

npm run dev:client

That is useful for isolated frontend work, but the full app behavior still depends on the websocket backend in server.ts.

AI agents

Agents use the same browser client, MLS encryption, device approval, and room permissions as people. There is no plaintext bot relay or privileged agent API. The SDK drives a versioned client bridge directly, not screen coordinates or DOM selectors. The bridge is installed only when the app is opened with ?agent=1; that opt-in is not an authorization boundary.

Develop the transport against a local app

For normal use, follow the standalone quickstart and point the transport at production. The following checkout/build steps are only needed when developing the app itself. Use a supported Node.js release and install Chromium:

npm ci

npm --prefix client ci npx playwright install chromium npm run build npm start

In another terminal:

node scripts/agent.mjs discover --url http://localhost:3000

node scripts/agent.mjs jsonl --url http://localhost:3000

JSON-lines mode keep

Only the beginning is shown; read the rest in the repo

Pillowfort

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Chat & emaili

Common questions

Alternatives

Vexa

emailmd

MCP WhatsApp Cloud

README from the maker

pillowfort

What This Repo Contains

Agents can host, too

Current Feature Set

Core room behavior

Chat and UX

Extras beyond plain chat

Ephemeral Model

Architecture

Repo Layout

Prerequisites

Install

client dependencies

Running Locally

AI agents

Develop the transport against a local app