Skip to main content
Once your app is built and deployed on Waniwani, the next step is getting it listed in the assistant directories so people can find and install it. There are two directories today: the ChatGPT Plugin Store and Claude’s Connectors Directory. This section walks through what each one needs and gives you copy-pasteable templates for the parts reviewers scrutinize most.
A listing is never guaranteed. Both OpenAI and Anthropic review every app for quality and policy, and they may follow up with questions. These guides get you through review with the fewest surprises, but completing a form is not the same as being approved.

Who submits

For both directories, we recommend submitting from your own account: the listing belongs to your organization and the Developer name points to your company, not Waniwani. The difference is how much flexibility each directory allows: For ChatGPT, the choice is yours: submit yourself or have Waniwani handle the mechanics. For Claude, Anthropic requires the listing to come from the app owner’s own workspace, so the final submit always happens on your side. In both cases Waniwani prepares everything you paste in.

What both directories require

Prepare these before you start either form. They are common to both reviews:
1

A versioned, production MCP server URL

The form needs a stable HTTPS MCP URL. Find yours at app.waniwani.ai/mcp: your apps are listed there, and the dropdown next to each one copies its production URL. It follows a versioned pattern, for example https://v1.<your-app>.mcp.waniwani.run/mcp.
2

Correct tool annotations in the server

Every tool needs accurate hints (read-only, destructive, and for ChatGPT also open-world) plus a written justification. This is the single most common reason apps get rejected. See the Tool justification template. For managed Waniwani apps these are set in the server code for you before submission.
3

A live privacy policy and support channel

Both reviews require a publicly accessible privacy policy URL and a monitored support URL or email. Open each link in a private browser window to confirm it loads without a login. A missing or gated privacy policy is an immediate rejection.
4

A public documentation URL

Claude requires a live documentation URL at review time, and it helps your ChatGPT listing too. These submission guides themselves can serve as your documentation URL if you do not have a dedicated page yet.
5

Listing copy and a logo

A name, a short tagline, a description, and a square logo (a contrast-safe icon that reads on dark backgrounds). The exact limits differ per directory and are covered in each guide.

Two hard eligibility limits

Both assistants reject the same two categories of app, so confirm yours does neither inside the chat:
  • No moving money or crypto inside the conversation. Handing the user off to your own site to finish a purchase is fine. Showing a quote or an estimate is fine.
  • No AI generation of images, video, or audio. Tools that produce diagrams or charts are fine.

Pick your path

ChatGPT submission

The full checklist for the ChatGPT Plugin Store: app info, tool justification, test cases, screenshots, and compliance.

Claude submission

The Connectors Directory flow: Team/Enterprise prerequisite, the in-product portal, annotations, and listing details.

After you submit

Submitting is the start. How to drive traffic to your app and capture it: agent on your site, GEO, and PR.

Templates

Copy-pasteable tool justification and test-case templates for the parts reviewers check hardest.