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

[PR #31764] fix!: modify console API /workspaces/current/tools/mcp to return provider ID #33390

New Issue
Open
opened 2026-02-21 20:53:12 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:53:12 -05:00
Owner
Copy Link
Copy Source

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

State: open
Merged: No

Summary

Fixes #31763

The id field in each MCP server entry from /console/api/workspaces/current/tools/mcp API should be the provider ID.

Currently the id and server_identifier fields are effectively duplicated.
We have no way of obtaining the provider ID without removing and re-adding MCP servers.
As such we cannot easily make use of related APIs that requires provider ID as argument.

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran make lint and make type-check (backend) and cd web && npx lint-staged (frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/31764 **State:** open **Merged:** No --- ## Summary Fixes #31763 The `id` field in each MCP server entry from `/console/api/workspaces/current/tools/mcp` API should be the provider ID. Currently the `id` and `server_identifier` fields are effectively duplicated. We have no way of obtaining the provider ID without removing and re-adding MCP servers. As such we cannot easily make use of related APIs that requires provider ID as argument. ## Checklist - ~This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs)~ - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [x] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [x] I've updated the documentation accordingly. - [x] I ran `make lint` and `make type-check` (backend) and `cd web && npx lint-staged` (frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:53:12 -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#33390
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?