Dify MCP Server (TypeScript)

Created By
faiz-geara year ago
Overview

what is Dify MCP Server?

Dify MCP Server is a TypeScript implementation of a Model Context Protocol (MCP) server that exposes Dify workflows as tools.

how to use Dify MCP Server?

To use Dify MCP Server, install it via Smithery, clone the repository, install dependencies, create a configuration file, build the project, and start the server.

key features of Dify MCP Server?

  • Converts Dify applications into MCP tools
  • Supports streaming responses from Dify workflows
  • Configurable via YAML configuration file
  • Written in TypeScript for type safety

use cases of Dify MCP Server?

  1. Integrating Dify workflows into applications as tools.
  2. Enabling streaming responses for real-time applications.
  3. Configuring Dify applications for various environments using YAML.

FAQ from Dify MCP Server?

  • What are the prerequisites for using Dify MCP Server?

You need Node.js 18 or higher and npm 8 or higher, along with access to Dify API and application secret keys.

  • How do I install Dify MCP Server?

You can install it via Smithery or by cloning the repository and installing dependencies manually.

  • Can I configure the server?

Yes, the server can be configured using a YAML file.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
faiz-gear
Star
-
Language
-
License
-

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago