mseep-dify-mcp-server 0.1.2__tar.gz → 0.1.3__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (13) hide show
  1. mseep_dify_mcp_server-0.1.3/PKG-INFO +16 -0
  2. mseep_dify_mcp_server-0.1.3/README.md +1 -0
  3. {mseep_dify_mcp_server-0.1.2 → mseep_dify_mcp_server-0.1.3}/pyproject.toml +1 -1
  4. mseep_dify_mcp_server-0.1.2/PKG-INFO +0 -172
  5. mseep_dify_mcp_server-0.1.2/README.md +0 -157
  6. {mseep_dify_mcp_server-0.1.2 → mseep_dify_mcp_server-0.1.3}/.gitignore +0 -0
  7. {mseep_dify_mcp_server-0.1.2 → mseep_dify_mcp_server-0.1.3}/.python-version +0 -0
  8. {mseep_dify_mcp_server-0.1.2 → mseep_dify_mcp_server-0.1.3}/Dockerfile +0 -0
  9. {mseep_dify_mcp_server-0.1.2 → mseep_dify_mcp_server-0.1.3}/setup.py +0 -0
  10. {mseep_dify_mcp_server-0.1.2 → mseep_dify_mcp_server-0.1.3}/smithery.yaml +0 -0
  11. {mseep_dify_mcp_server-0.1.2 → mseep_dify_mcp_server-0.1.3}/src/dify_mcp_server/__init__.py +0 -0
  12. {mseep_dify_mcp_server-0.1.2 → mseep_dify_mcp_server-0.1.3}/src/dify_mcp_server/server.py +0 -0
  13. {mseep_dify_mcp_server-0.1.2 → mseep_dify_mcp_server-0.1.3}/uv.lock +0 -0
mseep_dify_mcp_server-0.1.3/PKG-INFO ADDED
@@ -0,0 +1,16 @@
1
+ Metadata-Version: 2.4
2
+ Name: mseep-dify-mcp-server
3
+ Version: 0.1.3
4
+ Summary: Add your description here
5
+ Author-email: mseep <support@skydeck.ai>
6
+ Maintainer-email: mseep <support@skydeck.ai>
7
+ Requires-Python: >=3.10
8
+ Requires-Dist: httpx>=0.28.1
9
+ Requires-Dist: mcp>=1.1.2
10
+ Requires-Dist: omegaconf>=2.3.0
11
+ Requires-Dist: pip>=24.3.1
12
+ Requires-Dist: python-dotenv>=1.0.1
13
+ Requires-Dist: requests
14
+ Description-Content-Type: text/markdown
15
+
16
+ # Package managed by MseeP.ai
mseep_dify_mcp_server-0.1.3/README.md ADDED
@@ -0,0 +1 @@
1
+ # Package managed by MseeP.ai
{mseep_dify_mcp_server-0.1.2 → mseep_dify_mcp_server-0.1.3}/pyproject.toml RENAMED
@@ -1,6 +1,6 @@
1
1
  [project]
2
2
  name = "mseep-dify-mcp-server"
3
- version = "0.1.2"
3
+ version = "0.1.3"
4
4
  description = "Add your description here"
5
5
  readme = "README.md"
6
6
  requires-python = ">=3.10"
mseep_dify_mcp_server-0.1.2/PKG-INFO DELETED
@@ -1,172 +0,0 @@
1
- Metadata-Version: 2.4
2
- Name: mseep-dify-mcp-server
3
- Version: 0.1.2
4
- Summary: Add your description here
5
- Author-email: mseep <support@skydeck.ai>
6
- Maintainer-email: mseep <support@skydeck.ai>
7
- Requires-Python: >=3.10
8
- Requires-Dist: httpx>=0.28.1
9
- Requires-Dist: mcp>=1.1.2
10
- Requires-Dist: omegaconf>=2.3.0
11
- Requires-Dist: pip>=24.3.1
12
- Requires-Dist: python-dotenv>=1.0.1
13
- Requires-Dist: requests
14
- Description-Content-Type: text/markdown
15
-
16
- # Model Context Protocol (MCP) Server for dify workflows
17
- A simple implementation of an MCP server for using [dify](https://github.com/langgenius/dify). It achieves the invocation of the Dify workflow by calling the tools of MCP.
18
- ## 📰 News
19
- * [2025/4/15] zNow supports directly using environment variables to pass `base_url` and `app_sks`, making it more convenient to use with cloud-hosted platforms.
20
-
21
-
22
- ## 🔨Installation
23
- The server can be installed via [Smithery](https://smithery.ai/server/dify-mcp-server) or manually.
24
-
25
- ### Step1: prepare config.yaml or enviroments
26
- You can configure the server using either environment variables or a `config.yaml` file.
27
-
28
- #### Method 1: Using Environment Variables (Recommended for Cloud Platforms)
29
-
30
- Set the following environment variables:
31
-
32
- ```shell
33
- export DIFY_BASE_URL="https://cloud.dify.ai/v1"
34
- export DIFY_APP_SKS="app-sk1,app-sk2" # Comma-separated list of your Dify App SKs
35
- ```
36
-
37
- * `DIFY_BASE_URL`: The base URL for your Dify API.
38
- * `DIFY_APP_SKS`: A comma-separated list of your Dify App Secret Keys (SKs). Each SK typically corresponds to a different Dify workflow you want to make available via MCP.
39
-
40
- #### Method 2: Using `config.yaml`
41
-
42
- Create a `config.yaml` file to store your Dify base URL and App SKs.
43
-
44
- Example `config.yaml`:
45
-
46
- ```yaml
47
- dify_base_url: "https://cloud.dify.ai/v1"
48
- dify_app_sks:
49
- - "app-sk1" # SK for workflow 1
50
- - "app-sk2" # SK for workflow 2
51
- # Add more SKs as needed
52
- ```
53
-
54
- * `dify_base_url`: The base URL for your Dify API.
55
- * `dify_app_sks`: A list of your Dify App Secret Keys (SKs). Each SK typically corresponds to a different Dify workflow.
56
-
57
- You can create this file quickly using the following command (adjust the path and values as needed):
58
-
59
- ```bash
60
- # Create a directory if it doesn't exist
61
- mkdir -p ~/.config/dify-mcp-server
62
-
63
- # Create the config file
64
- cat > ~/.config/dify-mcp-server/config.yaml <<EOF
65
- dify_base_url: "https://cloud.dify.ai/v1"
66
- dify_app_sks:
67
- - "app-your-sk-1"
68
- - "app-your-sk-2"
69
- EOF
70
-
71
- echo "Configuration file created at ~/.config/dify-mcp-server/config.yaml"
72
- ```
73
-
74
- When running the server (as shown in Step 2), you will need to provide the path to this `config.yaml` file via the `CONFIG_PATH` environment variable if you choose this method.
75
-
76
- ### Step2: Installation on your client
77
- ❓ If you haven't installed uv or uvx yet, you can do it quickly with the following command:
78
- ```
79
- curl -Ls https://astral.sh/uv/install.sh | sh
80
- ```
81
-
82
- #### ✅ Method 1: Use uvx (no need to clone code, recommended)
83
-
84
- ```json
85
- {
86
- "mcpServers": {
87
- "dify-mcp-server": {
88
- "command": "uvx",
89
- "args": [
90
- "--from","git+https://github.com/YanxingLiu/dify-mcp-server","dify_mcp_server"
91
- ],
92
- "env": {
93
- "DIFY_BASE_URL": "https://cloud.dify.ai/v1",
94
- "DIFY_APP_SKS": "app-sk1,app-sk2",
95
- }
96
- }
97
- }
98
- }
99
- ```
100
- or
101
- ```json
102
- {
103
- "mcpServers": {
104
- "dify-mcp-server": {
105
- "command": "uvx",
106
- "args": [
107
- "--from","git+https://github.com/YanxingLiu/dify-mcp-server","dify_mcp_server"
108
- ],
109
- "env": {
110
- "CONFIG_PATH": "/Users/lyx/Downloads/config.yaml"
111
- }
112
- }
113
- }
114
- }
115
- ```
116
-
117
- #### ✅ Method 2: Use uv (local clone + uv start)
118
-
119
- You can also run the dify mcp server manually in your clients. The config of client should like the following format:
120
- ```json
121
- {
122
- "mcpServers": {
123
- "mcp-server-rag-web-browser": {
124
- "command": "uv",
125
- "args": [
126
- "--directory", "${DIFY_MCP_SERVER_PATH}",
127
- "run", "dify_mcp_server"
128
- ],
129
- "env": {
130
- "CONFIG_PATH": "$CONFIG_PATH"
131
- }
132
- }
133
- }
134
- }
135
- ```
136
- or
137
- ```json
138
- {
139
- "mcpServers": {
140
- "mcp-server-rag-web-browser": {
141
- "command": "uv",
142
- "args": [
143
- "--directory", "${DIFY_MCP_SERVER_PATH}",
144
- "run", "dify_mcp_server"
145
- ],
146
- "env": {
147
- "CONFIG_PATH": "$CONFIG_PATH"
148
- }
149
- }
150
- }
151
- }
152
- ```
153
- Example config:
154
- ```json
155
- {
156
- "mcpServers": {
157
- "dify-mcp-server": {
158
- "command": "uv",
159
- "args": [
160
- "--directory", "/Users/lyx/Downloads/dify-mcp-server",
161
- "run", "dify_mcp_server"
162
- ],
163
- "env": {
164
- "DIFY_BASE_URL": "https://cloud.dify.ai/v1",
165
- "DIFY_APP_SKS": "app-sk1,app-sk2",
166
- }
167
- }
168
- }
169
- }
170
- ```
171
- ### Enjoy it
172
- At last, you can use dify tools in any client who supports mcp.
mseep_dify_mcp_server-0.1.2/README.md DELETED
@@ -1,157 +0,0 @@
1
- # Model Context Protocol (MCP) Server for dify workflows
2
- A simple implementation of an MCP server for using [dify](https://github.com/langgenius/dify). It achieves the invocation of the Dify workflow by calling the tools of MCP.
3
- ## 📰 News
4
- * [2025/4/15] zNow supports directly using environment variables to pass `base_url` and `app_sks`, making it more convenient to use with cloud-hosted platforms.
5
-
6
-
7
- ## 🔨Installation
8
- The server can be installed via [Smithery](https://smithery.ai/server/dify-mcp-server) or manually.
9
-
10
- ### Step1: prepare config.yaml or enviroments
11
- You can configure the server using either environment variables or a `config.yaml` file.
12
-
13
- #### Method 1: Using Environment Variables (Recommended for Cloud Platforms)
14
-
15
- Set the following environment variables:
16
-
17
- ```shell
18
- export DIFY_BASE_URL="https://cloud.dify.ai/v1"
19
- export DIFY_APP_SKS="app-sk1,app-sk2" # Comma-separated list of your Dify App SKs
20
- ```
21
-
22
- * `DIFY_BASE_URL`: The base URL for your Dify API.
23
- * `DIFY_APP_SKS`: A comma-separated list of your Dify App Secret Keys (SKs). Each SK typically corresponds to a different Dify workflow you want to make available via MCP.
24
-
25
- #### Method 2: Using `config.yaml`
26
-
27
- Create a `config.yaml` file to store your Dify base URL and App SKs.
28
-
29
- Example `config.yaml`:
30
-
31
- ```yaml
32
- dify_base_url: "https://cloud.dify.ai/v1"
33
- dify_app_sks:
34
- - "app-sk1" # SK for workflow 1
35
- - "app-sk2" # SK for workflow 2
36
- # Add more SKs as needed
37
- ```
38
-
39
- * `dify_base_url`: The base URL for your Dify API.
40
- * `dify_app_sks`: A list of your Dify App Secret Keys (SKs). Each SK typically corresponds to a different Dify workflow.
41
-
42
- You can create this file quickly using the following command (adjust the path and values as needed):
43
-
44
- ```bash
45
- # Create a directory if it doesn't exist
46
- mkdir -p ~/.config/dify-mcp-server
47
-
48
- # Create the config file
49
- cat > ~/.config/dify-mcp-server/config.yaml <<EOF
50
- dify_base_url: "https://cloud.dify.ai/v1"
51
- dify_app_sks:
52
- - "app-your-sk-1"
53
- - "app-your-sk-2"
54
- EOF
55
-
56
- echo "Configuration file created at ~/.config/dify-mcp-server/config.yaml"
57
- ```
58
-
59
- When running the server (as shown in Step 2), you will need to provide the path to this `config.yaml` file via the `CONFIG_PATH` environment variable if you choose this method.
60
-
61
- ### Step2: Installation on your client
62
- ❓ If you haven't installed uv or uvx yet, you can do it quickly with the following command:
63
- ```
64
- curl -Ls https://astral.sh/uv/install.sh | sh
65
- ```
66
-
67
- #### ✅ Method 1: Use uvx (no need to clone code, recommended)
68
-
69
- ```json
70
- {
71
- "mcpServers": {
72
- "dify-mcp-server": {
73
- "command": "uvx",
74
- "args": [
75
- "--from","git+https://github.com/YanxingLiu/dify-mcp-server","dify_mcp_server"
76
- ],
77
- "env": {
78
- "DIFY_BASE_URL": "https://cloud.dify.ai/v1",
79
- "DIFY_APP_SKS": "app-sk1,app-sk2",
80
- }
81
- }
82
- }
83
- }
84
- ```
85
- or
86
- ```json
87
- {
88
- "mcpServers": {
89
- "dify-mcp-server": {
90
- "command": "uvx",
91
- "args": [
92
- "--from","git+https://github.com/YanxingLiu/dify-mcp-server","dify_mcp_server"
93
- ],
94
- "env": {
95
- "CONFIG_PATH": "/Users/lyx/Downloads/config.yaml"
96
- }
97
- }
98
- }
99
- }
100
- ```
101
-
102
- #### ✅ Method 2: Use uv (local clone + uv start)
103
-
104
- You can also run the dify mcp server manually in your clients. The config of client should like the following format:
105
- ```json
106
- {
107
- "mcpServers": {
108
- "mcp-server-rag-web-browser": {
109
- "command": "uv",
110
- "args": [
111
- "--directory", "${DIFY_MCP_SERVER_PATH}",
112
- "run", "dify_mcp_server"
113
- ],
114
- "env": {
115
- "CONFIG_PATH": "$CONFIG_PATH"
116
- }
117
- }
118
- }
119
- }
120
- ```
121
- or
122
- ```json
123
- {
124
- "mcpServers": {
125
- "mcp-server-rag-web-browser": {
126
- "command": "uv",
127
- "args": [
128
- "--directory", "${DIFY_MCP_SERVER_PATH}",
129
- "run", "dify_mcp_server"
130
- ],
131
- "env": {
132
- "CONFIG_PATH": "$CONFIG_PATH"
133
- }
134
- }
135
- }
136
- }
137
- ```
138
- Example config:
139
- ```json
140
- {
141
- "mcpServers": {
142
- "dify-mcp-server": {
143
- "command": "uv",
144
- "args": [
145
- "--directory", "/Users/lyx/Downloads/dify-mcp-server",
146
- "run", "dify_mcp_server"
147
- ],
148
- "env": {
149
- "DIFY_BASE_URL": "https://cloud.dify.ai/v1",
150
- "DIFY_APP_SKS": "app-sk1,app-sk2",
151
- }
152
- }
153
- }
154
- }
155
- ```
156
- ### Enjoy it
157
- At last, you can use dify tools in any client who supports mcp.