langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

After publishing a workflow as an MCP service, a 404 error occurs when attempting to access MCP tools via the MCP SSE / StreamableHTTP plugin. #715

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

Originally created by @hyxl520 on GitHub (Oct 15, 2025).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues Dify issues & Dify Official Plugins, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.7.1

Plugin version

0.2.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

After configuring MCP according to the image, the tool cannot be found when called, resulting in a 404 error.
Image

Image

✔️ Error log

No response

Originally created by @hyxl520 on GitHub (Oct 15, 2025). ### Self Checks - [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 [Dify issues](https://github.com/langgenius/dify/issues) & [Dify Official Plugins](https://github.com/langgenius/dify-official-plugins/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.7.1 ### Plugin version 0.2.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce After configuring MCP according to the image, the tool cannot be found when called, resulting in a 404 error. <img width="1137" height="660" alt="Image" src="https://github.com/user-attachments/assets/54d51dc1-ff60-4416-a38b-784e241cd130" /> <img width="640" height="655" alt="Image" src="https://github.com/user-attachments/assets/13648c96-7bf2-46c3-b3f7-ca79e6426413" /> ### ✔️ Error log _No response_
yindo added the bug label 2026-02-16 10:20:17 -05:00
yindo closed this issue 2026-02-16 10:20:17 -05:00
yindo commented 2026-02-16 10:20:17 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 15, 2025):

Hi @hyxl520! I'm Dosu and I’m helping the dify-official-plugins team.

A recent fix in Dify addressed incorrect API endpoint routing that could cause 404 errors when accessing workflow-related endpoints, including those used by MCP tools. The fix changed several workflow API routes, such as /apps/<uuid:app_id>/workflows/published to /apps/<uuid:app_id>/workflows, and adjusted parameter types and naming for consistency. If your deployment is based on Dify v1.7.1 and plugin v0.2.3, it's possible your instance is affected by these routing issues. Double-check that your MCP tool endpoints match the updated routes and that your workflow is published and registered correctly. You can review the relevant changes here: PR #25778.

Common causes for 404s in this context include endpoint mismatches, registration failures, or Docker networking/configuration issues. Make sure your MCP service is properly registered and exposed, and that your plugin configuration aligns with the expected endpoint structure.

To reply, just mention @dosu.

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

@dosubot[bot] commented on GitHub (Oct 15, 2025): <!-- Greeting --> Hi @hyxl520! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify-official-plugins team. <!-- Answer --> A recent fix in Dify addressed incorrect API endpoint routing that could cause 404 errors when accessing workflow-related endpoints, including those used by MCP tools. The fix changed several workflow API routes, such as `/apps/<uuid:app_id>/workflows/published` to `/apps/<uuid:app_id>/workflows`, and adjusted parameter types and naming for consistency. If your deployment is based on Dify v1.7.1 and plugin v0.2.3, it's possible your instance is affected by these routing issues. Double-check that your MCP tool endpoints match the updated routes and that your workflow is published and registered correctly. You can review the relevant changes here: [PR #25778](https://github.com/langgenius/dify/pull/25778). Common causes for 404s in this context include endpoint mismatches, registration failures, or Docker networking/configuration issues. Make sure your MCP service is properly registered and exposed, and that your plugin configuration aligns with the expected endpoint structure. <!-- 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/efe49327-aa36-4379-a683-18ced69b7dde?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/efe49327-aa36-4379-a683-18ced69b7dde?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/efe49327-aa36-4379-a683-18ced69b7dde?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/efe49327-aa36-4379-a683-18ced69b7dde?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/efe49327-aa36-4379-a683-18ced69b7dde?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/efe49327-aa36-4379-a683-18ced69b7dde?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/efe49327-aa36-4379-a683-18ced69b7dde?feedback_type=other)</sup>&nbsp;&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-official-plugins/issues/1865)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
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-official-plugins#715
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?