langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 12:36:14 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

dify1.11.1 MCP tool cannot be successfully added on the first attempt; it requires a second edit and save to be added. #21202

New Issue
Closed
opened 2026-02-21 20:11:25 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 20:11:25 -05:00
Owner
Copy Link
Copy Source

Originally created by @gyl6666 on GitHub (Dec 22, 2025).

Originally assigned to: @fatelei on GitHub.

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.11.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

1、click tools-->mcp-->add mcp
2、add mcp server url and params ，and then save
3、no mcp tools will be seen in the right side bar
4、edit the mcp server ,then save
5、tools will be seen now

✔️ Expected Behavior

mcp tools will be seen in the right side bar

❌ Actual Behavior

There is no mcp tools in the right side bar

Originally created by @gyl6666 on GitHub (Dec 22, 2025). Originally assigned to: @fatelei on GitHub. ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.11.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1、click tools-->mcp-->add mcp 2、add mcp server url and params ，and then save 3、no mcp tools will be seen in the right side bar 4、edit the mcp server ,then save 5、tools will be seen now ### ✔️ Expected Behavior mcp tools will be seen in the right side bar ### ❌ Actual Behavior There is no mcp tools in the right side bar
yindo added the 🐞 bug label 2026-02-21 20:11:25 -05:00
yindo closed this issue 2026-02-21 20:11:25 -05:00
yindo commented 2026-02-21 20:11:26 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 22, 2025):

This is a known bug in Dify v1.11.1: when you add an MCP server, the tools don't appear in the sidebar until you edit and save the provider a second time. The root cause is that the initial creation only saves metadata and leaves the tools list empty; the actual tool-fetching and validation only happen on update, not on create. That's why the tools only show up after a second save. Fixing this would require adding the tool-fetch logic to the creation path so tools are available immediately after the first save. The issue is already tracked and remains open as of now—no merged pull requests address it yet.

As a workaround, editing and saving the MCP provider again will populate the tools. Also, make sure all your MCP tool descriptions are non-null, as missing descriptions can cause tools to disappear from the UI due to validation errors. If you run into that, updating any null description fields in the tool_mcp_providers table and restarting the backend can help restore visibility.

For updates or a permanent fix, keep an eye on the issue tracker.
Technical details and related issues
Code reference for provider creation and update logic

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Dec 22, 2025): <!-- Answer --> This is a known bug in Dify v1.11.1: when you add an MCP server, the tools don't appear in the sidebar until you edit and save the provider a second time. The root cause is that the initial creation only saves metadata and leaves the tools list empty; the actual tool-fetching and validation only happen on update, not on create. That's why the tools only show up after a second save. Fixing this would require adding the tool-fetch logic to the creation path so tools are available immediately after the first save. The issue is already tracked and remains open as of now—no merged pull requests address it yet. As a workaround, editing and saving the MCP provider again will populate the tools. Also, make sure all your MCP tool descriptions are non-null, as missing descriptions can cause tools to disappear from the UI due to validation errors. If you run into that, updating any null description fields in the `tool_mcp_providers` table and restarting the backend can help restore visibility. For updates or a permanent fix, keep an eye on the issue tracker. [Technical details and related issues](https://github.com/langgenius/dify/issues/22179) [Code reference for provider creation and update logic](https://github.com/langgenius/dify/blob/eabdc5f0ebd806ede0c8f8695d54efb24e61748b/api/services/tools/mcp_tools_manage_service.py#L44-L792) <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/2035a92c-366a-46fb-b4fd-9c345890a2dd?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/2035a92c-366a-46fb-b4fd-9c345890a2dd?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/2035a92c-366a-46fb-b4fd-9c345890a2dd?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/2035a92c-366a-46fb-b4fd-9c345890a2dd?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/2035a92c-366a-46fb-b4fd-9c345890a2dd?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/2035a92c-366a-46fb-b4fd-9c345890a2dd?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/2035a92c-366a-46fb-b4fd-9c345890a2dd?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20is%20a%20known%20bug%20in%20Dify%20v1.11.1%3A%20when%20you%20add%20an%20MCP%20server%2C%20the%20tools%20don%27t%20appear%20in%20the%20sidebar%20until%20you%20edit%20and%20save%20the%20provider%20a%20second%20time.%20The%20root%20cause%20is%20that%20the%20initial%20creation%20only%20saves%20metadata%20and%20leaves%20the%20tools%20list%20empty%3B%20the%20actual%20tool-fetching%20and%20validation%20only%20happen%20on%20update%2C%20not%20on%20create.%20That%27s%20why%20the%20tools%20only%20show%20up%20after%20a%20second%20save.%20Fixing%20this%20would%20require%20adding%20the%20tool-fetch%20logic%20to%20the%20creation%20path%20so%20tools%20are%20available%20immediately%20after%20the%20first%20save.%20The%20issue%20is%20already%20tracked%20and%20remains%20open%20as%20of%20now%E2%80%94no%20merged%20pull%20requests%20address%20it%20yet.%0A%0AAs%20a%20workaround%2C%20editing%20and%20saving%20the%20MCP%20provider%20again%20will%20populate%20the%20tools.%20Also%2C%20make%20sure%20all%20your%20MCP%20tool%20descriptions%20are%20non-null%2C%20as%20missing%20descriptions%20can%20cause%20tools%20to%20disappear%20from%20the%20UI%20due%20to%20validation%20errors.%20If%20you%20run%20into%20that%2C%20updating%20any%20null%20description%20fields%20in%20the%20%60tool_mcp_providers%60%20table%20and%20restarting%20the%20backend%20can%20help%20restore%20visibility.%0A%0AFor%20updates%20or%20a%20permanent%20fix%2C%20keep%20an%20eye%20on%20the%20issue%20tracker.%20%20%0A%5BTechnical%20details%20and%20related%20issues%5D%28https%3A//github.com/langgenius/dify/issues/22179%29%20%20%0A%5BCode%20reference%20for%20provider%20creation%20and%20update%20logic%5D%28https%3A//github.com/langgenius/dify/blob/eabdc5f0ebd806ede0c8f8695d54efb24e61748b/api/services/tools/mcp_tools_manage_service.py%23L44-L792%29)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/29987)
yindo commented 2026-02-21 20:11:26 -05:00
Author
Owner
Copy Link
Copy Source

@Nov1c444 commented on GitHub (Dec 24, 2025):

It looks like this issue was fixed in #29972. The issue was caused by the tool-providers API using Redis cache, but the auth API didn't refresh the cache in Redis. It has been fixed.

@Nov1c444 commented on GitHub (Dec 24, 2025): It looks like this issue was fixed in #29972. The issue was caused by the `tool-providers` API using Redis cache, but the `auth` API didn't refresh the cache in Redis. It has been fixed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#21202
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?