[BUG] Plugin marketplace UI shows plugins as disabled but their tools remain available
Preflight Checklist
- [x] I have searched existing issues
- [x] I am filing a single bug report
- [x] I am using the latest version of Claude Code
What's Wrong?
The /plugin command UI shows plugins as disabled (◯) but their tools and skills remain available in the session. Tools prefixed with mcp__plugin_<name>_ and skills prefixed with <plugin-name>: are accessible despite their parent plugins being shown as disabled in the /plugin interface.
Note: Claude Code was restarted after disabling these plugins, but their tools still remain available to the agent.
What Should Happen?
When a plugin is shown as disabled in the /plugin UI (◯), its associated tools and skills should not be available in the Claude Code session. Only enabled plugins (◉) should have their functionality accessible. Restarting Claude Code should respect the disabled state and remove those tools from the session context.
Steps to Reproduce
- Install plugins from a marketplace
- Enable some plugins via the
/pluginUI - Restart Claude Code completely
- Disable those same plugins via the plugin UI (they should show as ◯)
- Restart Claude Code completely
- Run
/plugincommand - verify plugins show as disabled (◯) - Ask Claude to list available tools or check which tools are available
- Observe that tools prefixed with
mcp__plugin_<disabled-plugin-name>_are still available - These tools are functional despite their parent plugins being shown as disabled
Claude Model
Sonnet 4.5 (claude-sonnet-4-5-20250929)
Is This a Regression?
Unknown - not sure if this ever worked correctly
Claude Code Version
2.0.24 (Claude Code)Platform
Anthropic API
Operating System
Linux (Fedora 41 - Linux 6.16.7-100.fc41.x86_64)
Terminal/Shell
bash (/usr/bin/bash)
Error Messages/Logs
N/A - No error messages, the tools simply remain available despite UI showing plugins as disabled.
Additional Information
This issue affects plugin marketplace installations. The plugin UI state (enabled ◉ vs disabled ◯) does not match the actual runtime availability of plugin tools and skills.
Tool naming confirms they come from the plugins (e.g., mcp__plugin_<name>_* pattern for MCP tools, <plugin-name>:<skill> pattern for skills).
This appears related to issue #6320 (Denied MCP tools have their tool prompt in the context) and #8888 (MCP server disabled config not being respected), but specifically affects the plugin marketplace UI state vs. runtime state.
10 Comments
Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
I've encountered this problem too, but it's not related to MCP servers. I've also found that with this same issue it affects the uninstall of plugins too. So you uninstall a plugin, interface tells you too apply, and then restart CC to complete the uninstall, but then when you do that and return, the plugin is still there. Worse still, is that if an update to the plugin is subsequently published, you can't install the update either.
I believe the reason is that uninstalling or disabling the plugin is not removing it from your user .claude/settings.json file. I've noticed this as well - requires manual deletion from the plugins section.
I've noticed a similar problem too. I've configured a Marketplace with a single plugin that should only be loading the 'skills' directory - but it's loading all the commands and namespacing it under the skills plugin. In other words, it's loading too much.
Yeah, same problem here. Defeats one of the advantages that I was hoping to get with plugins. =/
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
Still an issue for some plugins. Depends on correct plugin configuration.
I'm seeing this with the Sentry plugin
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
This issue was closed incorrectly despite recent human comments. This behavior of the bot is reported at https://github.com/anthropics/claude-code/issues/16497. Please upvote that issue, so maybe it gets noticed.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.