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

installed plugin can't be used #15255

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

Originally created by @steven0081 on GitHub (Jul 10, 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 search for existing issues, 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.6

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

i have installed plugin "mcp_see_agent" from marketplace, and it is show in plugin tab,but it can't show in tools tab, and it can't be used in agent.

✔️ Expected Behavior

what should i do?

❌ Actual Behavior

No response

Originally created by @steven0081 on GitHub (Jul 10, 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 [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 (我已阅读并同意 [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.6 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce i have installed plugin "mcp_see_agent" from marketplace, and it is show in plugin tab,but it can't show in tools tab, and it can't be used in agent. ### ✔️ Expected Behavior what should i do? ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:20:54 -05:00
yindo closed this issue 2026-02-21 19:20:55 -05:00
yindo commented 2026-02-21 19:20:55 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 10, 2025):

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

The most common cause for a plugin like "mcp_see_agent" not appearing in the tools tab or being usable in the agent (especially in Docker/self-hosted setups) is a missing or misconfigured environment variable. Make sure your .env or Docker Compose environment includes:

INNER_API_KEY_FOR_PLUGIN=QaHbTe77CtuXmsfyhR7+vRjI/+XbV1AaFy691iy+kGDv2Jvy0/eAh8Y1
PLUGIN_DIFY_INNER_API_URL=http://api:5001
PLUGIN_DIFY_INNER_API_KEY=QaHbTe77CtuXmsfyhR7+vRjI/+XbV1AaFy691iy+kGDv2Jvy0/eAh8Y1

Do not use localhost or 127.0.0.1 for internal URLs in Docker—use the service name (like api) or host.docker.internal if needed. After updating these, restart the plugin daemon container with:

docker restart docker-plugin_daemon-1

If the plugin still doesn't show up, check that the plugin manifest is complete and correctly formatted, and that your installation scope/permissions allow marketplace plugins. Sometimes clearing custom values in your Docker .env (like POSITION_TOOL_PINS, POSITION_TOOL_INCLUDES, etc.) can help if you have them set. If you still have trouble, check the plugin installation logs for errors or incomplete states.

For more details, see this issue and this troubleshooting guide.

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 (Jul 10, 2025): <!-- Greeting --> Hi @steven0081! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> The most common cause for a plugin like "mcp_see_agent" not appearing in the tools tab or being usable in the agent (especially in Docker/self-hosted setups) is a missing or misconfigured environment variable. Make sure your `.env` or Docker Compose environment includes: ``` INNER_API_KEY_FOR_PLUGIN=QaHbTe77CtuXmsfyhR7+vRjI/+XbV1AaFy691iy+kGDv2Jvy0/eAh8Y1 PLUGIN_DIFY_INNER_API_URL=http://api:5001 PLUGIN_DIFY_INNER_API_KEY=QaHbTe77CtuXmsfyhR7+vRjI/+XbV1AaFy691iy+kGDv2Jvy0/eAh8Y1 ``` Do not use `localhost` or `127.0.0.1` for internal URLs in Docker—use the service name (like `api`) or `host.docker.internal` if needed. After updating these, restart the plugin daemon container with: ``` docker restart docker-plugin_daemon-1 ``` If the plugin still doesn't show up, check that the plugin manifest is complete and correctly formatted, and that your installation scope/permissions allow marketplace plugins. Sometimes clearing custom values in your Docker `.env` (like `POSITION_TOOL_PINS`, `POSITION_TOOL_INCLUDES`, etc.) can help if you have them set. If you still have trouble, check the plugin installation logs for errors or incomplete states. For more details, see [this issue](https://github.com/langgenius/dify/issues/18085) and [this troubleshooting guide](https://github.com/langgenius/dify/issues/21313). <!-- 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/1484ca19-9d46-409a-9906-40eee2372ac0?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/1484ca19-9d46-409a-9906-40eee2372ac0?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/1484ca19-9d46-409a-9906-40eee2372ac0?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/1484ca19-9d46-409a-9906-40eee2372ac0?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/1484ca19-9d46-409a-9906-40eee2372ac0?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/1484ca19-9d46-409a-9906-40eee2372ac0?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/1484ca19-9d46-409a-9906-40eee2372ac0?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/issues/22187)
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#15255
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?