Blender integration through the Model Context Protocol
Tools for your agent.
Revenue for whoever built them.
A marketplace for MCP servers and agent skills: publishers list them and get paid, and you subscribe to what you need — free, or by the month. Install any of it in one command into whatever AI tools you already use; we handle OAuth and the payouts to publishers.
npx mcprush@latest add <server>
What is being pulled from the MCP marketplace right now
The first tab is the last twenty-four hours of package downloads, counted by npm and PyPI rather than by us. Best free is the same figure over the whole life of the package. Highest trust is our scanner's letter first, and among servers holding the same letter the one people pull most — and only servers that actually publish tools, because a server with none is a grade about nothing.
Chroma’s official MCP server: vector search and collection management for RAG workflows.
Plug and play auth for Model Context Protocol (MCP) servers
A flexible arXiv search and analysis service with MCP protocol support
Clean, LLM-optimized Reddit MCP server. Browse posts, search content, analyze users. No fluff, just Reddit data.
An MCP server that provides access to arXiv papers through their API.
MCP server + public atlas of timeline-shift folklore, Mandela Effect reports, and collider-era myth — every claim labeled, every source
MCP server that gives Claude Code the ability to watch and understand videos — extracts frames via ffmpeg and processes audio via multiple
Twenty-eight categories, one permission model
A server gives your agent hands.
A skill tells it what to do with them.
An agent skill is a folder of instructions — a SKILL.md and whatever reference files it needs — that loads into the context window only when the work matches. It changes how the model decides. It does not change what the model can reach, which is still the server's job.
You type “review this PR before I push” and the instructions arrive. On every other turn they are not in the context window at all, so an installed skill you never invoke costs you nothing.
The listed skills weigh between 25 and 1,067,300 tokens. That is the number the catalogue filters on, and the budget tray totals a selection before you install any of it. 6,128 of the 8,089 are open source; seventy-six of them are paid once — there is nothing on a skill to meter, and one price buys the folder and every update its author ships inside it. The files stay on your disk whatever happens next.
461 of the 8,089 call an MCP server to do their work, and the card names how many. The other 7,628 are instructions only — no install and no scopes, though a skill can still carry a price.
Four free ones from four publishers you already know, picked as examples of a skill written out in full — the folder, the trigger, the licence and what it weighs. Every other skill in the catalogue is filed the same way.
Create beautiful visual art in .png and .pdf documents using design philosophy.
Train or fine-tune language and vision models using TRL or Unsloth with Hugging Face Jobs infrastructure.
Use this skill when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform, multi-vendor store, gig platform, or subscription platform, needs to pay out sellers, vendors, or providers, mentions spli
Automate browser interactions, test web pages and work with Playwright tests.
Three desks, already assembled
A pack is a set of skills that expect each other — a procedure, the voice it should be written in, and the guards that stop it going too far. Each pack mixes open-source skills with licensed ones and prices the set; what you weigh alongside that is context, which the tray totals before you install. These zero are every pack there is; the 8,089 skills they draw from are in the catalogue.
Install once. Your whole toolchain sees it.
mcprush speaks Streamable HTTP and stdio, so the same server drops into every MCP client you use. Team installs roll out to everyone's config automatically — and revoke just as fast.
# one file, committed to your repo
servers:
- id: <server>@<version>
budget: $40/mo
approve: [<tool>]
- id: <server>@<version>
scopes: [read]
- id: <server>@<version>
The risk of a tool is not its code. It's its reach.
A listing published here is scanned on publish and re-scanned on every release, and its report is on its own page. A listing imported from a public index is scanned from that public source instead, and its grade says which release it covers; where there is nothing to read, the page says so rather than inventing a letter. What you approve is a capability budget — not a promise.
Capability scopes, in plain language
"Reads your repo", "sends email on your behalf", "can reach any host". Declared in the manifest, enforced at the gateway, shown before install.
Network reach, named before you install
A listing's tools are labelled read, write or network from its manifest, and the network ones are named on its page. We do not yet hold a per-host allowlist, and the gateway does not refuse a call by its destination.
A scan report for every release
Tool descriptions are prompts. Every release gets its own scan report, with a digest of that release's tool surface and the tools it declares — so a surface that moved leaves a different digest. Warning you when it does is not built yet.
Pin, diff, roll back
Installs resolve to an exact release, fingerprinted by the scan of that build. Pin or move an install to any published version of a listing from its own page.
Charge for your server without building a billing system.
Ship the tools. We do identity, rate limits, plan allowances, invoices, dunning and tax; Stripe Connect holds your bank details and pays you. A paid listing runs on your own infrastructure and reaches buyers through our gateway, so an expired subscription stops working without you writing a line of billing code — or list it free and keep the distribution.
Install a whole desk, not one tool at a time
Curated bundles with a shared budget, one approval flow and a single line in your config.
Reads the branch, runs it in a throwaway sandbox, and leaves the review on the merge request before a human opens it.
Turns a bug report into a reproduction that fails, before anybody writes a line of the fix.
Answers the page: what fired, what changed, what the runbook says, and what to tell the channel.
Writes the migration, proves it on a branch, and says what it will do to the table before it touches the real one.
The parts people ask about twice
Give your agent a toolbox worth trusting.
Install in one command. Pay the listing’s own price and nothing to us. Cancel, cap or roll back from the same place you installed.