mcpField
D
Dify MCP Server

Dify MCP Server

Local
github.com/zhuzhoulinAI & Agents5Updated 81w ago

About Dify MCP Server

Dify MCP Server is a TypeScript server that connects multiple Dify applications to MCP clients. It retrieves application specifications from the Dify API and dynamically generates tool interfaces from them.

Key features

  1. 01Connect multiple Dify apps with API keys
  2. 02Fetch application metadata and parameters
  3. 03Generate tools from app specifications
  4. 04Accept text, paragraph, and dropdown inputs
  5. 05Support blocking and streaming responses

Use cases

  1. 01Call Dify applications from an MCP client
  2. 02Provide a unified tool entry for multiple apps
  3. 03Generate interfaces from application parameters

MCP support

The MCP server reads Dify application configurations and exposes each application as a separate tool to MCP clients.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Dify MCP Server

Dify Logo

English | 中文

A TypeScript-based MCP (Model Context Protocol) server that connects the MCP Client to Dify applications. This server dynamically exposes Dify applications as tools that can be used directly within the MCP Client.

Overview

This server implements the Model Context Protocol to bridge between MCP Client and Dify applications. It dynamically fetches application specifications from Dify APIs and exposes them as MCP tools. The server allows users to interact with multiple Dify applications through a unified interface within the MCP Client.

Features

Dynamic Dify Integration
  • Connects to multiple Dify applications using API keys
  • Automatically fetches application metadata and parameters
  • Dynamically generates tool interfaces based on Dify application specifications
  • Supports various input types including text, paragraphs, and select dropdowns
Request Handling
  • Robust error handling with request retries
  • Support for both blocking and streaming response modes
  • JSON BigInt handling for large numeric values
Configuration
  • API keys configured through environment variables
  • Configurable base URL and timeout settings
  • Fallback to default values when environment variables are not available

Installation

Prerequisites
  • Node.js (v16 or higher)
  • npm or yarn
Setup
  1. Clone the repository
git clone https://github.com/zhuzhoulin/dify-mcp-server.git
cd dify-mcp-server
  1. Install dependencies
npm install
  1. Build the project
npm run build
Integration with Windsurf IDE

To use with Windsurf IDE, add the server config to your MCP settings:

{
  "mcpServers": {
    "dify-mcp-server": {
      "command": "node",
      "args": [
        "/path/to/dify-mcp-server/build/index.js"
      ],
      "env": {
        "AGENT_API_KEYS": "key1,key2,key3",
        "BASE_URL": "https://api.dify.ai",
        "TIMEOUT": "60000"
      }
    }
  }
}

Environment Variables

  • AGENT_API_KEYS: Comma-separated list of Dify API keys
  • BASE_URL: Base URL for Dify API(default:https://api.dify.ai)
  • TIMEOUT: Request timeout in milliseconds (default: 60000)

How to get Environment Variables

API密钥(AGENT_API_KEYS): 多个以,分割

1744026439630

1744026494831

Usage

Once configured, the Dify MCP Server will:

  1. Connect to the specified Dify applications using the provided API keys
  2. Fetch application metadata and parameter specifications
  3. Generate MCP tool interfaces based on the Dify application configurations
  4. Make these tools available within the Windsurf IDE

Each Dify application will be exposed as a separate tool with a name format of dify_app_info_{application_name}.

Development

Available Scripts
  • npm run build: Build the project
  • npm run prepare: Prepare the project for distribution
  • npm run watch: Watch for changes and rebuild
  • npm run inspector: Run the MCP inspector for debugging
Project Structure
  • src/index.ts: Main server implementation
  • src/request.ts: HTTP client for Dify API communication
  • src/type.ts: TypeScript interfaces for Dify API

Troubleshooting

If you encounter issues:

  1. Verify your API keys are correct and have the necessary permissions
  2. Check that the BASE_URL is accessible from your environment
  3. Review server logs for detailed error messages
  4. Ensure the Dify applications are properly configured and accessible

License

This project is licensed under the terms specified in the LICENSE file.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.