---
title: "AI Plugin Directories: List Your SaaS in Claude, ChatGPT, Cursor and Grok"
description: "How to list a SaaS in every AI plugin directory: Claude plugins, ChatGPT and Codex plugins, the Cursor Marketplace, the xAI plugin marketplace for Grok Build and the MCP Registry. What to ship, where to submit, what gets rejected."
source: https://viraloop.io/ai-plugin-directories
---
Distribution inside the assistants

# List your SaaS in every AI plugin directory

Your buyers now ask Claude, ChatGPT, Cursor and Grok what to use, then expect to use it without leaving the chat. We listed Viraloop and Faceless in each directory and wrote down exactly what each one wants, what it rejects, and the order to do them in.

[Start with Claude plugins](/ai-plugin-directories/claude-plugins)[Playbook chapter](/playbook/ai-plugin-distribution)

## Five directories, one guide each

Each guide covers the files, the submission form, the review rules that reject people, and what we learned shipping our own listing.

[

### Claude plugin directory

Claude Code + Cowork

One public GitHub repo with a plugin manifest, a skill and an MCP config. Submit from the Console; updates mirror from the repo automatically.

How to list

](/ai-plugin-directories/claude-plugins)[

### ChatGPT plugin directory

ChatGPT + Codex

A manifest bundling a skill, an MCP server and directory metadata, submitted through the OpenAI platform with a verified identity and a domain challenge.

How to list

](/ai-plugin-directories/chatgpt-plugins)[

### Cursor Marketplace

Cursor IDE

A public repo with a Cursor plugin manifest and a remote MCP server. Submit the repo URL; every version is reviewed by a person before it is listed.

How to list

](/ai-plugin-directories/cursor-marketplace)[

### xAI plugin marketplace (Grok Build)

Grok Build + Grok app

One catalog entry in a public GitHub repo, pinned to a commit SHA, submitted as a pull request. Code-owner review checks source legitimacy and security.

How to list

](/ai-plugin-directories/grok-plugins)[

### The official MCP Registry

Every MCP client

Publish the npm package, add an mcpName, generate server.json and publish with mcp-publisher. Clients and community directories read the registry from there.

How to list

](/ai-plugin-directories/mcp-registry)

## What each directory wants

Directory

You ship

Submit at

Review

Auth

[Claude plugins](/ai-plugin-directories/claude-plugins)Anthropic

Public repo: .claude-plugin/plugin.json, .mcp.json, skills/

platform.claude.com/plugins/submit

Automated screening; Anthropic Verified badge is a separate, optional review

Env var API key or a remote MCP with OAuth

[ChatGPT and Codex plugins](/ai-plugin-directories/chatgpt-plugins)OpenAI

.codex-plugin/plugin.json, .mcp.json, skills/, a hosted MCP with OAuth

platform.openai.com/plugins

Human review of the MCP server, tool metadata and eight test cases

OAuth 2.1 on the hosted MCP, plus a demo login for reviewers

[Cursor Marketplace](/ai-plugin-directories/cursor-marketplace)Cursor

Public repo: .cursor-plugin/plugin.json, .cursor-plugin/marketplace.json, mcp.json, skills/

cursor.com/marketplace/publish

Manual review of every version; plugins must be open source

Remote MCP with OAuth dynamic client registration, no key to paste

[Grok Build plugins](/ai-plugin-directories/grok-plugins)xAI

Public repo: .grok-plugin/plugin.json, .mcp.json, skills/, plus a PR to xai-org/plugin-marketplace

Pull request to github.com/xai-org/plugin-marketplace

CI validator plus xAI code-owner review of source, security and duplication

Remote MCP with OAuth; env vars for local servers

[MCP Registry](/ai-plugin-directories/mcp-registry)Model Context Protocol

An npm package with mcpName, plus server.json

mcp-publisher publish (registry.modelcontextprotocol.io)

None; automated validation that the package matches the metadata

GitHub device login, or DNS auth for a custom-domain namespace

## Before the first submission

01

### Get referenced before you get installed

An assistant names two or three products, not ten links. Publish an llms.txt, answer questions in the first two sentences of every page and get into the roundups models quote. The Answer Engine Optimization chapter of the playbook is that work; the listings below are what happens after a model already knows you exist.

[Read the AEO chapter →](/playbook/answer-engine-optimization)

02

### Build one source of truth

Every directory wants the same three things in a slightly different folder layout: a manifest, a skill and an MCP server. Generate all of them from your API definition. Our generator writes the OpenAPI spec, llms.txt, the CLI tool table, the Claude plugin, the ChatGPT plugin and the Cursor plugin in one run, and a drift check in CI fails when any of them is stale.

[See how ours is wired →](/developers)

03

### Host one MCP server with OAuth

A remote server over streamable HTTP with OAuth 2.1, dynamic client registration and PKCE is what ChatGPT requires, what Cursor and Grok Build sign users in with, and what the MCP Registry lists as a remote. Build it once and every directory points at the same URL. Keep an API key header as the fallback for scripts.

[Our MCP setup guide →](/developers/docs/mcp)

Then publish in this order: the MCP Registry (no review), Claude plugins (automated review), Cursor (manual review), xAI (a pull request with a pinned SHA), and ChatGPT (the strictest). Each later one reuses the previous one's files.

## A listing gets you installed.  
Posting daily gets you named.

Models quote the brands that keep publishing. Viraloop generates and posts your short-form content to TikTok, Reels and Shorts every day, so the answer an assistant gives about you is this quarter's.

[Start posting daily](/register)[Viraloop for agents](/agents)