Skip to content

Conversation

@flyryan
Copy link

@flyryan flyryan commented Nov 24, 2025

Plugin Information

Submission Type

  • New Plugin
  • Update to Existing Plugin

Description

First implementation of the Agent-to-Agent (A2A) protocol for Dify, enabling cross-platform agent collaboration and task delegation. This plugin provides 5 tools for both synchronous and asynchronous communication with external A2A-compliant agents.

Why this plugin is needed:

  • Implements open A2A Protocol v0.3.0 standard for agent-to-agent collaboration
  • Complements Dify's existing MCP support (which focuses on tool/data access) by enabling agent delegation
  • Allows Dify agents to delegate specialized tasks to domain-expert agents on any A2A-compatible platform
  • Supports both sync (message/send) and async (message/stream + tasks/get) communication patterns
  • Provides universal agent-to-agent connectivity using JSON-RPC 2.0 standard

Key features:

  • 5 comprehensive tools: list agents, get capabilities, call agent (sync), submit task (async), get task status
  • Multiple authentication methods: Bearer, API Key, Basic Auth, None
  • Secure credential storage via Dify's secret-input
  • Full bilingual support (English + Chinese)
  • Comprehensive error handling and 60s+ timeout support

Compliance Checklist

Documentation Standards

  • My README contains setup instructions
  • My README contains usage details
  • My README contains required APIs and credentials information
  • My README contains connection requirements
  • My README contains a link to the source repository

Privacy Requirements

  • Does your plugin collect personal data? YES
    • Data collected: Agent API credentials (API keys, tokens), agent base URLs, agent names, agent descriptions
    • Purpose: To authenticate with and route requests to remote A2A-compatible agents
    • Storage: Securely stored in Dify's encrypted credential system
    • Third-party sharing: User instructions/messages sent to explicitly configured external agent endpoints only
  • I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

Additional Information

@flyryan
Copy link
Author

flyryan commented Dec 14, 2025

Hi everyone. Any update on this? We've been using this plugin in production successfully for weeks. It would be great to be able to use it without disabling plugin signing. Let me know if there is anything I can do to help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant