Skip to content

fix(plugins): keep catalog description after an MCP plugin is installed#263

Open
whitelonng wants to merge 1 commit into
KunAgent:developfrom
whitelonng:fix/plugin-desc-after-install
Open

fix(plugins): keep catalog description after an MCP plugin is installed#263
whitelonng wants to merge 1 commit into
KunAgent:developfrom
whitelonng:fix/plugin-desc-after-install

Conversation

@whitelonng

Copy link
Copy Markdown
Contributor

Summary

  • Fixes [Feature] 插件添加后就看不到介绍 #211: after installing/configuring a recommended MCP plugin, its description was replaced by the raw runtime status string (e.g. status: connected · stdio · github-mcp · 12 tools), so the human-readable intro disappeared.
  • mcpMarketplaceItemsFromConfigAndDiagnostics now keeps the catalog descriptionKey/description for known servers and exposes the runtime status/command as a secondary detail line instead of overwriting the description.
  • The marketplace card renders the detail line under the description only when it differs, so unknown/custom servers are unchanged.

Test plan

  • npx vitest run src/renderer/src/components/PluginMarketplaceView.test.ts (7 passed)
  • npx tsc --noEmit -p tsconfig.web.json
  • Manual: add the GitHub MCP plugin from the marketplace and confirm its description stays after install, with the status shown as a smaller detail line.

Installed/configured MCP servers were rendered with their raw status
string as the description, so a recommended plugin lost its
human-readable intro the moment it was added (KunAgent#211). Preserve the
catalog description (or descriptionKey) for known servers and surface
the runtime status/command as a secondary detail line instead.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant