Dify.ai Workflow
Dify MCP Server provides a bridge between AI assistants and Dify.ai's workflow applications through the Model Context Protocol. Built by teddylee777, it transforms Dify workflows into MCP tools that can be dynamically discovered and called by AI assistants, handling parameter validation and response formatting. The server loads configuration from a YAML file containing Dify API keys and base URLs, then exposes each configured Dify application as a separate tool with appropriate input schemas derived from the Dify user input forms. This implementation is particularly useful for organizations that have built complex workflows in Dify and want to make them accessible to AI assistants without rebuilding the logic.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.
Scan details: Circle-IR · 2026-09-19 · Appeal
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- file-system
- Source
- PulseMCP
- Repository
- github.com/teddylee777/dify-mcp-server
- Author type
- human
- Last scanned
- 2026-09-19
- Updated
- 2026-09-19
Use via MCP
Resolve Dify.ai Workflow from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp--scope user for --scope project to commit it to .mcp.json.