dify-mcp-client

Created By
3dify-projecta year ago
MCP Client as an Agent Strategy Plugin. Dify is not MCP Server but MCP Host.
Overview

What is Dify MCP Client?

Dify MCP Client is an Agent Strategy Plugin designed to connect with an MCP server, allowing for the execution of various tasks through a ReAct agent framework.

How to use Dify MCP Client?

To use Dify MCP Client, deploy the source code, configure the necessary settings, and execute the plugin using the command python -m main in the CLI. Ensure that the MCP server is properly set up and connected.

Key features of Dify MCP Client?

  • Connects to a standard input/output MCP server.
  • Converts tool, resource, and prompt lists into Dify Tools for LLM access.
  • Supports multiple functions for MCP operations.

Use cases of Dify MCP Client?

  1. Integrating with various MCP servers for task automation.
  2. Utilizing the ReAct loop for dynamic agent interactions.
  3. Developing and deploying custom plugins for specific workflows.

FAQ from Dify MCP Client?

  • Is Dify MCP Client free to use?

Yes! Dify MCP Client is open-source and free to use.

  • What programming language is used?

The Dify MCP Client is developed in Python.

  • How can I report issues or contribute?

You can report issues or contribute by visiting the GitHub repository and creating an issue or pull request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
3dify-project
Star
75
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
Payai X402 Tools

2 hours ago
Payai X402 Tools

2 hours 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