Swarms Marketplace MCP Server
Discover 6,000+ AI agents, prompts, tools, and MCP servers, then publish and monetize your own. One API, one MCP connection: swarms.world/mcp.
- Transport
- Streamable HTTP
- Protocol
- JSON-RPC 2.0
- Auth
- Bearer API key
swarms.world/mcp- Search agents, prompts, tools
- Read free listings in full
- Publish and edit as you
- Fees, reviews, bundles
Connect over MCP
The marketplace is an MCP server at https://swarms.world/mcp. Streamable HTTP, JSON-RPC 2.0, one tool per REST operation, generated from the OpenAPI spec so it never drifts. Every request needs your API key as a Bearer token.
get_get-prompts, get_get-agents_id, post_add-prompt… names are the HTTP method plus the REST path.
One text block whose text is JSON. Upstream failures come back as isError: true with the status and body, so an agent can recover.
The full skill, with every tool, argument, and error, is at /mcp-skill.md.
Call the REST API directly
Reads are public. Anything that publishes, edits, reviews, or touches your account needs the key. All endpoints are documented in the OpenAPI spec.
| Method | Path | What it does | Key |
|---|---|---|---|
| GET | /api/get-agents | Search agents | optional |
| GET | /api/get-agents/{id} | One agent (source when free) | optional |
| GET | /api/get-prompts | Search prompts | optional |
| GET | /api/get-prompts/{id} | One prompt by id or exact name | optional |
| GET | /api/get-tools | Search tools | optional |
| GET | /api/prompt-raw/{id} | Prompt as Markdown | optional |
| POST | /api/add-agent | Publish an agent | required |
| POST | /api/add-prompt | Publish a prompt | required |
| POST | /api/edit-agent | Edit an agent you own | required |
| POST | /api/edit-prompt | Edit a prompt you own | required |
| POST | /api/v1/publish/bundle | Publish a bundle | required |
| GET | /api/product/list | Your products | required |
| GET | /api/product/fees | Creator fees for a tokenized product | required |
| POST | /api/reviews | Submit a review | required |
Authentication
One key, three surfaces
A Swarms API key from swarms.world/platform/api-keys authenticates the marketplace REST API, the MCP server, and the Swarms API at api.swarms.world. Send it as Authorization: Bearer <key>.
What the key can see
Free listings return their body or source to anyone. Paid listings return metadata plus access_info until the account behind the key has purchased them. Publishing, editing, reviewing, and fee lookups act as that account.
Skills
Plain Markdown files written for agents, not humans. Drop one into .claude/skills, paste it into a system prompt, or point an agent at the URL.
MCP skill
Everything an agent needs to use the MCP server: auth, every tool with arguments and result shapes, workflows, errors, and troubleshooting.
OpenPublishing API skill
Payload schemas and examples for publishing agents and prompts, tokenizing, and claiming fees over REST.
Openllms.txt
The whole site indexed for language models: pages, endpoints, MCP tools, categories, and links. Give it to any agent as context.
OpenResources
Everything the marketplace exposes to code and to agents.
MCP server
The marketplace as a Model Context Protocol server. Every REST operation is a tool. Streamable HTTP, JSON-RPC 2.0, API key required.
OpenOpenAPI 3.1 specification
Machine-readable description of every marketplace endpoint with full request schemas. Regenerated on every deploy. Generate a client or feed it to an agent.
OpenAPI keys
Create and revoke Swarms API keys. One key works for the marketplace REST API, the MCP server, and the Swarms API at api.swarms.world.
OpenBulk publish
Import several GitHub repositories and publish them as agents in one pass from the browser.
OpenSwarms API
Run agents and multi-agent swarms on nearly 2,000 models. Docs, examples, rate limits, and the hosted MCP server at mcp.swarms.world.
OpenSDKs and framework
swarms (Python) is the open-source framework the marketplace is built around. Official SDKs in Rust and TypeScript.
OpenSupport
Email, Discord, Telegram, and demo booking. Service status at status.swarms.ai.
OpenFAQ
Do I need an API key?
For reads over REST, no: searching and fetching listings is public. For the MCP server, publishing, editing, reviewing, and anything about your own account, yes. Create one at swarms.world/platform/api-keys and send it as Authorization: Bearer <key>.
What is the difference between the MCP server and the REST API?
They expose the same operations. The REST API is plain HTTP for your own code. The MCP server wraps every REST operation as a tool that an agent can discover and call by itself over the Model Context Protocol, so you connect once and the agent does the rest.
How do the MCP tools stay in sync with the API?
The tool list is generated from the OpenAPI document at swarms.world/openapi.json, which is itself built from the route source on every deploy. A new endpoint becomes a tool automatically; nothing is hand-maintained.
Why does a paid listing come back without its prompt or source?
Free listings return their body or source to anyone. Paid listings return metadata plus an access_info object until the account behind your key has purchased them on swarms.world.
Can I run agents through the marketplace API?
Running models is the job of the Swarms API at api.swarms.world, documented at docs.swarms.ai, and it accepts the same key. The marketplace API is for the catalog: finding, reading, publishing, and monetizing listings.
What are the rate limits?
The marketplace API and the MCP server share a limit of 300 requests per minute per IP. The Swarms API has its own tiered limits, returned in X-RateLimit-* headers on every response.
Can I tokenize a listing programmatically?
Yes. The add-agent and add-prompt endpoints accept tokenization fields, including the creator wallet and a signing key. Only do that from infrastructure you control, never through a shared MCP host, and read the tokenization guide on docs.swarms.ai first.