Smithery MCP Batch Installer

@danielrosehill

Repository

About Smithery MCP Batch Installer

Speeds up installing Smithery MCP servers onto multiple clients

Config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Smithery MCP Batch Installer?

A bash script that automates installing Smithery MCP servers onto multiple client applications simultaneously. It has two versions: v1 takes a full install command (e.g., npx -y @smithery/cli@latest run @smithery-ai/github --client cursor --key <key>) and v2 takes just a package name (e.g., @mcpserver/openrouterai). It is designed for developers who need to deploy Smithery MCP servers across several environments without repeating commands.

How to use Smithery MCP Batch Installer?

Clone the repository, edit the TARGET_CLIENTS array in batch-installer.sh or batch-installer-v2.sh to include your preferred clients, run the script, and paste either a complete Smithery install command (v1) or a package name (v2). The script will then install the server for each client in your list. Press Enter without input to exit.

Key features of Smithery MCP Batch Installer

Replicates a Smithery install command across multiple clients automatically.
Preserves your Smithery key while changing only the target client.
Supports a configurable list of clients (default: windsurf, vscode, roocode, witsy, cursor).
Two versions: v1 (full command input) and v2 (package name input).
Suppresses installation output and auto-answers "no" to prompts for cleaner operation.

Use cases of Smithery MCP Batch Installer

Installing the same MCP server into Cursor, Windsurf, VS Code, and other clients in one go.
Rolling out a new Smithery server across multiple team environments with a single command.
Quickly testing a server across different editors to verify compatibility.

FAQ from Smithery MCP Batch Installer

What is the difference between v1 and v2?

v1 takes a full Smithery install command that includes --client cursor and replicates it for other clients. v2 takes only a package name (e.g., @mcpserver/openrouterai) and automatically constructs the full installation command for each client.

How do I customize which clients are targeted?

Edit the TARGET_CLIENTS array in the script file. For example, replacing it with TARGET_CLIENTS=("vscode" "intellij" "sublime" "atom"). The array does not need to include “cursor” for v1 because that client is run first.

What input does v1 of the script require?

A complete Smithery install command that includes --client cursor, such as npx -y @smithery/cli@latest run @smithery-ai/github --client cursor --key d708c05d-f7cc-48ee-907f-e9beb9b9f854.

What input does v2 of the script require?

A package name like @mcpserver/openrouterai. The script constructs the full install command automatically.

Does the script modify my Smithery key?

No. v1 uses the key as supplied in the install command; v2 reuses the same key across all client installations. The script only changes the --client argument.

Frequently asked questions

What is the difference between v1 and v2?

v1 takes a full Smithery install command that includes `--client cursor` and replicates it for other clients. v2 takes only a package name (e.g., `@mcpserver/openrouterai`) and automatically constructs the full installation command for each client.

How do I customize which clients are targeted?

Edit the `TARGET_CLIENTS` array in the script file. For example, replacing it with `TARGET_CLIENTS=("vscode" "intellij" "sublime" "atom")`. The array does not need to include “cursor” for v1 because that client is run first.

What input does v1 of the script require?

A complete Smithery install command that includes `--client cursor`, such as `npx -y @smithery/cli@latest run @smithery-ai/github --client cursor --key d708c05d-f7cc-48ee-907f-e9beb9b9f854`.

What input does v2 of the script require?

A package name like `@mcpserver/openrouterai`. The script constructs the full install command automatically.

Does the script modify my Smithery key?

No. v1 uses the key as supplied in the install command; v2 reuses the same key across all client installations. The script only changes the `--client` argument.