Test: enabling/disabling plugins and MCP servers in AH contexts

[connor4312]

• anyOS Aiday Marlen Kyzy (@aiday-mar)
• anyOS Vijay Upadya (@vijayupadya)

Complexity: 4

Authors: Connor Peet (@connor4312)

Create Issue

---

Recently we've fixed a bunch of things around MCP servers and plugin enablements in the agent host.

Install:

• A standalone MCP server (e.g. in VS Code settings)
• A plugin that provides a skill
• A plugin that provides an MCP server

Then please verify:

• The MCP server provided by the plugin cannot independently be enabled or disabled in the customizations view; it instead just links to the plugin.
• For both all three things:
  • The global "Disable" action works for each of them. (Can ask the agent if it has access to the skill or a specific tool from the MCP server)
  • The "Disable (Workspace)" action works for each of them, disabling the thing in a particular folder but still having it enabled in other folders
  • Similarly globally disabled + "Enable (Workspace)" turns on for the specific folder
  • Disabling and enabling in a per-session context works as you would expect

[aiday-mar]

The MCP server provided by the plugin cannot independently be enabled or disabled in the customizations view; it instead just links to the plugin.

I seem to be able to disable and enable the MCP server provided by the plugin from the customization view?