Percher
MCP-native hosting: publish and operate AI-built web apps live at name.percher.run.
- Transport
- Not stated
- Package
- —
- Registry id
- app.percher/percher
No install snippet on purpose. A working MCP config is a command, its arguments and an environment block — the last two are where API keys live, so this catalogue never stores them and cannot publish them. Follow the link above for the authors' own instructions.
Percher provides a hosted MCP connector that can be added to AI clients like Claude.ai, Cursor, Windsurf, and others as an OAuth-protected connector with nothing to install. Once connected, an AI assistant can operate your Percher apps and publish an app it just built for you. The hosted server exposes a narrow, remote-safe subset of 23 tools, while 54 local tools are available since npm release 1.0.2.
The percher_upload tool supports chunked, hash-verified upload and publish for apps that can't fit in one percher_publish call, such as those over ~64 KB of content or with heavy binary assets. The percher_deploy tool deploys the latest commit of a repo you've connected via the GitHub App, with Percher cloning it server-side. The hosted connector uses OAuth 2.1 with per-user login, and tokens are scope-limited and revocable in real time from the dashboard.
For projects on your machine, a local package (@percher/mcp or CLI bunx percher publish) reads your project directory and provides a full tool set.
Summary drafted from the project's own website. Every sentence is backed by text on that page and was reviewed before publishing.