Four of these write a config entry, so the client knows what to start or what address to call. skill add writes no config entry at all — it writes the skill's own files into your client's skills folder, because a skill has no endpoint and those files are the whole of it. A server behind our gateway runs on the publisher's machine and the entry is an address with your key; a server that runs locally is a command your client starts on yours, and the entry is that command — the one its own page prints. A skill is text and is never executed.
| Command | What it does | Printed on |
|---|---|---|
| npx mcprush@latest add <server> | Installs a free or bought server that runs behind our gateway into Claude Code’s config. Needs a key (login). For any other server, copy the line from its page. | Home · listing page · docs |
| npx mcprush@latest add <server> --client <client> | The same for claude-desktop, cursor, vscode, zed, devin or windsurf. For Claude Desktop it writes an mcp-remote bridge entry, so Node.js is needed. | Listing page |
| npx mcprush@latest add-list <list> | Installs the free or bought gateway servers from one of your saved lists and names the rest. | Library |
| npx mcprush@latest stack add <stack> | Writes every server in the stack it can into the client’s config, each with its own start line. Skips skills and paid members you haven’t bought, and names them. Needs a key; no dry run. | Home · stacks · stack page |
| npx mcprush@latest skill add <skill> | Writes the skill’s files to your client’s skills folder: .claude/skills/<skill>/ in the project for Claude Code, or your home folder with --global. A free skill needs no key. A folder you changed is kept unless you add --force. | Skill page · docs |
The commands that answer “what is this costing me” and “is this the thing I approved”. They read the same figures the dashboard prints — an operator quoting a number the buyer cannot see is a number nobody can check.
| Command | What it does | Printed on |
|---|---|---|
| npx mcprush@latest budget --max '$900/mo' --alert 80% | Sets the account’s monthly spending cap and when to warn you (a % of it). It is checked when you buy, not on each call. Owner or billing manager only; changing it also needs a write key. | Only here |
| npx mcprush@latest list | What this account has installed, and which of them are paused. | Only here |
| npx mcprush@latest remove <server> | Takes the server out of the client and off the account; use the same --client as for add. An install with saved variables needs a write key. A monthly subscription is cancelled in Dashboard → In use instead. An entry this tool did not write is kept unless you add --force. A server that stack add wrote with its own start line is removed only with --force. | Only here |
| npx mcprush@latest skill remove <skill> | Deletes the files it wrote and keeps files you added or changed (--force deletes the whole folder). Use the same flags as for skill add. No key needed. | Only here |
| npx mcprush@latest clients | Lists the clients: ✓ this tool writes its config (the file is shown), · you set it up by hand. | Only here |
A key belongs to an account and can be revoked from the dashboard the moment it leaves your machine.
| Command | What it does | Printed on |
|---|---|---|
| npx mcprush@latest login | Checks a key from Dashboard → Access and saves it in ~/.mcprush/config.json. Needs Node 20+. | Checkout, after a purchase |
| npx mcprush@latest whoami | Which account your key belongs to, its plan, the key’s scope, when it expires and how many servers are installed. | Only here |
| npx mcprush@latest logout | Forgets the key login saved. Entries it wrote into your clients keep their own copy until you revoke the key in Dashboard → Access. | Only here |
| npx mcprush@latest relink | After you log in with a new key, writes it into every entry this tool wrote in your clients, so they stop getting 401. --client narrows it to one. | Only here |
Nothing here requires our tool. These are the client's own commands and the plain HTTP route, printed because a reference that pretends to be the only way in is a reference nobody trusts.
| Command | What it does | Printed on |
|---|---|---|
| claude mcp add --transport http --scope user <server> https://mcprush.com/gw/<server>/mcp --header 'Authorization: Bearer ${MCPRUSH_KEY}' | Claude Code’s own command, no Node needed. The single quotes keep ${MCPRUSH_KEY} as written in every shell, PowerShell too: Claude Code reads MCPRUSH_KEY from your environment each time it starts the server, so the key never lands in its config. Export it in your shell profile (macOS, Linux) or run setx MCPRUSH_KEY <key> and open a new terminal (Windows); without it claude mcp list names the missing variable. | Listing |
| curl -fsS https://mcprush.com/api/skills/<skill-id>/bundle.tar.gz -H "Authorization: Bearer $MCPRUSH_KEY" | tar -xz | The skill’s folder as a tar.gz, without Node (macOS, Linux; on Windows use the npx line). Copy <skill-id> from the download line on the skill’s page: it is not always the part after the slash. The key is needed only for a paid skill. If it stops at 401 or 403, run the curl part alone without -f: it says why, with the checkout link when a purchase is what’s missing. Read the files first: some skills include scripts. | Skill page · docs |
npx mcprush@latest --help is the tool saying the same thing about itself.