Percher MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Percher local project publication tools distinct from its hosted subset: Do local filesystem publishing tools remain clearly separated from the remote-safe hosted connector subset?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Publishing and operating AI-built web apps through an OAuth-protected hosted MCP connector.

What we know

Hosted deployment connector for publishing inline/public-repo apps, deploying connected repositories and managing environment variables, domains, versions, analytics and backups.

Maintenance / activity evidence

@percher/mcp 1.0.4 published 2026-10-01T19:46:19.529Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
App-owner deployment/config authority. Writes: Publish/upload source; Deploy/redeploy/rollback; Set environment variables; Manage domains; Sleep/resume apps.
OAuth.
Sensitive access: Source code, Private repositories, Environment secrets, Production domains

Operational deployment connector with production-affecting writes and secrets exposure risk.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do local filesystem publishing tools remain clearly separated from the remote-safe hosted connector subset?

The bounded review of the publisher's documented Percher local project publication tools distinct from its hosted subset and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Operational deployment connector with production-affecting writes and secrets exposure risk.
App-owner deployment/config authority.
OAuth.
Source/repository content and environment configuration are processed by Percher.
Reviewed write actions: Publish/upload source; Deploy/redeploy/rollback; Set environment variables; Manage domains; Sleep/resume apps
Sensitive access: Source code, Private repositories, Environment secrets, Production domains
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
public repository identity
complete retention/telemetry/security details
numeric pricing
Official docs described the service as still being built and account creation paused.
Hosted connector cannot read arbitrary local disk.
Private repos require GitHub App flow.
Package page had no README and no public implementation repo.
Full retention/security/pricing detail was not established.
Official docs said account creation was paused while product was being built.
Package-to-hosted implementation link is official but thinner than repo-backed entries.
Publisher lifecycle: preview / onboarding paused

Original activity observations

@percher/mcp 1.0.4 published 2026-10-01T19:46:19.529Z

Technical identity

npm/@percher/mcp

Exact implementation source: https://www.npmjs.com/package/@percher/mcp ↗
Reviewed resource type: Host
Package identity: npm:@percher/mcp
Service endpoint: https://mcp.percher.app/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@percher/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
percher.app/docs/hosted-mcp
Source material retained for this review.
Evidence source ↗
percher.app/docs
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Host / Desktop app setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not a generic MCP Server; installation means product/developer integration, not a client registration.
Earlier review limitation; V5 documents conditional local and hosted routes with their stated prerequisites: Evidence gap: no first-party copyable installation command verified.
Earlier review limitation; V5 documents conditional local and hosted routes with their stated prerequisites: Re-check README/official package docs before publishing copyable instructions.
Earlier review limitation; V5 documents conditional local and hosted routes with their stated prerequisites: Targeted 2026-10-13 re-research: Publisher npm README re-reviewed; no independently verified general-purpose MCP one-click connection is warranted. Preserve current conditional setup.
Earlier review limitation; V5 documents conditional local and hosted routes with their stated prerequisites: Publisher npm README re-reviewed; no independently verified general-purpose MCP one-click connection is warranted. Preserve current conditional setup.
Vendor docs explicitly identify local npm package and hosted OAuth path as distinct; local package may publish or modify apps.
Documentation example; follow publisher prerequisites and confirm host syntax. No execution performed. Publisher-owned documentation at https://percher.app/docs/quick-start; static documentation review, not live execution.
Client-specific example. Not interchangeable with VS Code servers or Codex TOML. No runtime test.
Never paste credentials into chat.
Documentation example; follow publisher prerequisites and confirm host syntax. No execution performed.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.

Download / install
Publisher instructions
Local MCP supports project-file operations; hosted OAuth server offers reduced remote-safe tool surface. Choose the appropriate route.
publisher documented install or registration · Claude Code only · Publisher instructions
claude mcp add percher -- npx -y @percher/mcp
publisher documented install or registration · Codex only · Publisher instructions
codex mcp add percher --url https://mcp.percher.app/mcp
publisher documented install or registration · Codex only · Publisher instructions
codex mcp login percher
Configure application / integrations
MCP100 setup guide
Local `npx -y @percher/mcp` grants project file access and browser login on first publish; hosted https://mcp.percher.app/mcp uses browser OAuth and cannot read local files. For CI, PERCHER_TOKEN is a separate token route.
claude desktop or cursor mcpServers json · MCP100 composed guide
{ "mcpServers": { "percher": { "args": [ "-y", "@percher/mcp@1" ], "command": "npx" } } }
Check connection
Suggested check
For hosted route, complete browser OAuth and inspect non-deploying tools. For local route ensure tool discovery with project path; never publish to test.
Disconnect / uninstall / revoke
MCP100 setup guide
If you added this integration to Claude Code under the registration name `percher`, run `claude mcp remove percher` to unregister that client entry. In Claude Desktop, Cursor, VS Code or another host, delete/disable the corresponding named MCP registration in that host's settings and restart/reconnect. If you installed an npm package globally or operate a separate HTTP server, uninstall/stop it with its original deployment method. This does not delete user data or revoke service credentials.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate credential guidance / limitations: Publisher Percher hosted OAuth grants can be revoked from dashboard; local PERCHER_TOKEN needs its own account token management.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove percher

Official Documentation & Sources

What it does

Hosted deployment connector for publishing inline/public-repo apps, deploying connected repositories and managing environment variables, domains, versions, analytics and backups.

Capability: Cloud & DevOps
Resource type: Host
Best fit: Publishing and operating AI-built web apps through an OAuth-protected hosted MCP connector.

Representative uses

Publish generated apps
Deploy/redeploy repositories
Manage environment variables/domains
Inspect deployment history/analytics/backups
Manage app lifecycle

Limitations

Official docs described the service as still being built and account creation paused.
Hosted connector cannot read arbitrary local disk.
Private repos require GitHub App flow.
Package page had no README and no public implementation repo.
Full retention/security/pricing detail was not established.
Official docs said account creation was paused while product was being built.
Package-to-hosted implementation link is official but thinner than repo-backed entries.
Publisher lifecycle: preview / onboarding paused

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: OAuth.
Permissions: App-owner deployment/config authority.
Data handling: Source/repository content and environment configuration are processed by Percher.
Cost: unknown
Risk and cautions: Operational deployment connector with production-affecting writes and secrets exposure risk.

Access scope and cautions

Write actions: Publish/upload source Deploy/redeploy/rollback Set environment variables Manage domains Sleep/resume apps
Sensitive access: Source code Private repositories Environment secrets Production domains
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Publish generated apps; Deploy/redeploy repositories; Manage environment variables/domains; Inspect deployment history/analytics/backups; Manage app lifecycle.

What setup and authentication are documented?

A complete connection procedure is not verified. Recorded endpoint: https://mcp.percher.app/mcp. Recorded transport: streamable_http, stdio_bridge. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Hosted OAuth login/consent.

Can it modify data or perform write operations?

Documented write actions include: Publish/upload source; Deploy/redeploy/rollback; Set environment variables; Manage domains; Sleep/resume apps. Recorded permission boundary: App-owner deployment/config authority.

What data-handling boundary should I consider?

Source/repository content and environment configuration are processed by Percher. Recorded sensitive-access context: Source code; Private repositories; Environment secrets; Production domains.

What limitations and risks should I check before use?

Operational deployment connector with production-affecting writes and secrets exposure risk. Official docs described the service as still being built and account creation paused. Hosted connector cannot read arbitrary local disk. Private repos require GitHub App flow. Package page had no README and no public implementation repo. Full retention/security/pricing detail was not established. Official docs said account creation was paused while product was being built. Package-to-hosted implementation link is official but thinner than repo-backed entries. Publisher lifecycle: preview / onboarding paused. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

Is this an official MCP?

Percher is listed as First-party MCP in MCP100’s current evidence.