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

File type input is missing after publishing Apps as MCP Service #21085

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

Originally created by @Usigned on GitHub (Dec 16, 2025).

Originally assigned to: @Nov1c444 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

Cloud

Steps to reproduce

I create a workflow application with two inputs, one of which is file type and i publish it as a MCP service.

Image

Then i import this MCP service in tool->MCP tab and i find that the file type input is missing, neither can i find it when building new workflow apps.

Image Image

I am not sure whether this is a bug or if the Dify platform does not support MCP tools with file-type inputs.

✔️ Expected Behavior

the file type input appears in param list.

❌ Actual Behavior

the file type input is missing

Originally created by @Usigned on GitHub (Dec 16, 2025). Originally assigned to: @Nov1c444 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 Cloud ### Steps to reproduce I create a workflow application with two inputs, one of which is file type and i publish it as a MCP service. <img width="671" height="678" alt="Image" src="https://github.com/user-attachments/assets/7810c8b9-efee-4aaa-80eb-13663b0cb974" /> Then i import **this MCP service** in **tool->MCP** tab and i find that the file type input is missing, neither can i find it when building new workflow apps. <img width="731" height="278" alt="Image" src="https://github.com/user-attachments/assets/c64a128f-66b5-4e43-8b99-37a5bfdd8bea" /> <img width="671" height="581" alt="Image" src="https://github.com/user-attachments/assets/24bd4bd5-9292-47fc-ae48-b8fcddcfb7af" /> I am not sure whether this is a bug or if the Dify platform does not support MCP tools with file-type inputs. ### ✔️ Expected Behavior the file type input appears in param list. ### ❌ Actual Behavior the file type input is missing
yindo added the 🐞 bug label 2026-02-21 20:10:37 -05:00
yindo closed this issue 2026-02-21 20:10:37 -05:00
yindo commented 2026-02-21 20:10:38 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi @Usigned! I'm Dosu and I’m helping the dify team.

File-type inputs are not currently supported for MCP services in Dify (v1.11.1). The backend code that converts MCP schemas to tool parameters does not handle or recognize file-type fields, and the UI for MCP tool parameters only renders basic controls for types like string, number, array, and object—there’s no logic for file inputs. As a result, file-type parameters are not surfaced or usable when you import an MCP service or build new workflow apps with it. This is a platform limitation, not a bug in your configuration.

If file uploads are critical to your workflow, you may need to restructure your app to use supported input types or monitor future release notes for updates on file input support.
You can see the relevant backend logic here: convert_mcp_schema_to_parameter.

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 16, 2025): <!-- Greeting --> Hi @Usigned! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> File-type inputs are not currently supported for MCP services in Dify (v1.11.1). The backend code that converts MCP schemas to tool parameters does not handle or recognize file-type fields, and the UI for MCP tool parameters only renders basic controls for types like string, number, array, and object—there’s no logic for file inputs. As a result, file-type parameters are not surfaced or usable when you import an MCP service or build new workflow apps with it. This is a platform limitation, not a bug in your configuration. If file uploads are critical to your workflow, you may need to restructure your app to use supported input types or monitor future release notes for updates on file input support. You can see the relevant backend logic here: [convert_mcp_schema_to_parameter](https://github.com/langgenius/dify/blob/ae4a9040dfd344fa0888a23dfd9813ad25284def/api/services/tools/tools_transform_service.py#L266-L480). <!-- 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/8d13f236-a1a7-4723-af82-92ac65bd55f4?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/8d13f236-a1a7-4723-af82-92ac65bd55f4?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/8d13f236-a1a7-4723-af82-92ac65bd55f4?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/8d13f236-a1a7-4723-af82-92ac65bd55f4?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/8d13f236-a1a7-4723-af82-92ac65bd55f4?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/8d13f236-a1a7-4723-af82-92ac65bd55f4?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/8d13f236-a1a7-4723-af82-92ac65bd55f4?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=File-type%20inputs%20are%20not%20currently%20supported%20for%20MCP%20services%20in%20Dify%20%28v1.11.1%29.%20The%20backend%20code%20that%20converts%20MCP%20schemas%20to%20tool%20parameters%20does%20not%20handle%20or%20recognize%20file-type%20fields%2C%20and%20the%20UI%20for%20MCP%20tool%20parameters%20only%20renders%20basic%20controls%20for%20types%20like%20string%2C%20number%2C%20array%2C%20and%20object%E2%80%94there%E2%80%99s%20no%20logic%20for%20file%20inputs.%20As%20a%20result%2C%20file-type%20parameters%20are%20not%20surfaced%20or%20usable%20when%20you%20import%20an%20MCP%20service%20or%20build%20new%20workflow%20apps%20with%20it.%20This%20is%20a%20platform%20limitation%2C%20not%20a%20bug%20in%20your%20configuration.%20%0A%0AIf%20file%20uploads%20are%20critical%20to%20your%20workflow%2C%20you%20may%20need%20to%20restructure%20your%20app%20to%20use%20supported%20input%20types%20or%20monitor%20future%20release%20notes%20for%20updates%20on%20file%20input%20support.%20%20%0AYou%20can%20see%20the%20relevant%20backend%20logic%20here%3A%20%5Bconvert_mcp_schema_to_parameter%5D%28https%3A//github.com/langgenius/dify/blob/ae4a9040dfd344fa0888a23dfd9813ad25284def/api/services/tools/tools_transform_service.py%23L266-L480%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/29741)
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#21085
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?