Community plugins and adapters
Static registry for third-party Email SDK plugins and provider adapters.
Community plugins and adapters are third-party npm packages. The registry is static and maintained in this repository by pull request.
Use this page for discovery. Use the publishing guides when you want to create a package.
No community plugins are listed yet.
Community packages are listed by pull request after their registry entry passes the static checks.
What belongs here?
| Package kind | What it adds | Example setup |
|---|---|---|
| Adapter | A provider implementation for one email service. | plugins: [acmeMailPlugin(...)] |
| Plugin | Reusable send behavior, policy, hooks, or helpers. | plugins: [requireMetadataPlugin()] |
| Hybrid | A package that includes both provider and behavior. | plugins: [providerWithDefaults()] |
Adapters are listed here even though users mount the package through plugins. The adapter is the provider implementation; the plugin is the reusable registration wrapper.
Labels
| Label | Meaning |
|---|---|
| Community | Listed by pull request. The package is not endorsed. |
| Verified | Passed the registry checks for a specific package version. |
| Official | Maintained by OpenCore or in this repository. |
Verified does not mean risk-free. It means the package passed the static checks documented in the registry schema.
Add a package
Publish a package to npm, then open a pull request that adds an entry to apps/fumadocs/content/community/plugins.json.
If you want feedback before writing the entry, open the Community package listing issue template with the package and source links.
Start with:
- Publish a community adapter for provider packages.
- Publish a community plugin for behavior packages.