Dify
Dify is the most popular open-source LLM application platform, with 131k+ GitHub stars. Since v1.6.0, it supports two-way MCP — your agents call tools from external MCP servers, and your Dify workflows can be published as MCP endpoints that Claude Desktop, Cursor, and other clients consume natively.
Two-Way MCP: Consume and Expose
Most platforms only consume MCP tools. Dify goes further — it acts as both client and server in the MCP ecosystem. Your marketing team builds a lead-scoring workflow in Dify's visual builder, and that workflow becomes an MCP endpoint any IDE or terminal agent can call. Meanwhile, the same workflow consumes tools from Vinkius Cloud for data enrichment.
This bidirectional approach makes Dify a central hub for AI-powered automation. Build once in the drag-and-drop editor, expose everywhere via MCP.
Key capabilities:
- Two-way MCP — call external MCP tools + publish Dify apps as MCP servers
- Visual workflow builder — drag-and-drop with conditional logic, loops, and human-in-the-loop steps
- RAG engine — ingest PDFs, web pages, and documents with hybrid retrieval and reranking
- Prompt IDE — visual prompt orchestration and A/B testing
- 50+ built-in tools — web search, DALL·E, scraping, and connectors
- Plugin marketplace — extensible architecture with community plugins
- LLMOps — log monitoring, cost tracking, and production data analysis
- API-first — every feature accessible via RESTful APIs
Getting Set Up
1. Create a Token
Go to Vinkius Cloud → your server → Connection Tokens → Create. Copy the URL.
2. Add MCP Server in Dify
Open your agent or workflow → Tools → Add Tool → select MCP Server → paste:
https://edge.vinkius.com/{TOKEN}/mcpDify auto-discovers available tools and makes them available in the workflow editor and agent conversations.
3. (Optional) Publish as MCP Endpoint
To expose your Dify workflow as an MCP server, go to Publish → MCP Endpoint. Other clients can now consume your workflow as a standard MCP tool.
FAQ
What does "two-way MCP" mean in Dify? Dify can call tools from external MCP servers (like Vinkius Cloud) and also publish its own workflows as MCP endpoints. Claude Desktop, Cursor, and other clients can discover and call your Dify workflows through standard MCP.
Can I use MCP inside Dify visual workflows? Yes. MCP tools appear as nodes in the drag-and-drop workflow builder. Wire them alongside conditionals, loops, and other Dify nodes.
Do I need Docker to run Dify? Docker is the recommended self-hosted option, but Dify Cloud (dify.ai) offers a managed version with no infrastructure setup.
Is Dify free? Open-source under a permissive license. Dify Cloud has a free tier. Self-hosting is fully free with Docker.