Plugin Development

Build, sign, and publish plugins for the Dryade marketplace. SDK reference, manifest schema, and packaging guide.

Last updated: 16. März 2026

Building Plugins

Dryade plugins are Python packages that extend the platform with domain-specific AI workflows, tools, and agent configurations.

Plugin Structure

my-plugin/
├── dryade.json          # Plugin manifest
├── __init__.py          # Plugin entry point
├── routes.py            # FastAPI route definitions
├── agents/              # Agent configurations
│   └── my_agent.py
├── tools/               # Custom MCP tools
│   └── my_tool.py
└── ui/                  # Optional frontend bundle
    ├── src/
    └── dist/

Manifest Schema (dryade.json)

{
  "name": "my-plugin",
  "version": "1.0.0",
  "description": "Description of what the plugin does",
  "required_tier": "starter",
  "author": "Your Name",
  "category": "general",
  "entry_point": "__init__",
  "routes_module": "routes",
  "agents": ["agents/my_agent.py"],
  "tools": ["tools/my_tool.py"]
}

Plugin Tiers

  • Starter: Basic plugins suitable for individual users
  • Team: Multi-user plugins with collaboration features
  • Enterprise: Advanced plugins with compliance and audit capabilities

Signing and Publishing

Plugins must be cryptographically signed before they can be distributed:

  1. Package your plugin as a .dryadepkg file
  2. Sign with your Ed25519 author key
  3. Submit to the marketplace for review
  4. Marketplace counter-signs approved plugins
  5. Users install via the Plugin Manager

Plugin Security

  • All plugin code runs in a sandboxed environment
  • Plugins cannot access other plugins’ data
  • Route mounting is controlled by the core allowlist
  • UI bundles run in sandboxed iframes with signature verification