Percher is now a one-click connector, no install required

Updated 24 October 2026: you can now publish an app created in chat and choose which apps each connection can access. This post has been updated to match.

Add `https://mcp.percher.app/mcp` to an assistant that supports remote MCP connections, then sign in to Percher and approve the connection. There is no Percher token to copy and no local package to install. Follow the connection guide for your assistant's setup steps.

Once connected, ask it to list your apps.

Choose which apps it can work on

New connections start at All apps. This includes your own apps, shared apps and apps you add later. Sharing still has the same limits: an assistant does not get more access than your account has.

Choose Only selected apps to limit a connection. It can update those apps, but cannot create new ones. Selecting no apps gives it no app access.

Database tools start at None. You can enable them for apps you own: choose Read or Read and write, then choose whether the assistant acts as a visitor, an app user or with full access. The app must also be in the connection's app access. These settings control the assistant's database tools. They do not stop the app's own code from using its database.

You can change or revoke access under Account → Connections. Changes require your password and apply to new requests. Work already started may finish.

Publish an app from a chat

If your assistant has built an app in the conversation, ask it to publish the source to Percher. It can send the files through the connector. It can also publish from a public repository URL or a repository you have connected. Creating a new app requires All apps access and must pass the usual plan limits and security checks.

For an existing app, you can ask the assistant to inspect a failed build, change environment variables, manage domains or publish an update. It can list collaborators and pending transfers, but cannot change sharing or transfer ownership through the hosted connector.

The connector cannot read files on your computer. For a project stored there, use the local MCP setup. The hosted connector also has no runtime logs or Doctor; use the dashboard for logs or the local package for those diagnostics.

Check the connection before approving

Percher uses OAuth to let the assistant connect without asking you to copy a token. The assistant manages its tokens, and Percher checks the current permissions on each request. Revoking a connection stops new requests.

The hosted service receives your token when it handles a request. OAuth does not prevent a compromised service from misusing a token it receives.

A client can register under a name it chooses. Check the return address shown on the consent page before approving. Percher marks unverified clients; a familiar name alone is not proof of who operates one.