[PR #341] [MERGED] [Plugin] arrenxxxxx/mcp_config_during_use: MCP Config During Use #828

New Issue

2026-02-22T17:40:02-05:00

yindo commented

2026-02-22 17:40:02 -05:00

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/341
Author: @arrenxxxxx
Created: 4/14/2025
Status: ✅ Merged
Merged: 5/12/2025
Merged by: @LogicOber

Base: main ← Head: main

📝 Commits (4)

05d0e21 Add MCP Config During Use plugin
3a79c57 Merge branch 'langgenius:main' into main
b88e288 fix mcp terminology & package with dify-plugin-cli
933d74f fix mcp_cdu difypkg

📊 Changes

1 file changed (+0 additions, -0 deletions)

View changed files

➕ arrenxxxxx/mcp_config_during_use/mcp_config_during_use.difypkg (+0 -0)

📄 Description

Plugin Submission Form

1. Submission Type

New plugin submission
Version update for existing plugin

2. Description

MCP Config During Use is a plugin for Dify that allows configuring MCP (Modular Component Protocol) connections during use. It provides the ability to fetch and call tools via MCP protocol through HTTP with SSE transport, with configuration being done at runtime rather than at the provider level.

Repository URL: https://github.com/arrenxxxxx/dify-plugin-tools-mcp_config_during_use

3. Checklist

I have read and followed the Publish to Dify Marketplace guidelines
I have read and comply with the Plugin Developer Agreement
I confirm my plugin works properly on both Dify Community Edition and Cloud Version
I confirm my plugin has been thoroughly tested for completeness and functionality
My plugin brings new value to Dify

4. Documentation Checklist

Please confirm that your plugin README includes all necessary information:

Step-by-step setup instructions
Detailed usage instructions
All required APIs and credentials are clearly listed
Connection requirements and configuration details

5. Privacy Protection Information

Based on Dify Plugin Privacy Protection Guidelines:

Data Collection

This plugin does not collect, store, or transmit any personal data. All connection information (URL, headers, etc.) is only used during runtime to establish connections to the configured MCP servers.

Privacy Policy

I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-plugins/pull/341 **Author:** [@arrenxxxxx](https://github.com/arrenxxxxx) **Created:** 4/14/2025 **Status:** ✅ Merged **Merged:** 5/12/2025 **Merged by:** [@LogicOber](https://github.com/LogicOber) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (4) - [`05d0e21`](https://github.com/langgenius/dify-plugins/commit/05d0e2138cb011950c9c7e84a581bcfdb72c425d) Add MCP Config During Use plugin - [`3a79c57`](https://github.com/langgenius/dify-plugins/commit/3a79c57a3b9947ecac55317fa6195fd7a2b7d670) Merge branch 'langgenius:main' into main - [`b88e288`](https://github.com/langgenius/dify-plugins/commit/b88e2889e10672e17f754e50da836125703f5d14) fix mcp terminology & package with dify-plugin-cli - [`933d74f`](https://github.com/langgenius/dify-plugins/commit/933d74fd391a46c5d783ee41d0060d6a1d307b09) fix mcp_cdu difypkg ### 📊 Changes **1 file changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `arrenxxxxx/mcp_config_during_use/mcp_config_during_use.difypkg` (+0 -0) </details> ### 📄 Description # Plugin Submission Form ## 1. Submission Type * [x] New plugin submission * [ ] Version update for existing plugin ## 2. Description MCP Config During Use is a plugin for Dify that allows configuring MCP (Modular Component Protocol) connections during use. It provides the ability to fetch and call tools via MCP protocol through HTTP with SSE transport, with configuration being done at runtime rather than at the provider level. Repository URL: https://github.com/arrenxxxxx/dify-plugin-tools-mcp_config_during_use ## 3. Checklist * [x] I have read and followed the Publish to Dify Marketplace guidelines * [x] I have read and comply with the Plugin Developer Agreement * [x] I confirm my plugin works properly on both Dify Community Edition and Cloud Version * [x] I confirm my plugin has been thoroughly tested for completeness and functionality * [x] My plugin brings new value to Dify ## 4. Documentation Checklist Please confirm that your plugin README includes all necessary information: * [x] Step-by-step setup instructions * [x] Detailed usage instructions * [x] All required APIs and credentials are clearly listed * [x] Connection requirements and configuration details ## 5. Privacy Protection Information Based on Dify Plugin Privacy Protection Guidelines: ### Data Collection This plugin does not collect, store, or transmit any personal data. All connection information (URL, headers, etc.) is only used during runtime to establish connections to the configured MCP servers. ### Privacy Policy * [x] I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

yindo added the pull-request label 2026-02-22 17:40:02 -05:00

yindo closed this issue

2026-02-22 17:40:02 -05:00

yindo referenced this issue

2026-02-22 17:51:14 -05:00

[PR #828] [MERGED] bump markdown-editor plugin to version 0.0.2 #1210

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: langgenius/dify-plugins#828