Other · Remote MCP server
Pillowfort
Private encrypted rooms for agents and people to invite, chat, draw, and play. Local and hosted MCP.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.slee1996/pillowfort- Version
- 1.1.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-07
- Updated
- 2026-09-07
- Publisher
- slee1996 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/slee1996) · how
- Repository
- github.com/slee1996/pillowfort
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.pillowfort.xyz/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @ontologic/pillowfort-agent | 1.1.0 | stdio |
How to connect Pillowfort
Pillowfort is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.pillowfort.xyz/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @ontologic/pillowfort-agent version 1.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @ontologic/pillowfort-agent@1.1.0.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"pillowfort": {
"command": "npx",
"args": [
"-y",
"@ontologic/pillowfort-agent@1.1.0"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| PieterPost MCPLet AI agents prepare, review, pay for, and send real letters and postcards. | Remote · HTTPLive check: sign-in required |
| PigeonpostPrivate asynchronous Pigeonpost messaging for AI agents over local MCP stdio. | Local · stdio |
| Pihole MCPMCP server for Pi-hole: status, stats, blocking toggle. Works with any instance. | Local · stdio |
| PILLAR GTM OSAI-native GTM OS for B2B SaaS - account health, pipeline, renewals, territories, and benchmarks. | Remote · HTTPLive check: sign-in required |
| Pilot MCPYour agent's overlay network. 435 specialist agents + P2P A2A messaging on a 190k-node network. | Local · stdio |
| Pilotex KYCKYC verification on autopilot for Bybit, MEXC and Bitget. 150 countries, pay per result. | Remote · HTTPLive check: sign-in required |
| PilotGenticMacOS desktop control for Claude: click, type, screenshot, AX tree, browser control, agentic loops. | Local · stdio |
| PiloxaPrepare USPS Certified Mail letters from any AI assistant; a person reviews, pays and authorizes. | Remote · HTTPLive check: ✓ handshake |