How to list your website's connector in the Claude directory

Anyone with a Claude account can add your site's connector by pasting its address. That's perfect for you and your team. But if you want other people to find and install it in a couple of clicks, your connector needs a listing in Claude's directory, and that means a submission and a review.

This guide covers what the submission asks for, how to fill in each part well, and how AI Plugin Generator prepares the material so you can mostly copy and paste. Anthropic updates its forms from time to time, so field names may differ slightly, but the substance stays the same.

Private connector or public listing?

Before submitting, decide who the connector is for.

• For you and your team: you don't need a listing. Add it under Claude's Settings → Connectors → Add custom connector, paste your plugin's address, and sign in with a one-time code. See how to manage your WordPress site from Claude.
• For customers or the public: a directory listing makes it discoverable and gives users a familiar, trusted install flow.

A public connector should usually do less than a private one. Customers need products, stock and their own orders, not refunds or settings. A common setup is two plugins for the same site: a narrow public one for the directory and a fuller private one for you.

What the submission asks for

Claude's directory submission is a multi-step form. In our experience it covers:

1. Basic details: connector name, the server address, and a short tagline.
2. Description: what it does and who it's for.
3. Use cases: concrete examples of what a user can achieve.
4. Categories: where it belongs in the directory.
5. Authentication: how users sign in.
6. Tools: what the connector exposes, and confirmation that tools are labelled correctly.
7. Test access: how reviewers can try it.
8. Links: privacy policy, terms and support contact.
9. Branding: icon and publisher name.
10. Review and launch.

Your plugin's Submit tab has a Claude section that mirrors these steps. Every field is pre-filled from your site and your chosen tools, sized to the form's limits, with a copy button beside each.

Writing each part well

Name and tagline

Use your brand: "Riverside Garden Centre", not "Garden Store Connector". The tagline should say what users get: "Check plant availability and opening hours in Claude."

Description

Reviewers and users want the same things answered:

• What can it do? List the main capabilities in plain language.
• Who is it for? Your customers, your staff, or both.
• What are its limits? "Read-only: it can look up products and orders but can't change anything."
• What does it access? "Only data on riverside.example."

Honesty about limits helps more than it hurts. Reviewers check that the description matches the tools.

Use cases

Use cases are the heart of the listing. Write them as outcomes, each with an example prompt:

• Check availability before visiting. "Is the olive tree in 5L pots in stock at Riverside?"
• Track an order. "Where is my order 4821?"
• Compare options. "What's the difference between your two compost types?"

We generate use cases from the tools in your plugin, so they always match what the connector can really do. Edit them to use your own products and voice.

Categories

Choose categories that match the primary use. For store connectors, "Commerce & Shopping" fits customer-facing listings; owner-facing tools may fit "Productivity" or "Data & Analytics" better. Don't pick categories just to appear in more places; mismatches are a common review comment.

Authentication

Your plugin uses OAuth, the standard Claude expects. When a user connects, Claude opens your plugin's sign-in page. For a private plugin, you sign in with a one-time connection code from your dashboard. The form asks how sign-in works; the Submit tab gives you a short, accurate description to paste.

Tools and safety labels

Every tool must declare whether it only reads, changes data, or is destructive, and whether it reaches outside your system. Plugins built with AI Plugin Generator label these correctly by default: read tools are read-only, write tools are marked as changing data, and refunds, deletions and status changes are marked destructive. If your listing is public, consider including only read tools.

Test access for reviewers

Reviewers need to sign in and try your connector, without your personal account and without the risk of changing your live store.

1. In the Submit tab, create a reviewer code. It can be reused for 30 days, which covers the review period.
2. Paste it into the test-access field with one sentence of instructions: "On the sign-in page, enter this code."
3. Add a few read-only test prompts with expected results, such as "List the five newest products" with "returns five products with names and prices".

Never ask reviewers to perform actions that change live data. If your public plugin only has read tools, that's guaranteed.

Links

• Privacy policy: it must cover the connector's data use. If your site lacks a suitable page, the Submit tab can create one on your WordPress site for you to review.
• Terms: your store's terms page is usually fine.
• Support: a real email address you check.

Branding

A square icon with a simple mark. Your plugin's icon is generated from your site's own icon, and you can upload your own.

Before you press submit

Run through this list:

• Connector name is your brand, not generic.
• Description matches the tools exactly.
• Use cases are concrete, with example prompts.
• Categories fit the main use.
• Tools are labelled correctly; the public version is as narrow as possible.
• Reviewer code is fresh and has instructions.
• Test prompts are read-only and repeatable.
• Privacy policy covers the connector.
• Your subscription is active, so the connector doesn't pause mid-review.

After launch

Once listed, your connector appears in Claude's directory under your name. Keep an eye on your plugin's Activity tab to see which tools people use most; it's the best guide to what to improve. If you add tools later, update the listing so the description still matches.

Publishing in ChatGPT's app directory uses much of the same material: domain verification, descriptions, reviewer access and test cases. Many sites list in both.