The Claude Code plugin marketplace has no price field

Anthropic's Claude Code plugin marketplace is a JSON file in a git repository with no field for pricing, meaning developers cannot sell plugins through the official system. The schema, verified against official docs and a 66,972-server index on August 2, 2026, includes fields for license, category, and tags but no monetary value, and distribution relies on git hosts like GitHub or GitLab. Anthropic provides three marketplaces—official, community, and demo—with the community one pinning plugins to commit SHAs for security.

← All guides /blog The Claude Code Plugin Marketplace Is a JSON File in a Git Repo. The Only Price Tag in the Spec Is Measured in Tokens. What is the Claude Code plugin marketplace, how do you add one, and why can nobody sell you a plugin? The full manifest schema has fields for license, category and tags, and no field for money. Checked against the docs, the MCP registry API, and a 66,972-server index on August 2, 2026. Someone asks how to make money building Claude Code plugins about once a week now. You don't need a strategy post to answer it. You need to read one JSON schema, and that takes about a minute. The Claude Code plugin marketplace is a file called marketplace.json , sitting in a .claude-plugin/ directory in a git repository. That's the whole mechanism. You point Claude Code at a repo, it reads the JSON, and the plugins listed inside become installable. There is no storefront, no seller account, and no field anywhere in the specification where a price could go. This piece walks through what the marketplace actually is, how to add one, and what the shape of the spec tells you about whether this layer will ever pay its creators. Everything below was checked against the official documentation, the MCP registry API schema, and a live server index on August 2, 2026. What a Claude Code plugin marketplace actually is A plugin is a directory of components: skills, agents, hooks, MCP servers, LSP servers. A marketplace is a catalog listing those plugins and where to fetch each one. The catalog is a single JSON file. At the top level it takes name , an array of plugins , and optionally $schema , description , version , metadata.pluginRoot , allowCrossMarketplaceDependenciesOn , and renames . Each entry in the plugins array requires exactly two things: name and source . The source is where the plugin lives, and it can be a GitHub repo, a git URL, or a relative path. You host it by pushing to GitHub, GitLab, or any git host. You update it by pushing a commit. Users pull the change with /plugin marketplace update . That's the entire distribution system. It's npm -shaped in the sense that it resolves names to repositories, and unlike npm it doesn't even have a registry service in the middle. How to add a plugin marketplace Three marketplaces come from Anthropic, and they behave differently. The official one, claude-plugins-official , is added automatically when Claude Code starts. You only add it by hand if your network blocked the download: /plugin marketplace add anthropics/claude-plugins-official /plugin install github@claude-plugins-official It's curated, and the docs are direct about what that means: inclusion is at Anthropic's discretion. It holds the language server plugins pyright-lsp , rust-analyzer-lsp , and nine others , the pre-configured MCP integrations for GitHub, Linear, Notion, Figma, Sentry and friends, plus workflow plugins like commit-commands and pr-review-toolkit . The community one is where third-party work goes. It's a public repo, and you add it yourself: /plugin marketplace add anthropics/claude-plugins-community /plugin install <name @claude-community Everything in it passed automated validation and safety screening, and each plugin is pinned to a specific commit SHA in the catalog. That pinning is the security model: you're not trusting a moving branch. The demo marketplace lives in the main anthropics/claude-code repo and exists to show what the system can do. For anything else, you point at a repository directly. GitHub shorthand, a full git URL with a branch suffix, a local directory, or a bare URL to a hosted JSON file: /plugin marketplace add your-org/claude-plugins /plugin marketplace add https://gitlab.com/company/plugins.git v1.0.0 /plugin marketplace add ./my-marketplace /plugin marketplace add https://example.com/marketplace.json Teams skip the manual step by putting extraKnownMarketplaces in the project's .claude/settings.json , and everyone who trusts the folder gets prompted to install. Nothing in that flow touches a payment. Adding a marketplace is a clone. Installing a plugin is a copy into ~/.claude/plugins/cache . What the schema has room for, and what it doesn't Here is the full set of optional fields a plugin entry accepts: displayName , description , version , author , homepage , repository , license , keywords , category , tags , strict , relevance , defaultEnabled , plus the component paths skills , commands , agents , hooks , mcpServers , lspServers . There's a field for what your plugin is called in a UI, a field for tags so people can find it, a field for whether it starts enabled, and a field telling Claude when to suggest it. Somebody thought carefully about discovery. The only field within a mile of commerce is license , and it wants an SPDX identifier: MIT, Apache-2.0. It's there so a machine can tell whether the code is open, not so a human can be charged. There is no price , no currency , no checkout url , sku , trial , or license key . None of these were deprecated or marked as coming later. The concept has no slot in the data model. The only cost the marketplace reports is measured in tokens Open /plugin , go to the Discover tab, select a plugin, and the details pane shows you, in the docs' own words, what it contains and what it costs. That's the part I keep coming back to, because there is a Context cost row: an estimate of how many tokens the plugin adds to your context window every turn. So the system does have a price tag. It's denominated in tokens, it's charged on every request rather than once at purchase, and it's paid to the model provider rather than to the person who built the thing. The Not used recently header in the Installed tab exists for the same reason: plugins you installed and stopped invoking keep costing context, and the UI nudges you to find them. The economics of this marketplace are entirely about the buyer's ongoing overhead. The creator isn't a party to the transaction, because there isn't one. The same hole shows up everywhere else in the layer I went looking for a counterexample in the two other places this ecosystem congregates. The official MCP registry publishes its API schema, and a server there has name , description , title , repository , version , websiteUrl , icons , $schema , packages , remotes , and meta . Same story: identity, location, versioning, no commerce. Then Glama, the largest public MCP directory. On August 2, 2026 it listed 66,972 servers. Not one of them carries a price, because there's nowhere to put one. Licenses skew MIT and Apache-2.0. For scale on how fast the supply side is filling: the same index read 66,930 the previous day. Forty-two new servers in twenty-four hours, all free, in a market with no mechanism to be anything else. Distribution here is structurally incompatible with selling. A plugin marketplace is a git repo the user clones. MCP servers install from public repositories. A paywall is only technically possible if there's a server component holding a license check, which means you're selling a SaaS and the plugin is just its client. Why the free layers are free and the paid layers are paid Look at the wider template economy and the line is sharp. It has nothing to do with platform size or generosity. Framer pays creators at 0% commission and published $6.5M paid out over 2025. Webflow moved to 95% for creators in October 2025. Figma Community sits at 15% and has closed new seller intake. These are places where somebody sells a designed layout. Now the other side. n8n has no payment mechanism at all: a scan of all 11,128 templates in its public API found a median of 30 sales and $308 in lifetime revenue per paid template, with the entire paid catalog around $374K. ClickUp, Airtable, Asana, Linear, Slack and Miro pay creators nothing, because templates are their own content marketing, and Miro says so in plain text. Lovable, Replit, Bolt and v0 have no creator payments either. Those figures come from a market scan run August 1, 2026, across twenty-five platforms. The dividing line is craft versus configuration. Where the artifact is a designed thing a model can't yet reproduce, a cash register exists and the commission falls toward zero to attract creators. Where the artifact is a set of rules and settings that a model regenerates from a paragraph of description, no cash register ever appeared. Agent tooling is the purest case of configuration anyone has built: a skill is a markdown file, a rule is a paragraph, an MCP server is a thin adapter over an API somebody else runs. The layer didn't fail to develop payments. There was never anything here you could sell, and three separate schemas say so. The second-order version of this is already visible elsewhere: Webflow paused its own AI app generator after five months and raised creator payouts to 95%, while Bubble leaned into its AI builder and watched its marketplace stall to the point where a seller reported roughly $1,000 for 500+ hours of work. Platforms that build the generator kill the market for the artifact the generator makes. So what does get paid here One model works, and it isn't a plugin. You sell a service, and the plugin is the client that connects to it. That's Readwise inside Obsidian. That's a Copilot Plus subscription at $14.99 a month. The free artifact is distribution; the recurring charge sits behind an API key on a server you control. So the practical read for anyone eyeing this space is short. Don't plan on selling plugins, skills, MCP servers, or rule packs, because there is no mechanism and its absence is a design decision. Do treat a widely installed plugin as a distribution channel for something that bills. Getting into claude-plugins-community costs nothing and puts your name in front of people already running an agent. And if you want the version of this that does pay today, look at the markets on the other side of the craft line. Framer takes 0%, dropped its review requirement in June 2026 so anyone can publish, and runs a referral program paying 50% of a referred user's subscription for twelve months. That last one is often worth more than the template sales. FAQ What is the Claude Code plugin marketplace? A marketplace.json file in a .claude-plugin/ directory of a git repository, listing plugins and where to fetch each one. Claude Code reads it and makes those plugins installable. How do I add a plugin marketplace? /plugin marketplace add owner/repo for GitHub, or pass a full git URL, a local path, or a URL to a hosted JSON file. The official Anthropic marketplace adds itself on startup. Is there an official Claude Code plugin marketplace? Yes, claude-plugins-official , curated by Anthropic and added automatically. Separately there's anthropics/claude-plugins-community for third-party plugins that passed automated safety screening, which you add manually. Can you sell Claude Code plugins? Not through the marketplace. The manifest schema has no field for price, payment, or license keys, only an SPDX license string. Charging requires a server component your plugin authenticates against, which makes the product a SaaS rather than a plugin. How much do plugins cost? Nothing in money. Each one costs context tokens on every turn, which the plugin detail view reports as a Context cost estimate. Sources checked August 2, 2026: Claude Code plugin marketplace and plugin reference documentation, the Model Context Protocol registry OpenAPI schema, and the Glama MCP server index. Platform commission and payout figures come from a twenty-five-platform market scan dated August 1, 2026. Figures in a live market go stale; the dates are there so you can re-check them.