Log inSubmit server
Mcprush logo

Mcprush

Installs MCP servers and agent skills from mcprush.com into supported client configurations through one account gateway.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Mcprush

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcprush": {
      "command": "npx",
      "args": [
        "-y",
        "mcprush@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y mcprush@latest

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 5d ago.

Overview

The mcprush MCP server CLI installs MCP servers and agent skills from mcprush.com into the client you already use. It can add gateway-backed listings, configure direct servers, install curated stacks, and place skill folders in client-specific locations. Use it when you want marketplace resolution and client configuration handled from the command line without the tool launching server processes itself.

Use cases

  • Install a marketplace MCP server into an existing client
  • Add a curated stack of direct and gateway servers
  • Write agent skills into Claude Code or Cursor folders
  • Preserve backups while updating client configuration
  • Review manual setup steps for unsupported listings

Key features

  • Publisher-qualified server resolution
  • Gateway and direct server installation
  • Client configuration writing with backups
  • Skill folder installation and manifest-based removal
  • Curated stack installation
  • Bounded Docker, uvx, npm, and HTTP entries

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · mcprush@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1.3kPackage downloads in the last 30 days.
Last commit8d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Mcprush works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Mcprush

mcprush is an MCP server installation CLI that connects mcprush.com listings to supported client configurations. Its main tools are `add` for gateway or direct servers, `skill add` for agent skill folders, and `stack add` for curated groups. It also supports login, removal, name resolution, and configuration backups.

Run `npx mcprush@latest login`, then use `npx mcprush@latest add <publisher>/<server>`. Login obtains an account key for gateway-backed or paid listings. Direct listings can be added without a key, and the CLI writes the appropriate client configuration entry.

Yes, mcprush can write skills to Cursor's `.cursor/skills/` location and can add server entries to supported client configuration files. The CLI determines the client-specific destination and preserves a backup before changing a configuration.

Yes, mcprush writes configuration entries and does not start server processes itself. For direct listings, it prints the command your client will run, such as an npm, uvx, or Docker command, or records an HTTP address for a separately running server.

Run `skill remove` for the installed skill. Removal uses the skill's `.mcprush.json` manifest and deletes only files written by mcprush, leaving your notes and edits intact. A folder without the matching manifest is not removed unless `--force` is used.

Related MCP servers

All in Aggregators All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMcprush AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcprush?style=directory)](https://allmcps.com/mcp/mcprush)
HTML Embed
<a href="https://allmcps.com/mcp/mcprush"><img src="https://allmcps.com/api/badge/mcprush?style=directory" alt="Mcprush on AllMCPs" /></a>