Dify Docs MCP
Dify's MCP posture has two distinct surfaces. (1) A live, anonymous, remote documentation MCP server at https://docs.dify.ai/mcp, confirmed by an unauthenticated tools/list call that returned three real tools with input schemas — saved verbatim to dify-mcp-tools.json. (2) A per-application MCP server feature: any Dify app owner can toggle "MCP Server" on the app's Access Point tab and Dify mints a unique, credential-bearing MCP URL for that one app. There is no single vendor-wide MCP endpoint for the Dify Service API.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Endpoint
Hosted endpoint · transport streamable-http
Connect
This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):
For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:
If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:
Tools
search_dify_docs— Search across the Dify Docs knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Dify Docs, find specific documentation, understand how features work,query_docs_filesystem_dify_docs— Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Dify Docs documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computersubmit_feedback— Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — n
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.