Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- As of September 29, 2026 the portal is claude.ai/directory/manage. Pro/Max can submit; Team/Enterprise need Owner or documented Directory permissions. Free is not among listed eligible plans.
- Plugin bundles and remote MCP connectors are separate types. Bundles need public GitHub repositories; a referenced remote MCP server still needs its own connector submission.
- The old Console form is unsupported. Withdraw old submissions when that button exists, then resubmit; otherwise request migration from [email protected].
- Each plugin version receives automated validation and security scanning; new listings also need human review. No fixed review time is promised, and passing one stage does not establish public visibility.
- This guide has not submitted a real plugin, logged into paid accounts, or verified an organization's permissions or results. PRODUCT_FIT=NONE.
Who can submit, and which type should you choose?
Anthropic announced the portal September 25, 2026. As of September 29, paid Claude plans can submit: Pro/Max directly, Team/Enterprise through an Owner, and Enterprise Owners can grant Directory permissions through custom roles. Installing or using a plugin is different from submission eligibility; check organization settings and the portal.
For commands, skills, or agents, choose Plugin bundle and prepare a public GitHub repository. For a remote MCP server, choose MCP connector, including a separate connector submission when a bundle references it. Older MCPB desktop extensions are deprecated and cannot be submitted as standalone local servers. The directory serves claude.ai web, desktop, mobile, and Cowork; approved plugins can also work in Claude Code, without granting other eligibility such as Claude Code Projects.
Prepare the repository, contents, and permissions
Verify paid-account access and the required organization role, then choose bundle or connector. A bundle needs a public GitHub repository, reviewable documentation and version, and .claude-plugin/plugin.json following the official structure. Describe commands, agents, skills, and external services. A remote MCP server needs connection, authentication, and permission documentation, not merely a hidden reference in plugin configuration.
Check for leaked keys, customer data, or private internal addresses. Verify tools and expected behavior in a test account. This is self-review, not Anthropic validation or security approval. Organization approvals, directory policies, and third-party terms remain separate requirements.
Submit through the new portal and distinguish review stages
On web, open claude.ai/directory/manage, select Submit new, and follow the Plugin bundle or MCP connector checklist. Retain repository URL, version, time, and displayed status. Missing access calls for checking paid plan, Owner/Directory permissions, and the current organization, not assuming review failure. This guide has not operated accounts or verified simultaneous global rollout.
Inspect automatic validation and security-scan results, fix specific repository/configuration errors, and use the portal's version flow. New listings also need human review, with no fixed review time. Submission receipts or automated-check success do not mean published. Separately verify the correct public listing and the target account's installation and necessary authorization.
Move old Console submissions to the new directory
The old platform.claude.com/plugins/submissions form is unsupported. If an old submission has Withdraw, withdraw it and resubmit through the new developer portal. Without the button, contact [email protected] for migration. An old record does not establish automatic inclusion in the new directory.
Save the old repository, version, review notices, and correspondence first. Resubmission still undergoes current checks and review, without a promised queue position or launch date. If portal states conflict, stop duplicate submissions and ask the directory team to confirm the same project's status.
Verification, stopping conditions, and fallback
Verify three stages independently: submission received; version checks and human review passed; correct name, publisher, and version visible publicly and installable with minimal permissions. Record actual results. Some developers report approved listings temporarily absent; that warrants verification, not a proven universal platform incident.
For failed scans, excessive permissions, repository/version mismatches, or prolonged absence despite approval, stop promotion and preserve evidence. Fix the specific error or contact the team. Before submission, retain the local version; after submission/publication, preserve the last usable repository version and follow review for revisions. No instant lossless rollback is promised. IP changes cannot grant business permissions or review success. PRODUCT_FIT=NONE.
What still needs account-specific verification
The sources promise no fixed review days, per-organization or per-region approval rates, or final visibility times. This guide has not verified submission fees, revenue sharing, or any particular approval. Paid-plan eligibility does not establish those unknowns.
For internal team use rather than public listing, check organization sharing and installation policies instead of assuming listing is the only distribution path. Future changes should be checked against Publish to the directory and actual portal notices before updating this guide.
Sources
Frequently Asked Questions
Can a free account submit?
The documentation requires a paid Claude plan: Pro/Max directly, Team/Enterprise with Owner or permitted Directory access. Plugin use does not establish submission eligibility.
Does a referenced MCP server need its own submission?
Yes. Plugin bundles and connectors are separate types; remote MCP servers need connector submission even when a bundle references them.
Do old Console submissions migrate automatically?
Do not assume so. Withdraw and resubmit when the button exists; otherwise request migration from [email protected].
How soon after approval will a listing appear?
No fixed review time is promised. Submission, automated checks, human review, and visibility are separate stages. Check the portal and listing rather than treating a receipt as publication.
Is immediate rollback guaranteed?
No instant lossless rollback is promised. Preserve usable versions and review records, stop promoting a problematic version, and revise through the portal or contact the team.