protocol-launcher

Protocol Launcher is a compiled, type-safe toolset designed to generate one-click launch URLs for protocol-based apps. It exposes a modular set of MCPs (Minecraft Context Protocols) that can be imported on demand or in full, allowing developers to compose and use protocol-driven functionality without pulling in runtime dependencies. The library provides both on-demand imports for specific providers (e.g., cherry-studio, cursor) and a full import path to access the complete suite. You can leverage the on-demand approach to minimize bundle size while still gaining access to the protocol-launching capabilities you need. This makes it suitable for apps that need to launch or encode protocol-based URLs securely and efficiently, with support for multiple apps and zero-runtime-dependency packaging where possible.

Prerequisites:

• Node.js (recommended latest LTS)
• npm, yarn, or pnpm

Install the library:

npm install protocol-launcher

Or using Yarn:

yarn add protocol-launcher

Or using PNPM:

pnpm install protocol-launcher

Usage (on-demand imports):

// Cherry Studio
import { installMCP, installProvider } from 'protocol-launcher/cherry-studio'

// Cursor
import { installMCP as installCursorMCP } from 'protocol-launcher/cursor'

Usage (full import):

import { cherryStudio, cursor } from 'protocol-launcher'

After installation, import and initialize the MCPs you need in your application entry point, then use the provided APIs to generate and manage launch URLs for protocol-based apps.

Notes:

• The library emphasizes type safety and on-demand imports to keep bundles lean.
• If you encounter environment-specific issues, ensure your bundler (e.g., Webpack, Vite) is configured to handle ESM modules as protocol-launcher is ESM-first.
• Check the official docs at the repository's docs site for detailed guides and examples: https://zhensherlock.github.io/protocol-launcher/
• The npm package name is protocol-launcher; use this in your package.json and imports.
• If you plan to use multiple providers, prefer on-demand imports to minimize runtime footprint.

Environment variables and configuration options:

• The MCP setup is designed to be modular; if any provider requires environment-specific configuration, consult the provider docs within the protocol-launcher repository for recommended env vars and defaults.