Dify Plugin SDK

July 17, 2026 ยท View on GitHub

A Python SDK for building plugins for Dify.

Here is a short introduction to Dify Plugin: https://docs.dify.ai/plugins/introduction

Development

This repository uses just as its command runner. Install it with your preferred package manager, or with uv:

uv tool install rust-just

Common development commands:

just dev       # Sync default dev dependencies
just fmt       # Apply formatting fixes
just lint      # Format and apply lint fixes
just check     # Check lockfile, formatting, and linting
just test      # Run SDK tests
just build     # Build source and wheel distributions
just docs      # Generate schema documentation

Production Plugin Examples

See langgenius/dify-official-plugins for production plugin implementations that are published and used by Dify.

LLM Polling Support

SDK 0.9.0 adds support for polling-based LLM invocation. A model can now declare the polling feature and implement polling methods, allowing plugins to submit long-running provider jobs and return later checks through a short request/response flow.

Polling results use three states:

  • running returns plugin-owned state for the next check.
  • succeeded returns the final LLM result.
  • failed returns a terminal error.

Version Management

This SDK follows Semantic Versioning (a.b.c):

  • a: Major version - Indicates significant architectural changes or incompatible API modifications
  • b: Minor version - Indicates new feature additions while maintaining backward compatibility
  • c: Patch version - Indicates backward-compatible bug fixes

For SDK Users

When depending on this SDK, it's recommended to specify version constraints that:

  • Allow patch and minor updates for bug fixes and new features
  • Prevent major version updates to avoid breaking changes

Example in your project's dependency management:

dify_plugin >= 0.8

Manifest Version Reference

For the manifest specification, we've introduced two versioning fields:

  • meta.version - The version of the manifest specification, designed for backward compatibility. When installing an older plugin to a newer Dify, it's difficult to ensure breaking changes never occur, but at least Dify can detect them through this field. Once an unsupported version is detected, Dify will only use the supported parts of the plugin.
  • meta.minimum_dify_version - The minimum version of Dify, designed for forward compatibility. When installing a newer plugin to an older Dify, many new features may not be available, but showing the minimum Dify version helps users understand how to upgrade.

Meta.Version Reference

Manifest VersionDescription
0.0.2As ToolProviderType now supports mcp, an elder implementation is going to broken when user selected a mcp tool in Dify, so we bump it to 0.0.2 to ensure Dify knows that mcp is disabled if meta.version under 0.0.2.
0.0.1Initial release

Meta.MinimumDifyVersion Reference

Minimum Dify VersionSDK VersionDescription
1.2.00.2.0Support fetching application info
1.4.00.0.1-beta.49Support LLM multimodal output
1.4.00.3.1Support OAuth functionality for plugins
1.5.10.4.0Support dynamic-select parameter type
1.5.10.4.0Support LLM structured output
1.6.00.4.1Support dark-icon field in manifest
1.7.00.4.2Support OAuth functionality for plugins
1.8.10.4.4Support filename in MultiModalPromptMessageContent
1.9.00.5.0Support Datasource functionality for plugins
1.10.00.6.0Support Trigger functionality for plugins
1.11.00.7.0Support Multimodal Reranking / Embeddings
1.14.00.8.1Dependency and project structure cleanup
1.14.20.9.0Support polling-based LLM plugin invocations