mcp-install

# mcp-install A reusable, app-agnostic installer for registering stdio MCP servers with Claude Desktop, Claude Code, Codex, and Grok Build. This package has **no knowledge of any specific MCP server**. Every app-specific detail — server name, entrypoint command, which env vars to forward into the registered entry, the PyPI distribution name used for `uvx --from` inference, the env var a standalone binary uses to identify itself — is read from a small JSON manifest (`install.config.json`) that each consuming project ships on its own. Point `mcp_install.Install` at your manifest and it needs no code changes. ## Installing ```bash pip install mcp-install # or, for local development against a sibling checkout: pip install -e ../mcp-install ``` ## Wiring it into your own MCP server project 1. Add `mcp-install` as a dependency of your project. 2. Add your own `install` console-script entry point in your `pyproject.toml`: ```toml [project.scripts] install = "mcp_install.Install:main" ``` 3. Ship an `install.config.json` manifest at your project root: ```json { "serverName": "my-server", "entrypoint": "my-mcp", "distributionName": "my-mcp", "binaryEnvVar": "MY_MCP_BINARY", "envKeys": ["MY_SERVER_TOKEN"], "defaultEnvValues": {}, "envWarnings": { "MY_SERVER_TOKEN": "MY_SERVER_TOKEN is not set." } } ``` | Key | Required | Meaning | |---|---|---| | `serverName` | yes | Default key the server is registered under in each client's config (overridable with `--server-name`). | | `entrypoint` | yes | Command run via `uvx <entrypoint>` (overridable with `--entrypoint`). | | `distributionName` | no | PyPI/installed distribution name used to infer a `uvx --from <git-url>` source from the running install's metadata. | | `binaryEnvVar` | no | Env var name checked for a pre-built standalone binary path; when set, `install` registers that binary directly instead of a `uvx` command. | | `en…