Claude Plugin Directory Portal: How Marketers Can Submit

Anthropic opened a directory submission portal for Claude plugins on 25 September 2026, and according to its announcement it is open to developers on paid Claude plans. If you have a repeatable marketing workflow, such as a content brief builder or a schema checker, you can package it as a plugin bundle in a GitHub repository, submit it at claude.ai/directory/manage, pass an automated scan, and publish it. This post covers what is confirmed as of 30 September 2026, and how I would approach it as a non-engineer.

Key Takeaways

• The portal launched on 25 September 2026 and, per Anthropic, accepts submissions from developers on paid Claude plans.
• You can submit a single MCP connector or a plugin bundle (MCP servers plus skills) hosted on GitHub.
• Every submission is validated and security-scanned; some versions are held for a human reviewer.
• After approval you control when to publish, and Anthropic says published plugins get install and discovery analytics.
• Marketers should start with a skill-only plugin, not a custom server, because the review surface is smaller.
• Treat any distribution promise as unproven until you see real install numbers.

What Anthropic actually announced

The Claude blog post announcing the portal is dated 25 September 2026. It says the portal is open to developers on paid Claude plans, that each submission gets automatic validation and safety scanning on upload, and that you receive status updates, scan results and recommended changes before approval. Once approved, you decide when the plugin goes live.

It also says published plugins show installation data by product surface and version, plus discovery metrics such as listing views and the search terms that led people to you. Unified discovery across Claude and Claude Code is described as rolling out "over the coming weeks", so as of today I would not assume it is fully live for everyone.

Several secondary outlets covered the launch, but I have relied on Anthropic's own pages for every claim below.

Why a marketer should care

Most marketing teams I have worked with have three or four prompts that people copy from a Notion page. They drift, someone edits them, and quality varies by person. A plugin turns that into a versioned, installable unit.

At Masai School, where I helped grow the Instagram account from 26K to 117K and LinkedIn from 50K to 200K (see the Masai School work), the biggest operational win was never a clever prompt. It was a shared, consistent process for briefs and reviews. A plugin is the same idea, made portable.

What a marketing plugin could contain

• A skill that turns a keyword and SERP notes into a brief in your house format.
• A skill that checks a draft against your style guide and flags unsupported claims.
• An MCP connector to a tool you own, such as an internal keyword database.

The first two need no server. That matters, as the next section shows.

Two submission paths

Anthropic's docs state that if your plugin references a remote MCP server you run, you submit that server as a connector too. A skill-only bundle avoids that second submission.

The submission steps, per the docs

The submission docs list these steps as of 30 September 2026:

1. Put the plugin in a GitHub repository and connect your GitHub account on claude.ai. Your account must be able to push to the repository.
2. Open claude.ai/directory/manage, choose Submit new, then Plugin bundle.
3. Enter the repository (and optionally the plugin folder path and tracked branch or tag), then run Validate.
4. Check the listing details, which are read from plugin.json and the README.
5. Answer the data handling questions: personal data, other services, retention, and whether it is meant for people under 18.
6. Complete the compliance step and acknowledgements, then choose how new versions arrive and select Submit for review.

The docs recommend running claude plugin validate ./<plugin-folder> locally first, and note the portal's Validate step runs more checks than the command.

Limits worth knowing

An organization can create up to 10 submissions in 24 hours, and drafts and withdrawn submissions count. Each plugin folder is its own submission. The repository can be private during validation but must be public before the listing goes live.

What the scan and review can do to you

After you submit, the directory scans the newest commit on your tracked branch. Per the docs, a finished scan leaves a version in one of three states: it passes every check, it is held for an Anthropic reviewer, or it fails with the rules listed. A failed security scan can name a category, such as sending data to an undisclosed destination.

That last example is the one marketers should take seriously. If your skill tells Claude to post data to a third-party analytics endpoint and your data handling answers do not say so, expect a problem.

Publishing is a separate step

A passing version is not live until you select Publish. By default that records a request for an Anthropic reviewer, who publishes it. The docs describe settings where later versions go live automatically, but Anthropic applies the setting, so you cannot count on auto-publish for your first release.

A cautious plan for the first two weeks

Here is how I would sequence it, based on the documented flow rather than any result I have observed.

1. Pick one workflow you already run at least weekly.
2. Write it as a skill with plain instructions and one example input and output.
3. Add a README that says what data the skill touches (ideally none).
4. Validate locally, fix findings, then validate in the portal.
5. Submit, and read the Versions tab for scan results.
6. When published, watch the Usage tab the docs mention for installs, versions, runs and error rates.

Do not build a server on day one. Every extra moving part is a new thing to explain to a reviewer.

Distribution: what is and is not known

Anthropic promises discovery metrics, but nothing I found tells us how listings are ranked or how many people browse the directory. So a plugin is a distribution bet, not a channel with known volume. If you sell a product, a plugin can put you inside a workflow. If you sell services, it is closer to a credibility asset.

Also plan for the ordinary SEO layer. A plugin page will not carry your brand story, so keep your own site page for the plugin, with documentation and examples, and link it from the README.

Sharing without a public listing

The docs also point to options to share a plugin with teammates or roll it out across an organization without a public listing. For agencies, this is often the better first step: prove the plugin internally before exposing it to review.

Risks to weigh

• Review time and outcomes are not published as a guarantee, so do not promise a client a launch date.
• Your plugin's behaviour depends on model behaviour that changes; test after model updates.
• Anything touching client data needs a real data handling answer, and possibly a legal review.
• Sept 2026 details may change; re-read the docs before submitting.

FAQ

Who can submit a plugin to the Claude directory?

According to Anthropic's announcement, developers on paid Claude plans. The docs also say your plan and role must be able to submit, and link to a page on who qualifies. Check that page for your organization.

Do I need to know how to code?

For a skill-only plugin you mostly write instructions and metadata files in a GitHub repository. You do need to be comfortable with GitHub, and a developer can help with plugin.json and validation.

What is the difference between a connector and a plugin bundle?

A connector is one remote MCP server listed on its own. A plugin bundle combines MCP servers and skills from a GitHub repository. If your bundle references a server you run, the docs say to submit the server as a connector as well.

Can my repository be private?

It can be private while you validate and submit, but it must be public before the listing goes live. Private repos require you to agree that source is uploaded for scanning and reviewer access.

How many submissions can I make?

The docs say an organization can create up to 10 submissions in any 24-hour period, including drafts and withdrawn ones.

Will my plugin go live automatically after it passes?

Not by default. You select Publish and, by default, an Anthropic reviewer publishes it. Later versions may go live automatically depending on a setting Anthropic applies.

What analytics do I get?

Anthropic says published plugins show installs by product surface and version and discovery metrics like listing views and search terms. The docs also mention a Usage tab with runs and error rates.

Is a plugin a good marketing channel?

Unproven. Directory traffic figures have not been published, so treat it as an experiment and measure installs against the effort spent.

Where can I see my plugin's status?

In the developer portal under Submissions, where the Versions tab lists each scanned commit and its results.

Work with me

I am Younus Fardeen, an organic growth, SEO and AEO strategist with 4+ years of marketing experience across edtech and startups. If you want help turning a marketing workflow into something repeatable, or planning how AI tools fit your content operation, see my work and reach me through the contact form at younusfardeen.in.