Sell MCP servers
An MCP server is a connector. It lets an assistant or an agent call a tool or read data through the Model Context Protocol. If you already built one that other people would configure, you can sell that package.
Live listings
MCP servers listed here.
No live listings in this shelf yet. Open MCP servers or browse the catalog.
The product is the connector, not the model
Buyers are not paying you for Claude or ChatGPT. They already have a client. They are paying for the server that exposes a careful set of tools: search the help desk, create a task, read a table, file a page. The valuable part is the permission boundary and the tool descriptions that make the model call the right function. A thin wrapper that dumps an entire admin API into the model is a liability, and it is a hard sell to anyone who has operated one.
Write down the client you tested. A server that runs in a local process is a different product from a remote server you host. Say which one the buyer gets. Say how secrets are stored. “Put your key in the config” is acceptable if you say which file and whether it stays on their machine. “Send your key to my website” needs a much clearer reason.
What the listing must include
The list of tools, and for each tool whether it reads or changes data. The auth method. The install steps for the client you tested, in order, with the config snippet and the secrets redacted in the public page. The runtime: Node, Python, Docker, or a hosted URL. What the buyer needs from the third-party app, such as a token with a named scope. A short transcript of a real tool call, including one the server refused.
Support belongs in the scope. “I answer install questions for 14 days” is a product. “Message me sometime” is not. If you will not update the server when the upstream API changes, say that. MCP clients move quickly. A server sold as finished, with no updates, can be honest. A server sold as maintained has to name the period.
Safety is the sales page
The buyer is about to let a model call your tools. They will look for least privilege. If a tool can delete, the listing should say so in the first screen, not in a comment in the code. If tools are read-only, say that too, because it is a reason to buy. Offer a way to disable the dangerous tools in config.
An optional code audit on AIMarket24 covers security, dependencies, quality, and license, and a pass shows as a badge. It is a reasonable extra for a server that holds tokens. It is not required. Do the obvious cleanup yourself first: no keys in the repo, pinned dependencies, a license that allows the sale. The marketplace also rejects uploads that are 95% or more similar to an existing listing.
Money
Listing is free. AIMarket24 keeps 15% of each sale. The first 50 sellers who publish a live listing are founding sellers and pay 5% for six months. The buyer pays into escrow. You are paid after they confirm delivery, or automatically 3 days after delivery if no problem is reported. The price should reflect the hours a developer would spend to learn the upstream API and to write tool descriptions the model actually follows. A one-endpoint server is a small product. A server that covers a real app, with pagination, errors, and read versus write split, is a larger one. This page does not invent a going rate.
If you host the server, decide whether the price is the software, a month of hosting, or both. Hosting has a cost after the sale. Put it in the listing so the buyer does not treat a setup fee as a forever plan. If the buyer hosts it, your cost stops at support, and the price can be a single payment.
Who the buyers are
Developers wiring an IDE assistant. Teams that want Claude or another MCP client to see one internal tool without pasting data into a chat. Agent builders who need a connector they can ship beside their agent. They all read the tool list first. They leave if the list is “various endpoints.”
They are not, by default, the same people who buy a prompt pack. Link them to the explainer if they are new to the protocol, and to the marketplace guide if they are comparing servers. If what you built is really a full agent with the server inside it, sell the agent and mention the server as a part, so the product type matches the delivery.
When you publish
The marketplace is live. A seller account includes 7 days of Premium and 50 build tokens. Tokens pay for workshop builds at $1 each. They do not change the 15% commission. Founding seats are claimed when you publish a live listing, and only the first 50 of those seats get 5% for six months.
Prepare the repo without secrets, the tool list, and the install notes now. The public listing should be understandable by someone who has used MCP once, not only by you. If you cannot explain a tool in one sentence, the model will not use it well either, and the buyer will notice during the escrow window.
Frequently asked questions
Can I sell an MCP server on AIMarket24?
Yes. List it as a plugin or MCP server, with the tools, auth, runtime, and install steps.
Do I have to host it?
No. Say whether the buyer runs it locally or you host it. Those are different products.
What is the fee?
15% of the sale, or 5% for six months for the first 50 sellers who publish a live listing.
When can I publish?
The marketplace is live.