Dify MCP Server

Dify MCP server enabling AI agents to interact with Dify LLM application platform — executing Dify workflows and chatbot conversations, querying knowledge bases, triggering AI pipelines, and integrating Dify's no-code AI application capabilities into agent-driven AI workflow orchestration and LLM application execution.

Evaluated Mar 06, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ AI & Machine Learning dify llm-platform no-code-ai mcp-server workflows chatbots rag
⚙ Agent Friendliness
71
/ 100
Can an agent use this?
🔒 Security
72
/ 100
Is it safe for agents?
⚡ Reliability
66
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
68
Documentation
72
Error Messages
68
Auth Simplicity
82
Rate Limits
65

🔒 Security

TLS Enforcement
82
Auth Strength
70
Scope Granularity
65
Dep. Hygiene
68
Secret Handling
72

TLS depends on deployment. API key per Dify app. Community MCP. Protect API keys. Configure HTTPS for self-hosted. LLM prompt processing — review for prompt injection.

⚡ Reliability

Uptime/SLA
68
Version Stability
65
Breaking Changes
65
Error Recovery
65
AF Security Reliability

Best When

An agent needs to invoke Dify workflows or knowledge bases — for orchestrating Dify-built AI applications as tools within larger agent workflows.

Avoid When

You don't have Dify deployed, or if you're building AI applications from scratch — Dify MCP is for using existing Dify apps, not building them.

Use Cases

  • Executing Dify AI workflows from orchestration agents
  • Running Dify chatbot conversations from interaction agents
  • Querying Dify knowledge bases from RAG agents
  • Triggering custom AI pipelines from automation agents
  • Chaining Dify apps in multi-step agent workflows
  • Testing Dify application outputs from QA agents

Not For

  • Teams using LangChain, LlamaIndex, or other AI frameworks directly
  • Teams needing Dify admin operations (app creation, training)
  • Teams without a running Dify instance

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
Yes
Webhooks
No

Authentication

Methods: api_key
OAuth: No Scopes: No

Dify app API key from Dify app settings. Each Dify application has its own API key. Self-hosted Dify or Dify Cloud. Key grants access to specific Dify app capabilities.

Pricing

Model: freemium
Free tier: Yes
Requires CC: No

Dify Community Edition is open source (Apache 2.0) and free to self-host. Dify Cloud offers managed hosting with free and paid tiers. Community MCP server is open source and free.

Agent Metadata

Pagination
none
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • Each Dify app has a separate API key — agents must manage multiple keys for multiple apps
  • Dify workflow execution is asynchronous — agents must poll for completion
  • LLM costs pass through from underlying providers — not absorbed by Dify
  • Streaming vs blocking API modes have different response handling
  • Dify self-hosted version may differ from Dify Cloud in features
  • Community MCP server — Dify API evolves; may break between versions

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Dify MCP Server.

$99

Scores are editorial opinions as of 2026-03-06.

5178
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered