Skip to main content
Percher is still being built and account creation is paused — get notified when it opens.
Percher

Package versions and licences

The 1.0 licence boundary, generated project files, and upgrading npm tools

Ask your agent
Check my installed Percher package versions and their LICENSE files. Explain the difference between earlier MIT versions, FSL-1.1-MIT packages from 1.0.0, and generated files with 0BSD notices. Suggest an upgrade plan without changing my project.Read the guide at percher.app/docs/licensing
How it works, with exact details

The CLI and local MCP server are distributed through npm alongside four JavaScript libraries. All six established a shared 1.0.0 baseline on 13 September 2026.

Which licence applies?

PackageRoleFrom version 1.0.0
percherCLIFSL-1.1-MIT
@percher/mcpLocal MCP serverFSL-1.1-MIT
@percher/coreCommand and scaffold APIsFSL-1.1-MIT
@percher/clientPlatform API clientFSL-1.1-MIT
@percher/sharedShared constants and utilitiesFSL-1.1-MIT
@percher/tomlConfiguration parser and validationFSL-1.1-MIT

Versions below 1.0.0 retain their original MIT licence. Versions from 1.0.0 use FSL-1.1-MIT. The version number identifies the boundary across all six packages.

FSL is a source-available licence with use restrictions. Each version also receives an MIT grant two years after it is first made available under FSL. Read the LICENSE included with your exact package version for the full permitted-purpose terms and future grant; the npm licence label alone does not establish when that future grant takes effect.

Your project and generated files

Percher-authored files produced by percher create --template and percher ai-files install use the permissive BSD Zero Clause licence (0BSD). Starter projects carry PERCHER-TEMPLATE-LICENSE.txt; generated AI instructions include their notice. These are separate grants from the package's FSL licence.

Your existing project files keep their existing licences. Third-party dependencies and bundled components retain their own licences; CLI and MCP archives include their complete THIRD-PARTY-NOTICES.txt. The public package grants do not cover Percher's proprietary hosted platform or private logo artwork.

Upgrade a CLI or local MCP installation

Run the current 1.x CLI with npx --yes percher@1 --version or bunx percher@1 --version. For a global npm installation, run npm install -g percher@1, then percher --version.

For the local MCP server, change the package argument in your existing client configuration to @percher/mcp@1 and restart that server. For example:

{
  "mcpServers": {
    "percher": {
      "command": "npx",
      "args": ["-y", "@percher/mcp@1"]
    }
  }
}

A hosted connector uses https://mcp.percher.app/mcp and requires no local npm installation. Keep an existing working connection; the npm release alone is not a reason to disconnect it. See Hosted MCP for that separate setup.

If you import the libraries directly, select the 1.x packages you use and update your lockfile. For example, npm install @percher/core@1 resolves its declared compatible client, shared and toml dependencies. Packages can receive independent patch versions after the common 1.0.0 baseline; they do not have to share every later patch number.

An npm deprecation warning appeared

Earlier versions now ask you to upgrade to 1.0.0 or later and state the licence boundary. This is an upgrade notice, not a withdrawal of the old MIT grant. An existing version-specific warning may also describe a technical problem; read the whole notice before deciding to keep a pinned version.

Review the new licence before changing your dependency or MCP configuration. Deprecation does not update your files, alter a lockfile, or redeploy an app for you. Installing a new CLI or local MCP version is separate from publishing an app.

Read the 1.0 release announcement or visit the CLI package on npm.