# SaaS app marketplaces: where to list your product 19 marketplaces where a SaaS can get its own listing, like an app store. Most need a small build first (an MCP server, browser extension, CLI or integration). Checked against official docs; domain rating from Ahrefs. ## Claude List your MCP server in the Claude connectors directory. You get a page on claude.com and people can connect your product in a few clicks. - Guide: https://indiehustles.com/marketplaces/claude - Official docs: https://claude.com/docs/connectors/building/submission - You need: MCP server - You build: A remote MCP server for your product. - Who's there: Claude users looking for tools to connect, often for work. - Domain rating: 92 - Link to your site: Dofollow - Cost: Paid Claude plan - Review: Automatic scan, sometimes manual ### Steps 1. Make sure your MCP server runs on an https URL. Use OAuth if tools touch a user account. 2. Give every tool a title and mark it read-only or destructive. 3. Add your server to Claude as a custom connector and try each tool. 4. Go to claude.ai/directory/manage, click Submit new and pick MCP connector. 5. Fill in the listing: name, one-liner, description, icon, docs and privacy links, support contact, and a test account for reviewers. 6. Submit and track the status in the same portal. ### Good to know - Free Claude accounts can’t submit. Pro, Max, Team or Enterprise all work. - New listings start as Community. Anthropic may later mark yours Verified, with no extra steps. - The public page at claude.com/connectors/ can be indexed by Google. The in-app directory can’t. ## ChatGPT Publish a plugin to the ChatGPT directory so users can add your product right from the chat. The same directory feeds Codex. - Guide: https://indiehustles.com/marketplaces/chatgpt - Official docs: https://developers.openai.com/plugins/deploy/submission - You need: MCP server, OAuth login - You build: An MCP server with OAuth, packed as a plugin. - Who's there: ChatGPT and Codex users asking for a tool to get something done. - Domain rating: 93 - Link to your site: Not confirmed - Cost: Free - Review: Manual, often 2 to 6 weeks ### Steps 1. Verify your identity or business in your OpenAI Platform organization settings. 2. Build a plugin zip: a manifest, optional skills, and your MCP server config. 3. Serve the domain check file at `/.well-known/openai-apps-challenge` on your MCP server. 4. Upload the zip at platform.openai.com/plugins and fix anything the automatic scan flags. 5. Add 5 test cases, 3 negative test cases, a test account without 2FA, and a demo video. 6. Submit. Once approved, you choose when it goes live. ### Good to know - API key auth isn’t supported in the portal. Use OAuth, or ship a skills-only plugin with no server. - You need website, support, privacy policy and terms links, all on https. - Don’t put “MCP”, “Server” or “Plugin” in the name. ## Official MCP Registry Publish your MCP server to the official registry in a few minutes. It has no page of its own, but other MCP directories, like Glama, pull from it. - Guide: https://indiehustles.com/marketplaces/mcp-registry - Official docs: https://modelcontextprotocol.io/registry/quickstart - You need: MCP server - You build: Nothing new if you already have a remote MCP server. - Who's there: Mostly other directories and AI apps that read the registry and list what’s in it. - Domain rating: 91 - Link to your site: No link - Cost: Free - Review: None ### Steps 1. Install the publisher: `brew install mcp-publisher`. 2. Run `mcp-publisher init` to create `server.json`. 3. Set a name like `com.yourdomain/yourserver`, a title, a description, a version, and your server URL under `remotes`. 4. Prove you own the domain: make a key, add the TXT record from the docs, then run `mcp-publisher login dns --domain yourdomain.com --private-key `. 5. Run `mcp-publisher publish`. ### Good to know - Do this first. It’s the quickest way to show up on other MCP directories. - Use a GitHub login instead of DNS if your name starts with `io.github./`. - The registry is still in preview, so expect changes. ## Glama One of the largest MCP directories. If you’re on the official registry, your page is likely already there. Claim it and fix the details. - Guide: https://indiehustles.com/marketplaces/glama - Official docs: https://glama.ai/mcp/connectors - You need: MCP server - You build: Nothing new. You claim the page and improve your tool descriptions. - Who's there: Developers and AI users searching for MCP servers. - Domain rating: 77 - Link to your site: Nofollow - Cost: Free - Review: None ### Steps 1. Publish to the Official MCP Registry first. 2. Find your page at glama.ai/mcp/connectors/. 3. Click Claim ownership. Verify with GitHub, a `/.well-known/glama.json` file on your server, or a DNS TXT record. 4. If your server needs a login, add a test account so the health check passes. Unhealthy listings get filtered out. 5. Improve your tool descriptions. Glama grades each one, and clear “when to use this” notes raise the grade. ### Good to know - Keep the verification file or record in place. Ownership lapses 7 days after it’s gone. - Registry updates overwrite your name and description unless you set Glama as the source. ## Vercel Connect Add your API or MCP server to Vercel Connect so Vercel users can plug it into their apps. You get a page at vercel.com/connect. - Guide: https://indiehustles.com/marketplaces/vercel - Official docs: https://vercel.com/docs/connect/providers - You need: Public API - You build: Nothing new if you have an API or MCP server with OAuth or API keys. - Who's there: Developers on Vercel adding outside services to their apps. - Domain rating: 92 - Link to your site: Not confirmed - Cost: No fee listed - Review: Manual ### Steps 1. In the Vercel dashboard, open Connect, then Browse Connectors, then Submit a Service. 2. Add your service name, an SVG icon and a short description. 3. Add your MCP server or REST API as a target. 4. Pick how users connect: OAuth or API key. For OAuth, accept `https://connect.vercel.com/callback` as a redirect URL. 5. Run Preview & Test, then Submit for Review. ### Good to know - Don’t use Create Connector. That button is for adding a service to your own team, not for getting listed. - Vercel emails your contact address if it needs more details. ## ClawHub Publish a skill that teaches OpenClaw agents to use your API. It goes live in minutes with its own page on clawhub.ai. - Guide: https://indiehustles.com/marketplaces/clawhub - Official docs: https://docs.openclaw.ai/tools/clawhub - You need: Public API - You build: A SKILL.md file that explains your API to an agent. - Who's there: People running OpenClaw agents who need a skill for a task. - Domain rating: 83 - Link to your site: Not confirmed - Cost: Free - Review: Automatic scan ### Steps 1. Write a folder with a `SKILL.md`: what your product does, how to get an API key, and which endpoints to call. 2. Install the CLI: `npm i -g clawhub`. 3. Run `clawhub login`, then `clawhub whoami` to check. 4. Run `clawhub skill publish ./my-skill --slug my-skill --name "My Skill" --version 1.0.0`. 5. Check your page and scan status on clawhub.ai. ### Good to know - Put your signup link in the setup steps. The page has no separate website field. - Very new GitHub accounts may be blocked from publishing. ## Zapier Build a Zapier integration and get your own app page in the Zapier directory, where people look for tools to connect. - Guide: https://indiehustles.com/marketplaces/zapier - Official docs: https://docs.zapier.com/platform/publish/public-integration - You need: Public API - You build: A Zapier integration: sign-in plus a few triggers and actions. - Who's there: Non-technical teams looking for apps that connect to the tools they already use. - Domain rating: 91 - Link to your site: Not confirmed - Cost: Free - Review: Manual, reply within a week ### Steps 1. Build the integration in the Zapier Developer Platform, in the browser or with the CLI. 2. Run a live Zap for every trigger, action and search. 3. Prepare public API docs, a test account that never expires, your logo and a description starting with “ is a…”. 4. Open your integration, click Publish and fill in the form. 5. Fix anything the reviewer asks for. ### Good to know - Your API must be live and public, not invite-only. - At least one admin needs an email on your company domain. - You start in Beta for 90 days, already listed, then move to Public. ## Make Build a Make app for your API and get it verified so Make users can add it from the module picker. - Guide: https://indiehustles.com/marketplaces/make - Official docs: https://developers.make.com/custom-apps-documentation/app-review - You need: Public API - You build: A Make custom app: a connection and one module per action. - Who's there: Ops and marketing people building automations. - Domain rating: 90 - Link to your site: Not confirmed - Cost: No fee listed - Review: Manual ### Steps 1. In Make, open Custom Apps and create an app with a connection and one module per main action. 2. Put every module in one working scenario, and make one more scenario that shows an API error. 3. Run the scenarios right before you ask for review. Run logs expire. 4. Click Publish, make all modules visible, then open the Review tab. 5. Add your API docs link and the scenario links, and click Request review. 6. Fill in the form Make emails you and answer the QA feedback. ### Good to know - You can’t unpublish or delete parts once the app is public. Remove test modules first. - Your service needs its own domain, not a shared one like herokuapp.com. ## n8n Publish an n8n node for your API. Once verified, n8n users can install it from their dashboard. - Guide: https://indiehustles.com/marketplaces/n8n - Official docs: https://docs.n8n.io/integrations/creating-nodes/deploy/submit-community-nodes/ - You need: Public API - You build: An n8n node, published to npm. - Who's there: Technical teams and agencies building workflows and AI agents. - Domain rating: 90 - Link to your site: Not confirmed - Cost: Free - Review: Manual, up to 4 weeks ### Steps 1. Create the node with n8n’s node CLI. Add a credential for your API key and one operation per main action. 2. Name the package `n8n-nodes-yourproduct`, keep it free of runtime dependencies, and add a README. 3. Put it in a public GitHub repo and publish to npm from GitHub Actions with provenance. 4. Check it with `npx @n8n/scan-community-package n8n-nodes-yourproduct`. 5. Submit it at creators.n8n.io/nodes. ### Good to know - Since May 2026, n8n won’t verify nodes published from your own machine. - Nodes that compete with n8n’s paid features may be rejected. ## Notion Build a simple Notion connection, like sending new leads or reports into a Notion database, and list it in Notion’s marketplace. - Guide: https://indiehustles.com/marketplaces/notion - Official docs: https://developers.notion.com/guides/get-started/marketplace-listing - You need: Nothing extra - You build: A small Notion connection, like sending new records into a Notion database. - Who's there: Notion users who want data from their other tools in their workspace. - Domain rating: 90 - Link to your site: Dofollow - Cost: Free - Review: Manual, 5 to 10 business days ### Steps 1. Create a public connection in Notion’s developer settings. Set the install scope to “Any workspace”. 2. Open the Marketplace dashboard, go to Connections and start a new listing. 3. Add the name, description, category, logo and a few screenshots, and pick your connection. 4. Submit for review. Notion replies by email. ### Good to know - You can’t change the install scope later. - Your page goes live at notion.com/connections/, with a link to your site. ## Linear Build a Linear integration, like creating issues from your product, and get a page in Linear’s integrations directory. - Guide: https://indiehustles.com/marketplaces/linear - Official docs: https://linear.app/developers/integration-directory - You need: Nothing extra - You build: A Linear integration with OAuth. - Who's there: Product and engineering teams that work in Linear every day. - Domain rating: 85 - Link to your site: Dofollow - Cost: Free - Review: Manual ### Steps 1. Build an integration that uses Linear OAuth. 2. Publish a page on your site that explains how to connect it. 3. Make a color icon and a white icon at 320×320, plus 1 to 3 showcase images at 1600×1000 from Linear’s Figma template. 4. Fill in the submission form linked in Linear’s directory guide and send your assets to integrations@linear.app. ### Good to know - Linear lists integrations from real companies and usually turns down hobby scripts. - Listings link to both your homepage and your setup page. ## Chrome Web Store Publish a small extension that does one job from your product. You get a page on Google’s own domain that ranks well and gets cited by AI tools. - Guide: https://indiehustles.com/marketplaces/chrome-web-store - Official docs: https://developer.chrome.com/docs/webstore/register - You need: Browser extension - You build: A small extension that does one thing from your product. - Who's there: Chrome users searching the store for a tool that does one job. - Domain rating: 100 - Link to your site: Nofollow - Cost: About $5 once - Review: Manual, a few days to a few weeks ### Steps 1. Build a small extension that does one thing from your product. 2. Register in the Chrome Web Store Developer Dashboard and pay the one-time fee. 3. Zip the extension with `manifest.json` at the root and upload it. 4. Fill in the listing: description, icon, screenshots, privacy details and why you need each permission. 5. Submit for review. ### Good to know - The link to your site is nofollow. The value is the page itself, not the link. - Fewer permissions mean a faster review. - The same zip works on Edge, and on Firefox with small changes. ## Edge Add-ons Publish your Chrome extension on Microsoft Edge Add-ons. Same zip, free to register, and your developer name links to your site. - Guide: https://indiehustles.com/marketplaces/edge-add-ons - Official docs: https://learn.microsoft.com/en-us/microsoft-edge/extensions/publish/publish-extension - You need: Browser extension - You build: Nothing new if you have a Chrome extension. - Who's there: Edge users browsing the add-ons store. - Domain rating: 96 - Link to your site: Dofollow - Cost: Free - Review: Manual, up to 7 business days ### Steps 1. Register for the Edge program in Microsoft Partner Center with a personal Microsoft account. 2. Create a new extension and upload your zip. 3. Set the category and your website. That’s the link on your listing. 4. Fill in the privacy section and the store listing: description, logo and screenshots. 5. Publish, with a short note for the testers. ### Good to know - Work or school Microsoft accounts don’t work here. - Company accounts need extra checks that can take weeks. Individual accounts are faster. ## Firefox Add-ons Publish your extension on Mozilla’s add-on store. Your Chrome code works with two small manifest changes. - Guide: https://indiehustles.com/marketplaces/firefox-add-ons - Official docs: https://extensionworkshop.com/documentation/publish/submitting-an-add-on/ - You need: Browser extension - You build: Your Chrome extension, with two manifest changes. - Who's there: Firefox users browsing the add-ons store. - Domain rating: 96 - Link to your site: Nofollow - Cost: Free - Review: Automatic, sometimes manual ### Steps 1. Add a `browser_specific_settings.gecko` block to your manifest with an `id` and `data_collection_permissions`. 2. If you collect nothing, set `"required": ["none"]`. 3. Create a free Mozilla account and open the Developer Hub. 4. Upload your zip and fix any validation errors. 5. If your code is bundled or minified, upload the source too, with build steps. 6. Fill in the listing and submit. ### Good to know - The data collection field is required for all new extensions. - Reviewers must be able to rebuild your code exactly from the source you upload. ## npm Wrap your API in a small CLI and publish it to npm. It also shows up on jsDelivr, deps.dev, Libraries.io and other package sites. - Guide: https://indiehustles.com/marketplaces/npm - Official docs: https://docs.npmjs.com/creating-and-publishing-unscoped-public-packages - You need: Public API - You build: A small CLI that wraps your API. - Who's there: Developers who’d rather use a CLI than call an API. - Domain rating: 93 - Link to your site: Nofollow - Cost: Free - Review: None ### Steps 1. Build a CLI with a login command for the API key and one command per main action. 2. In `package.json`, fill in name, description, keywords, homepage and repository, and add a `bin` entry. 3. Run `npm login`. Your account needs 2FA. 4. Run `npm publish`. Add `--access public` only for scoped names like `@you/cli`. ### Good to know - Links from npm and the package sites are nofollow. You get pages and discovery, not link value. - Some users prefer a CLI to an API, so it helps your customers too. ## Postman Set up a public Postman team profile with your API collection. Developers can try your endpoints with their own key, and your profile links to your site. - Guide: https://indiehustles.com/marketplaces/postman - Official docs: https://learning.postman.com/docs/collaborating-in-postman/using-workspaces/public-workspaces - You need: OpenAPI file - You build: Nothing new if you have an OpenAPI file. - Who's there: Developers trying out an API before they build on it. - Domain rating: 91 - Link to your site: Dofollow - Cost: Free to start - Review: Approval on Team plans ### Steps 1. Create a team named after your product. 2. In team settings, add an About section and your website and social links. Turn on the public profile. 3. Create a public workspace and import your OpenAPI file. 4. Feature the workspace on your profile. 5. Add a Run in Postman button to your docs. ### Good to know - Postman scans public workspaces for secrets. Remove keys before publishing. - On Team plans, a Community Manager has to approve public workspaces. ## RapidAPI List your API on the largest public API marketplace. You don’t have to sell through it. Users can pass their own key from your app. - Guide: https://indiehustles.com/marketplaces/rapidapi - Official docs: https://docs.rapidapi.com/docs/add-api-getting-started - You need: Public API - You build: Nothing new if you have a public API. - Who's there: Developers browsing for an API to use in their app. - Domain rating: 83 - Link to your site: Not confirmed - Cost: Free - Review: None ### Steps 1. Sign up, open Studio and click Add API Project. 2. Import your OpenAPI file. RapidAPI builds the endpoint list and a live playground from it. 3. Under Hub Listing, set the base URL, logo, category, website and a short overview. 4. Add your Authorization header as a parameter so users can send their own key. 5. Accept the terms and switch the listing from Private to Public. ### Good to know - Add a free $0 plan so anyone can try it. ## Fern Agent Score Get your docs graded on how well AI agents can read them. Your score gets a public page that links to your docs. - Guide: https://indiehustles.com/marketplaces/fern-agent-score - Official docs: https://buildwithfern.com/agent-score - You need: Docs site - You build: An llms.txt file and Markdown copies of your docs pages. - Who's there: Developers and AI tools checking which docs agents can read well. - Domain rating: 77 - Link to your site: Dofollow - Cost: Free - Review: Instant ### Steps 1. Add an `llms.txt` that lists every docs page, and a `.md` version of each page. 2. Check your score locally: `npx afdocs check https://docs.yoursite.com`. 3. Open Fern Agent Score, paste your docs URL and click Score docs. 4. Fix the failing checks and score again. ### Good to know - The link goes to your docs, not your homepage. - Scored pages don’t all show on the leaderboard. ## EmDash Publish a plugin for EmDash, Cloudflare’s new CMS. You get a page in its plugin directory with a link to your site. - Guide: https://indiehustles.com/marketplaces/emdash - Official docs: https://docs.emdashcms.com/plugins/creating-plugins/publishing/ - You need: Public API - You build: A small EmDash plugin that connects a site to your product. - Who's there: Sites built on EmDash, Cloudflare’s new CMS, looking for plugins. - Domain rating: 76 - Link to your site: Dofollow - Cost: Free - Review: Approval before going public ### Steps 1. Start a plugin: `npx @emdash-cms/plugin-cli init my-plugin`. 2. Fill in `emdash-plugin.jsonc`: slug, publisher, license, author and security contact. Run `emdash-plugin validate`. 3. Log in with a Bluesky handle: `emdash-plugin login your.handle`. 4. Run `emdash-plugin bundle`, then `emdash-plugin publish`. 5. Bump the version for each new publish. ### Good to know - Use your domain as your Bluesky handle, so the listing shows @yourdomain.com. - Bundles must stay under 256 KB and 20 files. - The CLI is new and still changing. Pin an exact version.