Skip to content
Back to search

install-mcp

A simple CLI to install MCP servers into any client - auth included!

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/supermemoryai--install-mcp/badge.svg)](/listings/supermemoryai--install-mcp)

HTML

<a href="/listings/supermemoryai--install-mcp"><img src="/api/listings/supermemoryai--install-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

A CLI tool to install and manage MCP servers.

Installing MCPs is a huge pain, so I made a CLI tool to make it easier.

Usage

The CLI now supports multiple installation methods with automatic detection:

Simple package names

npx install-mcp mcp-package-name --client claude-desktop

Scoped packages

npx install-mcp @org/mcp-server --client claude-desktop

Full commands (for custom arguments)

npx install-mcp 'npx some-mcp-server --custom-args' --client claude-desktop

Remote URLs (with automatic naming)

npx install-mcp https://mcp.example.com/server --client claude-desktop

The tool automatically:

- Converts simple package names to `npx package-name` - Preserves full commands as-is - Infers server names from package names or URLs (e.g., `mcp.example.com` → `mcp-example-com`) - Handles OAuth authentication for remote servers

Supermemory project support

When installing a server hosted on `https://api.supermemory.ai/*`, you can pass a project name via `--project`. This is a convenience alias for adding the header `x-sm-project: <value>`.

Rules:

- Only applies to URL installs targeting `https://api.supermemory.ai/*`. - Values must not contain spaces. - If you omit `--project` for these URLs, you'll be prompted. Pressing Enter uses `default`. - The value is injected as a header alongside any `--header` flags.

Examples:

# Explicit project
npx install-mcp https://api.supermemory.ai/servers/my-server \
  --client cursor \
  --project myproj

# Prompted for project (Enter defaults to "default")
npx install-mcp https://api.supermemory.ai/servers/my-server --client cursor

Warp users: the generated config will include `--header "x-sm-project: <value>"` in the `args` array when installing Supermemory URLs.

Headers Support

You can pass headers for authentication or other purposes using the `--header` flag:

# Single header
npx install-mcp https://api.example.com/mcp --client claude-desktop --header "Authorization: Bearer token123"

# Multiple headers
npx install-mcp https://api.example.com/mcp --client claude-desktop \
  --header "Authorization: Bearer token123" \
  --header "X-API-Key: secret-key"

OAuth Authentication for Remote Servers

When installing remote servers (URLs), the CLI will ask if the server uses OAuth authentication:

npx install-mcp https://api.example.com/mcp --client claude-desktop
# Output: Does this server use OAuth authentication? (Y/n)

You can bypass this prompt using the `--oauth` flag:

# Automatically run OAuth authentication
npx install-mcp https://api.example.com/mcp --client claude-desktop --oauth yes

# Skip OAuth authentication entirely
npx install-mcp https://api.example.com/mcp --client claude-desktop --oauth no

If you answer yes, the authentication flow:

- Runs automatically before installation - Handles OAuth flows seamlessly in the background - **Authentication state is shared globally** - once you authenticate with a server, that authentication is automatically available to all MCP clients - No need to re-authenticate when using the same server in different clients

# Output: Running authentication for https://api.example.com/mcp

If authentication fails, you'll see:

Authentication failed. Use the client to authenticate.

If the server doesn't use OAuth (you answer no), the installation proceeds directly without authentication.

This ensures secure access to remote servers while maintaining flexibility for servers that don't require OAuth.

Supported Clients

The `--client` flag specifies which MCP client you're installing for:

- `claude-desktop` - `cline` - `roo-cline` - `windsurf` - `witsy` - `enconvo` - `cursor` - `vscode` - `gemini-cli` - `claude-code` - `goose` - `zed` - `opencode` - `warp` (outputs config to copy/paste into Warp's cloud-based settings) - `codex` (OpenAI's Codex CLI tool) - `droid` (Factory.AI's Droid CLI tool)

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 146 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Install MCP CLI
  2. ### A CLI tool to install and manage MCP servers.
  3. Installing MCPs is a huge pain, so I made a CLI tool to make it easier.
  4. ## Usage
  5. The CLI now supports multiple installation methods with automatic detection:
  6. ### Simple package names
  7. ```bash
  8. npx install-mcp mcp-package-name --client claude-desktop
  9. ```
  10. ### Scoped packages
  11. ```bash
  12. npx install-mcp @org/mcp-server --client claude-desktop
  13. ```
  14. ### Full commands (for custom arguments)
  15. ```bash
  16. npx install-mcp 'npx some-mcp-server --custom-args' --client claude-desktop
  17. ```
  18. ### Remote URLs (with automatic naming)
  19. ```bash
  20. npx install-mcp https://mcp.example.com/server --client claude-desktop
  21. ```
  22. The tool automatically:
  23. - Converts simple package names to `npx package-name`
  24. - Preserves full commands as-is
  25. - Infers server names from package names or URLs (e.g., `mcp.example.com` → `mcp-example-com`)
  26. - Handles OAuth authentication for remote servers
  27. ### Supermemory project support
  28. When installing a server hosted on `https://api.supermemory.ai/*`, you can pass a project name via `--project`. This is a convenience alias for adding the header `x-sm-project: <value>`.
  29. Rules:
  30. - Only applies to URL installs targeting `https://api.supermemory.ai/*`.
  31. - Values must not contain spaces.
  32. - If you omit `--project` for these URLs, you'll be prompted. Pressing Enter uses `default`.
  33. - The value is injected as a header alongside any `--header` flags.
  34. Examples:
  35. ```bash
  36. # Explicit project
  37. npx install-mcp https://api.supermemory.ai/servers/my-server \
  38. --client cursor \
  39. --project myproj
  40. # Prompted for project (Enter defaults to "default")
  41. npx install-mcp https://api.supermemory.ai/servers/my-server --client cursor
  42. ```
  43. Warp users: the generated config will include `--header "x-sm-project: <value>"` in the `args` array when installing Supermemory URLs.
  44. ### Headers Support
  45. You can pass headers for authentication or other purposes using the `--header` flag:
  46. ```bash
  47. # Single header
  48. npx install-mcp https://api.example.com/mcp --client claude-desktop --header "Authorization: Bearer token123"
  49. # Multiple headers
  50. npx install-mcp https://api.example.com/mcp --client claude-desktop \
  51. --header "Authorization: Bearer token123" \
  52. --header "X-API-Key: secret-key"
  53. ```
  54. ### OAuth Authentication for Remote Servers
  55. When installing remote servers (URLs), the CLI will ask if the server uses OAuth authentication:
  56. ```bash
  57. npx install-mcp https://api.example.com/mcp --client claude-desktop
  58. # Output: Does this server use OAuth authentication? (Y/n)
  59. ```
  60. You can bypass this prompt using the `--oauth` flag:
  61. ```bash
  62. # Automatically run OAuth authentication
  63. npx install-mcp https://api.example.com/mcp --client claude-desktop --oauth yes
  64. # Skip OAuth authentication entirely
  65. npx install-mcp https://api.example.com/mcp --client claude-desktop --oauth no
  66. ```
  67. If you answer yes, the authentication flow:
  68. - Runs automatically before installation
  69. - Handles OAuth flows seamlessly in the background
  70. - **Authentication state is shared globally** - once you authenticate with a server, that authentication is automatically available to all MCP clients
  71. - No need to re-authenticate when using the same server in different clients
  72. ```bash
  73. # Output: Running authentication for https://api.example.com/mcp
  74. ```
  75. If authentication fails, you'll see:
  76. ```
  77. Authentication failed. Use the client to authenticate.
  78. ```
  79. If the server doesn't use OAuth (you answer no), the installation proceeds directly without authentication.
  80. This ensures secure access to remote servers while maintaining flexibility for servers that don't require OAuth.
  81. ## Supported Clients
  82. The `--client` flag specifies which MCP client you're installing for:
  83. - `claude-desktop`
  84. - `cline`
  85. - `roo-cline`
  86. - `windsurf`
  87. - `witsy`
  88. - `enconvo`
  89. - `cursor`
  90. - `vscode`
  91. - `gemini-cli`
  92. - `claude-code`
  93. - `goose`
  94. - `zed`
  95. - `opencode`
  96. - `warp` (outputs config to copy/paste into Warp's cloud-based settings)
  97. - `codex` (OpenAI's Codex CLI tool)
  98. - `droid` (Factory.AI's Droid CLI tool)
  99. - `aider` (AI pair programming tool)
  100. - `aider-desk` (Desktop version of aider)
  101. ## License
  102. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.