[Guidance Needed]: How to Support Tool, Model, and Endpoint Services Simultaneously in Latest Dify Plugin Version

[lpdink]

Self Checks

• [x] I have read the Contributing Guide and Language Policy.
• [x] I have searched for existing issues search for existing issues, including closed ones.
• [x] I confirm that I am using English to submit this report, otherwise it will be closed.
• [x] Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Hi, I'm from the Alibaba Cloud ADBPG team and currently developing a Dify plugin.

I visited the Dify Plugin Marketplace but couldn't find any bundled plugin projects listed under the "Bundle" category. Additionally, I didn't locate any files with the .difybndl extension in that repository.

I noticed that, as of the time of submitting this issue, the latest version of dify-plugin-daemon enforces a restriction preventing a single plugin from simultaneously serving as a model, tool, and endpoint (see this code line).

In response to this limitation, I've refactored our original plugin into three separate plugins—one for each capability (tool, model, and endpoint)—and bundled them together. You can find our current implementation here: https://github.com/aliyun/alibabacloud-adbpg-dify-plugin.

What’s confusing is that I’m unable to provide tool, model, and endpoint capabilities within a single plugin, yet I also don’t understand how to properly publish or submit a bundle to the marketplace. Any guidance or suggestions would be appreciated!

2. Additional context or comments

No response

3. Can you help us with this feature?

• [x] I am interested in contributing to this feature.

[dosubot[bot]]

Currently, Dify enforces that each plugin can only serve as a tool, model, or endpoint—not all at once. The recommended approach is to split your functionality into separate plugins, one per capability, and submit each as its own folder and pull request. There is no official support or workflow for bundling multiple plugins (such as with a .difybndl file) for marketplace submission or public distribution—each plugin is treated as a standalone unit in the marketplace and in the official plugin repositories. The .difybndl format is only documented for offline installation, where you manually package all dependencies for local deployment, not for marketplace publishing or multi-plugin bundles (source, source).

If you want to present your three related plugins as a "bundle" to users, you could maintain a meta-repository or documentation page that links to each plugin individually until official bundle support is introduced. You might also want to share your use case and requirements in the ongoing discussions (like issue #30173) to help shape future improvements to plugin bundling and marketplace workflows.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}