What to prepare
- A public HTTPS remote server or separately packaged eligible plugin.
- Working supported authentication and accurate tool annotations.
- Documentation, privacy information, support contact, icon and reviewer access as required.
More preparation than a directory row
The current portal inspects the remote connection, tools, listing materials and compliance acknowledgments. Local MCP bundles are no longer accepted as standalone desktop-extension listings; the documented alternative is plugin packaging. Preparation must match the actual artifact and account authority.
Submission workflow
- Follow the current connector checklist.
- Test actual tools in Claude and prepare listing materials.
- Use an authorized account in the developer portal.
- Track the portal’s submission and review status.
Blockers to resolve before review
Use these as preparation checks. The destination makes its own acceptance decision.
- Missing tool titles or relevant safety annotations.
- Unsupported authentication, inaccessible tools or incomplete reviewer materials.
Primary sources
Checked 2026-10-29. Follow the destination’s current instructions if its requirements change.