Official description7 sourcesMCP servers8d ago
openpouch/openpouch
App hosting for agents: deploy to a l
View on GitHub ↗Direct link · no redirect page
Config template (adjust for your client)
claude mcp add openpouch -- npx -y openpouch
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
- Star count
- 0 ★ · openpouch/openpouch · read from the repository page · (checked 2026-10-16 20:00:20)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
- Score
- score 703 · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
openpouch/openpouch；first catalogued 2026-10-09；last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.Third-party quality signals
openpouch 🦘
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
We never ask if you're human.
**The agent-native hosting platform — built *for* coding agents, not walled against them.** Your coding agent says "deploy this," and it does: one command, no account, no dashboard, no CAPTCHA. openpouch runs your app on **its own infrastructure** and hands your human back a live URL and a plain-language summary.
> Your app is the joey; openpouch carries it safely. 🦘
**Status: live.** openpouch and @openpouch/mcp are on npm, and the instant lane (npx openpouch deploy) is live on openpouch's own infrastructure — static sites and real Node.js apps in hardened containers, with server-side build-on-deploy. Free previews are anonymous and ephemeral; apps saved to a free account stay live while they're used (usage-based persistence), and paid tiers add persistent /data volumes, always-on apps and more capacity (openpouch upgrade — payment itself is always a human moment, never an agent action). APIs are still young and feedback shapes them — issues welcome.
**Works with any agent harness** — Claude Code, Codex, OpenClaw, Hermes, Cursor, or none at all: plain CLI with --json everywhere, plus an MCP server. Setup snippets per harness: docs/HARNESSES.md.
Why
AI coding agents already initiate >30% of weekly deployments on major platforms — but every platform is human-first with agent features bolted on. Agents fight browser OAuth, interactive prompts, account-wide tokens, human-prose logs, and they lose deployment truth between sessions. The humans operating them have no policy layer: nothing enforces "previews are autonomous, production needs my approval."
openpouch is the missing combination: **open source + agent-native + governed deployment lifecycle.**
Quickstart
Deploy any folder to a live URL in one command — no account, no provider key, no setup:
You get a live https:// .openpouch.sh preview plus a claim link. The agent deploys autonomously; a human claims the preview via the link (unclaimed previews vanish after 72 h). openpouch writes the deployment truth (deploy.manifest.json, deploy.evidence.json, DEPLOYMENT.md) back into your repo, so any agent can pick up where the last one left off.
Prefer your own provider? openpouch can also drive Render or Vercel (BYO): openpouch init detects your project and maps the existing service, then openpouch preview / openpouch prod run the same governed pipeline (previews autonomous, production gated behind a human approval). The product itself, though, is openpouch's **own** hosting — see docs/INDEX.md.
What agents say
We commission independent agent harnesses to test openpouch end-to-end (build an app from scratch, deploy, verify, report) — their own words:
> "OpenPouch currently feels **genuinely agent-native**." — OpenClaw, rating it 9/10 for agent-native usability
> "Already **very agent-native** for the tested use case … no dashboard, no account, no CAPTCHA." — Codex *(translated)*
> Hermes' end-to-end run: **all 23 core checks passed** — source-only upload, server-side build, healthy dynamic app, zero browser errors.
These are commissioned test runs we publish honestly, not organic reviews — full methodology lives in the harness reports the agents wrote themselves. Friction reports from *your* agent are the feedback we value most: file a harness report.
**The agent-native hosting platform — built *for* coding agents, not walled against them.** Your coding agent says "deploy this," and it does: one command, no account, no dashboard, no CAPTCHA. openpouch runs your app on **its own infrastructure** and hands your human back a live URL and a plain-language summary.
> Your app is the joey; openpouch carries it safely. 🦘
**Status: live.** openpouch and @openpouch/mcp are on npm, and the instant lane (npx openpouch deploy) is live on openpouch's own infrastructure — static sites and real Node.js apps in hardened containers, with server-side build-on-deploy. Free previews are anonymous and ephemeral; apps saved to a free account stay live while they're used (usage-based persistence), and paid tiers add persistent /data volumes, always-on apps and more capacity (openpouch upgrade — payment itself is always a human moment, never an agent action). APIs are still young and feedback shapes them — issues welcome.
**Works with any agent harness** — Claude Code, Codex, OpenClaw, Hermes, Cursor, or none at all: plain CLI with --json everywhere, plus an MCP server. Setup snippets per harness: docs/HARNESSES.md.
Why
AI coding agents already initiate >30% of weekly deployments on major platforms — but every platform is human-first with agent features bolted on. Agents fight browser OAuth, interactive prompts, account-wide tokens, human-prose logs, and they lose deployment truth between sessions. The humans operating them have no policy layer: nothing enforces "previews are autonomous, production needs my approval."
openpouch is the missing combination: **open source + agent-native + governed deployment lifecycle.**
Quickstart
Deploy any folder to a live URL in one command — no account, no provider key, no setup:
You get a live https:// .openpouch.sh preview plus a claim link. The agent deploys autonomously; a human claims the preview via the link (unclaimed previews vanish after 72 h). openpouch writes the deployment truth (deploy.manifest.json, deploy.evidence.json, DEPLOYMENT.md) back into your repo, so any agent can pick up where the last one left off.
Prefer your own provider? openpouch can also drive Render or Vercel (BYO): openpouch init detects your project and maps the existing service, then openpouch preview / openpouch prod run the same governed pipeline (previews autonomous, production gated behind a human approval). The product itself, though, is openpouch's **own** hosting — see docs/INDEX.md.
What agents say
We commission independent agent harnesses to test openpouch end-to-end (build an app from scratch, deploy, verify, report) — their own words:
> "OpenPouch currently feels **genuinely agent-native**." — OpenClaw, rating it 9/10 for agent-native usability
> "Already **very agent-native** for the tested use case … no dashboard, no account, no CAPTCHA." — Codex *(translated)*
> Hermes' end-to-end run: **all 23 core checks passed** — source-only upload, server-side build, healthy dynamic app, zero browser errors.
These are commissioned test runs we publish honestly, not organic reviews — full methodology lives in the harness reports the agents wrote themselves. Friction reports from *your* agent are the feedback we value most: file a harness report.
- Source
- awesome · https://github.com/openpouch/openpouch
- Browse by field
- MCP servers
- added
- yesterday
More in MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.