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

After executing the mcp tool call in the agent, the runtime log details show the error: provider type not found. #20115

New Issue
Closed
opened 2026-02-21 20:05:55 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 20:05:55 -05:00
Owner
Copy Link
Copy Source

Originally created by @jizhuwojiaopaozong on GitHub (Nov 4, 2025).

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.9.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

After executing the mcp tool call in the agent, the runtime log details show the error: provider type not found.

Image

✔️ Expected Behavior

Hopefully, I can view the logs normally.

❌ Actual Behavior

Image
Originally created by @jizhuwojiaopaozong on GitHub (Nov 4, 2025). ### 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.9.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce After executing the mcp tool call in the agent, the runtime log details show the error: provider type not found. <img width="1125" height="883" alt="Image" src="https://github.com/user-attachments/assets/55559692-f03e-40fc-b681-0f1e1cd7357e" /> ### ✔️ Expected Behavior Hopefully, I can view the logs normally. ### ❌ Actual Behavior <img width="1125" height="883" alt="Image" src="https://github.com/user-attachments/assets/55559692-f03e-40fc-b681-0f1e1cd7357e" />
yindo added the 🤖 feat:agent label 2026-02-21 20:05:55 -05:00
yindo closed this issue 2026-02-21 20:05:55 -05:00
yindo commented 2026-02-21 20:05:55 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 4, 2025):

The "provider type not found" error after calling the MCP tool in the agent is usually caused by a missing or misconfigured MCP provider plugin, incorrect MCP server URL, or network issues in Docker. Make sure you have the MCP SSE plugin installed and configured with the correct MCP Server URL (it should point to the root /mcp endpoint, not /api/sse). For Qwen3, use the Tongyi plugin (v0.0.19+), and set enable_thinking to false if not using streaming.

Check that your agent app's toolbar includes both "Fetch MCP Tools" and "Call MCP Tool". If you're running in Docker, avoid using localhost or 127.0.0.1 for MCP endpoints—use host.docker.internal or your actual IP address instead. Also, ensure your reverse proxy (like Nginx) routes /mcp/* requests to the backend and that HTTPS is used for MCP URLs if required by your setup.

The error can also occur if the provider is not registered or referenced correctly in the tool configuration. The code looks up the provider by ID and type during tool invocation, so any mismatch or missing registration will trigger this error. Double-check your provider and tool setup for typos or missing fields.

If all configuration steps are correct and the error persists, check your logs for more details and consider updating to the latest Dify version, as some tool invocation issues have been fixed in recent releases.
Reference 1 | Reference 2

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Nov 4, 2025): <!-- Answer --> The "provider type not found" error after calling the MCP tool in the agent is usually caused by a missing or misconfigured MCP provider plugin, incorrect MCP server URL, or network issues in Docker. Make sure you have the MCP SSE plugin installed and configured with the correct MCP Server URL (it should point to the root `/mcp` endpoint, not `/api/sse`). For Qwen3, use the Tongyi plugin (v0.0.19+), and set `enable_thinking` to false if not using streaming. Check that your agent app's toolbar includes both "Fetch MCP Tools" and "Call MCP Tool". If you're running in Docker, avoid using `localhost` or `127.0.0.1` for MCP endpoints—use `host.docker.internal` or your actual IP address instead. Also, ensure your reverse proxy (like Nginx) routes `/mcp/*` requests to the backend and that HTTPS is used for MCP URLs if required by your setup. The error can also occur if the provider is not registered or referenced correctly in the tool configuration. The code looks up the provider by ID and type during tool invocation, so any mismatch or missing registration will trigger this error. Double-check your provider and tool setup for typos or missing fields. If all configuration steps are correct and the error persists, check your logs for more details and consider updating to the latest Dify version, as some tool invocation issues have been fixed in recent releases. [Reference 1](https://github.com/langgenius/dify/discussions/20835) | [Reference 2](https://github.com/langgenius/dify/issues/23811) <!-- 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/e48fb194-93ab-4eaa-bb56-af59c1d6e4dd?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/e48fb194-93ab-4eaa-bb56-af59c1d6e4dd?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/e48fb194-93ab-4eaa-bb56-af59c1d6e4dd?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/e48fb194-93ab-4eaa-bb56-af59c1d6e4dd?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/e48fb194-93ab-4eaa-bb56-af59c1d6e4dd?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/e48fb194-93ab-4eaa-bb56-af59c1d6e4dd?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/e48fb194-93ab-4eaa-bb56-af59c1d6e4dd?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&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/27805)
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 🤖 feat:agent
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#20115
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?