langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -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. #20118

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.

The final thought process showed: "there is not a tool named", but all my MCP tools are registered. Could it be a model illusion caused by the long inference chain?

Image

✔️ Expected Behavior

Hopefully, I can view the logs normally.

❌ Actual Behavior

Image 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. The final thought process showed: "there is not a tool named", but all my MCP tools are registered. Could it be a model illusion caused by the long inference chain? <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" /> <img width="642" height="102" alt="Image" src="https://github.com/user-attachments/assets/25bc6dba-1855-4051-8dbe-7691914eb063" />
yindo closed this issue 2026-02-21 20:05:55 -05:00
yindo commented 2026-02-21 20:05:56 -05:00
Author
Owner
Copy Link
Copy Source

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

The "provider type not found" and "there is not a tool named" errors after an MCP tool call are usually caused by one or more of the following:

  • The MCP provider plugin is missing or misconfigured, or the MCP Server URL is incorrect (it should point to the root /mcp endpoint, not /api/sse). If you're running in Docker, avoid using localhost or 127.0.0.1—use host.docker.internal or your actual IP address instead. Also, make sure your reverse proxy routes /mcp/* requests correctly and uses HTTPS if required. The agent app's toolbar must include both "Fetch MCP Tools" and "Call MCP Tool" for MCP tools to be available to the agent. For Qwen3, use the Tongyi plugin v0.0.19+ and set enable_thinking to false if not using streaming [source].

  • The error can also occur if the provider is not registered or referenced correctly in the tool configuration. Double-check your provider and tool setup for typos or missing fields, as the code looks up the provider by ID and type during tool invocation [source].

  • If any MCP tool in your database is missing a description (i.e., the description field is null in the tool_mcp_providers table), Dify will not recognize the tool and will throw errors like these. Make sure all MCP tools have valid, non-null descriptions in the database [source].

  • If you're using a local model, ensure it is configured to support tool calls in Dify (i.e., it must have tool-call, multi-tool-call, or stream-tool-call in its features). In the Dify UI, set the "Function Calling" method to "Tool Call" (not the deprecated "Function Call"). Your vLLM/OpenAI-compatible endpoint must support the latest OpenAI tool calling API, not just function calling [source].

Recent Dify releases (after v1.9.2) include fixes and refactors for MCP tool and provider handling, so if all configuration steps are correct and the error persists, consider updating to the latest version [source].

If you check these areas and update any missing or incorrect configuration, the error should be resolved and logs should display as expected.

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" and "there is not a tool named" errors after an MCP tool call are usually caused by one or more of the following: - The MCP provider plugin is missing or misconfigured, or the MCP Server URL is incorrect (it should point to the root `/mcp` endpoint, not `/api/sse`). If you're running in Docker, avoid using `localhost` or `127.0.0.1`—use `host.docker.internal` or your actual IP address instead. Also, make sure your reverse proxy routes `/mcp/*` requests correctly and uses HTTPS if required. The agent app's toolbar must include both "Fetch MCP Tools" and "Call MCP Tool" for MCP tools to be available to the agent. For Qwen3, use the Tongyi plugin v0.0.19+ and set `enable_thinking` to false if not using streaming [[source]](https://github.com/langgenius/dify/issues/27805). - The error can also occur if the provider is not registered or referenced correctly in the tool configuration. Double-check your provider and tool setup for typos or missing fields, as the code looks up the provider by ID and type during tool invocation [[source]](https://github.com/langgenius/dify/issues/27805). - If any MCP tool in your database is missing a description (i.e., the `description` field is null in the `tool_mcp_providers` table), Dify will not recognize the tool and will throw errors like these. Make sure all MCP tools have valid, non-null descriptions in the database [[source]](https://github.com/langgenius/dify/issues/22179). - If you're using a local model, ensure it is configured to support tool calls in Dify (i.e., it must have `tool-call`, `multi-tool-call`, or `stream-tool-call` in its features). In the Dify UI, set the "Function Calling" method to "Tool Call" (not the deprecated "Function Call"). Your vLLM/OpenAI-compatible endpoint must support the latest OpenAI tool calling API, not just function calling [[source]](https://github.com/langgenius/dify/issues/24166). Recent Dify releases (after v1.9.2) include fixes and refactors for MCP tool and provider handling, so if all configuration steps are correct and the error persists, consider updating to the latest version [[source]](https://github.com/langgenius/dify/pull/25766). If you check these areas and update any missing or incorrect configuration, the error should be resolved and logs should display as expected. <!-- 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/868b8077-61b8-421f-a20b-8481cd3e704b?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/868b8077-61b8-421f-a20b-8481cd3e704b?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/868b8077-61b8-421f-a20b-8481cd3e704b?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/868b8077-61b8-421f-a20b-8481cd3e704b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/868b8077-61b8-421f-a20b-8481cd3e704b?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/868b8077-61b8-421f-a20b-8481cd3e704b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/868b8077-61b8-421f-a20b-8481cd3e704b?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/27812)
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
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#20118
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?