1. Conduid
  2. AI
  3. Difydocmcpserver
MCP server · AI

Difydocmcpserver

一个用于集成Dify知识库的MCP (Model Context Protocol) Server,允许AI助手直接访问和检索Dify知识库中的内容。

Unclaimed last commit a year ago ai
41Fair

Scored 5 months ago · breakdown

About Difydocmcpserver

Difydocmcpserver is an MCP server published by shellus in the AI category: 一个用于集成Dify知识库的MCP (Model Context Protocol) Server,允许AI助手直接访问和检索Dify知识库中的内容。.

The repository has 4 stars and 1 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/shellus/difydocmcpserver

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Difydocmcpserver

Powered by Claude · Grounded in docs

I know everything about Difydocmcpserver. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

Static checks derived from the repository 21 hours ago. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • !License declaredNo license file. Legally you have no right to use it in a product.
  • !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
  • ✓Dependencies pinnedA lockfile pins dependency versions.
  • ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

Dify Doc MCP Server

一个用于集成Dify知识库的MCP (Model Context Protocol) Server,允许AI助手直接访问和检索Dify知识库中的内容。

技术选型

  • 语言: TypeScript
  • 运行环境: Node.js v18+
  • MCP框架: @modelcontextprotocol/sdk
  • HTTP客户端: axios
  • 数据验证: zod
  • 传输方式: StdioServerTransport (标准输入输出)

主要架构

本项目实现了三个核心工具:

  1. dify_retrieve_knowledge - 知识库检索
  2. dify_list_datasets - 获取知识库列表
  3. dify_get_dataset_detail - 获取知识库详情

通过MCP协议与Dify REST API集成,支持语义检索、关键字检索、全文检索和混合检索等多种检索方式。

安装

全局安装

npm install -g dify-doc-mcp-server

或使用npx(无需安装)

npx dify-doc-mcp-server

快速开始

方式一:使用npx(推荐)

# 直接运行,无需安装
DIFY_BASE_URL="http://your-dify-host:8031" DIFY_API_KEY="your-api-key" npx dify-doc-mcp-server

方式二:本地开发

# 1. 克隆项目
git clone <repository-url>
cd difydocmcpserver

# 2. 安装依赖
npm install

# 3. 配置环境变量
export DIFY_BASE_URL="http://localhost:8031"
export DIFY_API_KEY="your-dify-api-key"

# 4. 构建和运行
npm run build
npm start

可用工具

dify_list_datasets

获取Dify知识库列表

  • keyword (可选): 搜索关键词
  • limit (可选): 返回条数 (1-100,默认20)

dify_get_dataset_detail

获取Dify知识库详细信息

  • dataset_id (必需): 知识库ID

dify_retrieve_knowledge

从Dify知识库中检索相关内容

  • dataset_id (必需): 知识库ID
  • query (必需): 检索查询内容
  • search_method (可选): 检索方法 (semantic_search/keyword_search/full_text_search/hybrid_search)
  • top_k (可选): 返回结果数量 (1-20,默认3)
  • score_threshold (可选): 相似度阈值 (0-1,默认0)

MCP客户端配置

{
  "mcpServers": {
    "dify-doc": {
      "command": "npx",
      "args": ["dify-doc-mcp-server"],
      "env": {
        "DIFY_BASE_URL": "http://your-dify-host:8031",
        "DIFY_API_KEY": "your-dify-api-key"
      }
    }
  }
}

API密钥获取

  1. 登录Dify控制台
  2. 进入"设置" → "知识库" → "API" → "API密钥"
  3. 创建新的API密钥
  4. 复制密钥并设置到环境变量中

测试

# 设置环境变量并运行测试
DIFY_BASE_URL="http://your-dify-host:8031" DIFY_API_KEY="your-api-key" DATASET="your-dataset-name" QUERY="引导" node test-mcp.js

测试脚本会验证:

  • MCP Server连接
  • 工具列表获取
  • 知识库列表、详情和检索功能

相关链接

README fetched from the repository 21 hours ago. The original is authoritative.

Questions

About Difydocmcpserver

How do I install Difydocmcpserver?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Difydocmcpserver safe to use with an AI agent?

Its trust score is 41 out of 100 (fair). It passes 3 of the 6 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Difydocmcpserver still maintained?

The last commit was a year ago and 1 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.