codebuddy-ide-mcp-upgrade

Upgrade the CloudBase MCP bundle and tool whitelist embedded in CodeBuddy IDE.

1.1k|138|Updated May 23, 2025
One-click install
npx skills add https://github.com/TencentCloudBase/CloudBase-AI-Toolkit --skill codebuddy-ide-mcp-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebuddy-ide-mcp-upgrade
Source: https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/skills/codebuddy-ide-mcp-upgrade
Command: npx skills add https://github.com/TencentCloudBase/CloudBase-AI-Toolkit --skill codebuddy-ide-mcp-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires marked, and includes scripts (resource) components.

What problem does it solve?

The CloudBase MCP bundled inside CodeBuddy IDE (via the genie extension) drifts out of date: the IDE-side tool whitelist keeps stale entries for renamed or removed MCP tools, so users see degraded CloudBase functionality even after new MCP releases. This Skill provides the full procedure to unpack the IDE's embedded configuration, rebuild the MCP bundle, regenerate the whitelist and prompts, inject them safely, verify, and roll back.

Core Features & Use Cases

  • Unpack and diff the embedded config: Locate the tcb integration block inside the 21MB webpack bundle using the "id":"tcb" anchor, eval-parse the JSON string, and compare the live whitelist against the repository's tools.json source of truth.
  • Rebuild and inject safely: Build the new MCP bundle with webpack, generate a full toolWhiteList plus system/user prompts, apply changes with dry-run and timestamped backups, and patch the toolTimeout defect.
  • Verify and roll back: Re-read the IDE config field-by-field, launch the bundle exactly as the IDE does to compare tools/list, run node --check syntax validation, and restore from backup with one command.
  • Use Case: After an MCP release renames tools, run this Skill to regenerate the IDE whitelist, inject the new bundle into CodeBuddy, and confirm via end-to-end acceptance tests that agents now call the new tool names.

Quick Start

Ask the AI to upgrade the CloudBase MCP bundled inside CodeBuddy IDE and regenerate the tool whitelist from the latest MCP release.

Frequently Asked Questions about codebuddy-ide-mcp-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade the CloudBase MCP bundled inside CodeBuddy IDE?

Unpack the embedded tcb config from the genie extension's index.js, rebuild the MCP bundle with npm run build:webpack, regenerate the toolWhiteList from scripts/tools.json, then inject with the apply script using dry-run first and verify with the bundle and config verification scripts.

Why does CodeBuddy IDE show outdated CloudBase tools after an MCP release?

The IDE filters tools through its own toolWhiteList, which is not updated when the MCP bundle changes. Stale whitelist entries referencing renamed or removed tools silently block new functionality, so the whitelist must be regenerated on every MCP release.

Should the CodeBuddy tool whitelist be trimmed to save context?

No. CodeBuddy supports Tool Search and deferred loading, so the whitelist no longer needs to save context. Generate it in full from tools.json; extra entries are silently skipped and cause no errors.

Why does the IDE config verify as valid JSON but the extension still breaks?

JSON field comparison can pass even when the surrounding JavaScript is corrupted, such as a duplicated JSON.parse prefix closing the string early. Always run node --check or a vm.Script compile on the entire file and roll back on failure.

Why do long-running CloudBase operations time out at 60 seconds in CodeBuddy?

The TcbIntegration config never passes toolTimeout to the MCP SDK, so the default 60000ms applies regardless of the configured value. The patch script adds the missing field and raises the timeout to 300000ms.