Repository navigation
v1.5.1 - Improved MCP Discovery for Ecosystem-Aware Workflows
v1.5.1 - Improved MCP Discovery
Enhanced set_workspace_info Tool - Supporting v1.5.0 MCP-aware workflows
Key Improvements
- Made available_mcps Required: Changed from optional to required parameter to ensure agents provide MCP ecosystem context
- Tool Signature Mapping: Added MCP_TOOL_SIGNATURES constant mapping 42 signature tools to 7 BC MCP servers
- Automatic Discovery Instructions: Updated tool description with explicit guidance on inferring MCP servers from available tools:
- If \search_telemetry_traces\ exists bc-telemetry-buddy is available
- If
eserve_object_ids\ exists al-objid-mcp-server is available - If \�nalyze_dependencies\ exists al-dependency-mcp-server is available
- If \get_lsp_diagnostics\ exists serena-mcp is available
- If \create_work_item\ exists azure-devops-mcp is available
- If \ rack_time_entry\ exists clockify-mcp is available
- If \ ranslate_xliff\ exists nab-al-tools-mcp is available
- Updated Intercept Message: Changed workspace configuration prompt from 'Optional' to 'REQUIRED' with discovery instructions
- Consistent Logging: Fixed server logs to reference \set_workspace_info\ instead of legacy \set_workspace_root\
Why This Matters
- Agents can't see which MCP servers are connected (MCP protocol limitation)
- Agents CAN list available tools in their context
- Tool signature matching enables automatic MCP ecosystem discovery
- Specialists can now provide ecosystem-aware recommendations and tool delegation
- Prevents agents from skipping MCP ecosystem information
Migration
All \set_workspace_info\ calls now require the \�vailable_mcps\ parameter (can be empty array []):
\\ ypescript
// Before (v1.5.0):
set_workspace_info({ workspace_root: 'C:/project/path' })
// After (v1.5.1):
set_workspace_info({
workspace_root: 'C:/project/path',
available_mcps: [] // Or discover via tools: ['bc-telemetry-buddy', 'al-objid-mcp-server']
})
\\
v1.5.0 - Workspace Management Tools (Released Earlier Today)
New Tools
- set_workspace_info - Configure workspace root and MCP ecosystem context
- get_workspace_info - Query currently configured workspace and available MCPs
Major Features
- Lazy Initialization: Server starts with only embedded knowledge, defers project/company layers until workspace is set
- First-Call Interception: Tools provide helpful guidance to set workspace before allowing operations
- VS Code Workaround: Solves VS Code bug #245905 (\\ doesn't work in user-level MCP settings)
- Automatic Reload: Setting workspace triggers full config reload with project-local layers
- MCP Ecosystem Awareness: Track available BC MCP servers for conditional knowledge loading
Why This Was Needed
- MCP servers launched by VS Code extension run from user home/npm cache, not workspace folder
- Config file discovery (\�ckb-config.yml) and project layers (./bc-code-intel-overrides) failed
- No standard MCP protocol for workspace context passing
- Lazy initialization prevents startup failures while maintaining zero-config embedded knowledge
- Specialists need to know what other BC tools are available for delegation and integration
Universal Content Type Support - ALL Layers
- Breaking Architecture Fix: ALL layers (embedded, git, project) now support all three content types
- Topics (domains/) - BC knowledge articles
- Specialists (specialists/) - AI persona definitions
- Methodologies (methodologies/) - Systematic workflows
- Git Layer: Now loads from \domains/, \specialists/, and \methodologies/\ subdirectories
- Project Layer: Enhanced to support all content types for local overrides
- Consistent Interface: All layers implement \getContentIds(), \getContent(), \hasContent(), \searchContent()\
Installation
\\�ash
npm install -g bc-code-intelligence-mcp@1.5.1
\\
Full Changelog
See CHANGELOG.md for complete details.