# mcprush [Health: Active]

**Category:** 🔗 Aggregators  
**Repository:** https://github.com/mcprush/mcprush-cli  
**GitHub Stars:** 1  
**npm Downloads (last month):** 1345  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mcprush

## Description
Install MCP servers and agent skills from mcprush.com into the client you already use, through one gateway and one key.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcprush": {
    "command": "npx",
    "args": ["-y","mcprush@latest"]
  }
}
```

## Documentation

## What mcprush does

The mcprush MCP server CLI connects the mcprush.com marketplace with supported MCP client configurations. It resolves listings by publisher and name, records gateway installs against an account, and writes the resulting server entry into a client configuration. A bare listing name is accepted only when it is unambiguous; otherwise, the command shows the matching publishers and their package and download information.

Gateway-backed servers use one marketplace address and the account key associated with the install. Direct listings work differently: the client starts the published npm, PyPI, Docker, or HTTP server itself, with no mcprush gateway in the request path. The CLI prints the command or address it writes, along with required setup steps and variables when the listing provides them.

Skills are folders of text instructions rather than server endpoints. The mcprush MCP server writes them to the location expected by the selected client, such as `.claude/skills/` or `.cursor/skills/`. It records the written files in `.mcprush.json`, and removal uses that manifest to delete only files created by the tool.

## How it works

Authenticate with `npx mcprush@latest login`, then install a server with `npx mcprush@latest add <publisher>/<server>`. `skill add` installs a skill folder, while `stack add` processes a curated group of listings. A free skill can be downloaded without an account; paid skills require the key for an account that has purchased access in the browser.

The CLI does not start server commands. For direct entries, it writes bounded launch commands such as `npx`, `uvx`, or `docker run`, or records an HTTP address for a process you start separately. Gateway entries point to the marketplace service. The tool also prints one-time initialization or author-provided installation instructions when a listing cannot be represented as a single client entry.

## Setup and configuration

Run the commands through `npx` so the current package version is used. The CLI writes into the selected client's existing configuration and keeps a `.bak` copy of the previous file, using restrictive file permissions for configurations containing keys. It will not overwrite an entry it did not create unless `--force` is supplied.

Malformed or unsupported configuration files are not rewritten automatically. Instead, the CLI stops and prints the configuration to paste manually. Zed and VS Code JSONC files receive special handling: Zed is edited in place where possible, while VS Code comments are removed on write and the original is preserved as a backup.

## Tools and capabilities

- Add gateway or direct MCP servers to client configuration.
- Install and remove marketplace skills with manifest tracking.
- Add curated stacks containing gateway and direct listings.
- Resolve publisher-qualified names and report ambiguous matches.
- Pass supported package, Python, Docker, port, volume, and environment settings from listing metadata.
- Preserve user-owned entries and show manual steps for unsupported listings.

## Limitations and notes

The mcprush MCP server does not execute downloaded skills, start direct servers, or take payment for paid listings. Skills are written as files; executable permissions may be preserved for files beginning with `#!`, but execution is left to the client. Skill paths are constrained to the skill's own folder.

Direct launch entries are restricted to marketplace-defined package, image, address, and launcher forms. Sensitive launcher controls and broad host-environment settings are not written into entries. Removing a skill is local and does not require the marketplace, but the CLI will not remove or replace a folder without its matching manifest unless forced. Account removal also respects marketplace rules for installs that cannot be canceled from the terminal.

_Full upstream README: https://allmcps.com/mcp/mcprush/readme_