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

[PR #30955] refactor(web): MCP tool availability to context-based version gating #33034

New Issue
Closed
opened 2026-02-21 20:52:32 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:52:32 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/30955

State: closed
Merged: Yes

Background

MCP tool availability was computed in the Agent node and passed through multiple layers via canChooseMCPTool. This made the gating logic hard to trace and required frequent prop plumbing changes. We want a single source of truth that can be adjusted later without touching the entire selector tree.

Changes

  • Add MCPToolAvailabilityProvider and useMCPToolAvailability to centralize MCP availability.
  • Remove canChooseMCPTool prop drilling across tool selector / block selector / agent strategy components.
  • Default to allowing MCP tools when no provider is present; only wrap with provider where version-based gating is needed (Agent node panel).
  • Simplify MCP tooltip to a version unsupported message.
  • Update MultipleToolSelector tests to use the provider.

Testing

  • pnpm lint:fix --quiet
  • pnpm type-check:tsgo
**Original Pull Request:** https://github.com/langgenius/dify/pull/30955 **State:** closed **Merged:** Yes --- ## Background MCP tool availability was computed in the Agent node and passed through multiple layers via `canChooseMCPTool`. This made the gating logic hard to trace and required frequent prop plumbing changes. We want a single source of truth that can be adjusted later without touching the entire selector tree. ## Changes - Add `MCPToolAvailabilityProvider` and `useMCPToolAvailability` to centralize MCP availability. - Remove `canChooseMCPTool` prop drilling across tool selector / block selector / agent strategy components. - Default to allowing MCP tools when no provider is present; only wrap with provider where version-based gating is needed (Agent node panel). - Simplify MCP tooltip to a version unsupported message. - Update MultipleToolSelector tests to use the provider. ## Testing - pnpm lint:fix --quiet - pnpm type-check:tsgo
yindo added the pull-request label 2026-02-21 20:52:32 -05:00
yindo closed this issue 2026-02-21 20:52:32 -05:00
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 pull-request
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#33034
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?