広告掲載
MCP.so
ログイン

Gotoolkits_mcp Difyworkflow Server MCP Server

@MCP-Mirror

リポジトリ

基本情報

カテゴリ

その他

トランスポート

stdio

作者

MCP-Mirror

Gotoolkits_mcp Difyworkflow Server MCP Server について

Mirror of

#mcp#difyworkflow#server

Gotoolkits_mcp Difyworkflow Server MCP Server の設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

Gotoolkits_mcp Difyworkflow Server MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Gotoolkits_mcp Difyworkflow Server?

Gotoolkits_mcp Difyworkflow Server is an MCP server Tools application that lets you query and invoke Dify workflows on demand, supporting multiple custom workflows simultaneously. It is built for developers using the Dify platform who want to trigger workflows via an MCP client.

How to use Gotoolkits_mcp Difyworkflow Server?

Clone the repository, build the binary with Go or make, then configure the server in your MCP client’s settings JSON. Set the Dify API base URL via -base-url, and provide comma-separated workflow names and API keys via the environment variables DIFY_WORKFLOW_NAME and DIFY_API_KEYS. Use the tools list_workflows to list authorized workflows and execute_workflow to run one by name, passing the input as message.

Key features of Gotoolkits_mcp Difyworkflow Server

  • Lists all authorized Dify workflows.
  • Executes any named workflow with custom input.
  • Supports multiple workflows with one-to-one name/key mapping.
  • Uses the Dify platform API for all operations.
  • Works with any MCP‑compatible client.

Use cases of Gotoolkits_mcp Difyworkflow Server

  • Trigger a translation workflow from an AI assistant.
  • Run a content generation workflow by name.
  • Automate multi‑step Dify pipelines via MCP tools.
  • Integrate Dify workflows into larger MCP‑based toolchains.

よくある質問

1

What dependencies or runtime are required?

The server is a compiled Go binary. You only need the binary and a Dify platform with an accessible API endpoint.

2

How are workflow names and API keys configured?

Set `DIFY_WORKFLOW_NAME` and `DIFY_API_KEYS` as comma‑separated lists. The order must correspond one‑to‑one – the first name maps to the first key, and so on.

3

What transport or authentication does the server use?

It communicates with the Dify API via the base URL you provide (e.g., `http://localhost/v1`). Authentication is handled by the API keys supplied in the environment.

4

What is the expected input variable name for a Dify workflow?

The Dify workflow’s input variable should be defined as "message". The `execute_workflow` tool passes the user’s input under that key.

5

Are there any limitations on workflow names or keys?

No limits are stated beyond the requirement that names and keys be provided in matching order. The server supports multiple workflows but the exact maximum is not specified.

コメント

「その他」の他のコンテンツ

N

Next Generation Movers: free moving quotes (remote MCP)

Next Generation Movers

Free moving quotes for AI agents from Next Generation Movers, a licensed interstate mover (USDOT 3764697). US long-distance nationwide and local DC/MD/VA. Indicative ballpark price and booking options; optional $0.01 x40

Codelf

unbug

A search tool helps dev to solve the naming things problem.

14.2K

Hindsight

vectorize-io

Hindsight: Agent Memory That Learns

50.4K

Volley.sh

Volley

A good sequence diagram can solve almost any communication problem in engineering. Volley lets your agent write them as plain text, with the real request and response payloads on every arrow. It checks its own syntax wi

ICSS

chokcoco

不止于 CSS

20.7K
広告掲載