MCP Tools DirectoryAbout this integration
MCP server exposing Dify knowledge base retrieval to Cursor and other MCP clients
- Transport
- stdio
- Authentication
- api-key
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.0
- Package
- dify-mcp
- Last compatibility test
- Not independently tested
Connect your agent
dify-mcpPublisher documentation was reviewed from pinned captures. The package was not executed and no Dify data was accessed; transport security depends on the operator's base URL and TLS settings.
Capabilities: dataset discovery, dataset metadata, semantic retrieval, document browsing, segment browsing
Connected profiles
Additional details
io.github.salted-butter-joshua/dify-mcp
Source ↗ · Checked 2026-09-170.1.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17DIFY_API_BASE, DIFY_API_KEY, DIFY_ALLOWED_DATASETS
Source ↗ · Checked 2026-09-17dify-mcp
Source ↗ · Checked 2026-09-190.1.0
Source ↗ · Checked 2026-09-19The MCP client launches the configured Python process over stdio, so the publisher says no separate manual server startup is needed.
Source ↗ · Checked 2026-09-19The connection requires a Dify Knowledge Base API key and a required allowlist of dataset identifiers.
Source ↗ · Checked 2026-09-19The local process connects over HTTP or HTTPS to a configurable self-hosted or remote Dify Knowledge API base URL.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19