Dify MCP Plugin Server

Official Dify MCP plugin server enabling AI agents to interact with Dify — the open-source LLM application development platform — querying Dify workflows and chatbots, triggering automated pipelines, accessing Dify knowledge bases, managing applications, and integrating Dify's no-code/low-code AI application infrastructure into agent-driven workflows.

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

Score Breakdown

⚙ Agent Friendliness

MCP Quality
72
Documentation
75
Error Messages
72
Auth Simplicity
80
Rate Limits
78

🔒 Security

TLS Enforcement
90
Auth Strength
80
Scope Granularity
75
Dep. Hygiene
78
Secret Handling
80

HTTPS. API key. LLM provider policies apply. Official Dify MCP. Self-hosted option available.

⚡ Reliability

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

Best When

An agent needs to invoke Dify-built AI workflows or applications as sub-components — Dify's visual workflow builder creates applications that can be triggered via this MCP.

Avoid When

You don't use Dify or prefer other LLM application frameworks like LangChain or LlamaIndex.

Use Cases

  • Triggering Dify workflow automations from orchestration agents
  • Querying Dify chatbot applications for specialized domain knowledge from agent systems
  • Accessing Dify knowledge bases for RAG retrieval from information agents
  • Building multi-agent systems where Dify apps serve as specialized sub-agents
  • Managing Dify application configurations from infrastructure agents
  • Integrating existing Dify pipelines into larger agent workflows from automation agents

Not For

  • Teams not using Dify (use LangChain, LlamaIndex, or other LLM framework MCPs)
  • Building new AI apps from scratch (use Dify directly rather than via MCP)
  • High-throughput production workloads without Dify enterprise plan

Interface

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

Authentication

Methods: api_key
OAuth: No Scopes: No

Dify API key required. Self-hosted Dify or Dify Cloud account needed. API key generated per Dify application.

Pricing

Model: freemium
Free tier: Yes
Requires CC: No

Dify is open source — self-hosted is completely free. Dify Cloud has a free sandbox. MCP plugin is free. Production Dify Cloud requires paid plan.

Agent Metadata

Pagination
cursor
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • Dify applications must be built and deployed before they can be invoked via MCP
  • Dify is a fast-moving project — API may change significantly between versions
  • Self-hosted Dify requires proper infrastructure setup (Docker, Postgres, Redis)
  • Official Dify plugin MCP but Dify ecosystem matures rapidly — verify current API
  • Dify Cloud rate limits in free tier are quite low — may hit limits quickly
  • LLM costs in Dify workflows billed to the Dify account's configured providers

Alternatives

Full Evaluation Report

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

$99

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

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