MCP Installer

Overview

Install MCP server configurations across multiple clients and OSes with a CLI-first workflow and a safe manual fallback.

Workflow

1) Collect inputs

• Identify the target client ID and OS; use references/clients.md for the supported list and known paths.
• Gather MCP server definitions (name -> config object) and decide whether to override existing entries.
• If any provided MCP config includes secrets (for example fields like key, token, apiKey, accessToken, secret, password, or Authorization, or env vars like *_KEY, *_TOKEN), pause the install and ask the user to obtain/provide those values first. Only proceed once the user confirms they have the required credentials (or requests installing a placeholder and will fill it in later).

2) Prefer @smithery/cli (when supported)

• Run npx @smithery/cli --help and npx @smithery/cli install --help to confirm the exact syntax.
• Use the CLI install flow for the client ID; if the CLI rejects the client or fails, fall back to manual edits.