Phase 4: MCP Configuration Module

Implement MCP server configuration merging, writing to harness-specific paths, and tracking configured servers.

Tasks

Task 12: Implement MCP config merger — Create mcp-config-merger.ts to merge NodeSource MCP servers into existing harness config without overwriting user's existing servers. Deep merge mcpServers object. Preserve all non-NodeSource entries.
- Depends on: Task 4
- Files: packages/core/src/mcp/mcp-config-merger.ts
- Testing: Unit tests for merge logic. Test with empty config, existing NodeSource entries (update), existing user entries (preserve), mixed scenario.
Task 13: Implement MCP config writer — Create mcp-config-writer.ts to write MCP configurations to harness-specific paths. Use harness adapter to get config path and format (JSON/TOML). Read existing config, merge, write back atomically.
- Depends on: Tasks 12, 4
- Files: packages/core/src/mcp/mcp-config-writer.ts
- Testing: Unit tests with mocked file system. Test JSON (Claude/OpenCode) and TOML (Codex) formats. Test handling of invalid existing config.
Task 14: Implement MCP tracker module — Create mcp-tracker.ts to record configured MCP servers in tracking file. Store server name, config path, configuration timestamp, and harness (string identifying which harness the MCP was configured for). Support lookup by harness for targeted uninstalls. Handle missing/corrupted tracking file gracefully.
- Depends on: Task 13
- Files: packages/core/src/mcp/mcp-tracker.ts, packages/core/src/mcp/index.ts
- Testing: Unit tests for write/read with harness, lookup by harness, targeted uninstall by harness, missing/corrupted tracking file handling.

🔗 Related PRs

nodesource/ns-benchmark#17 - Cesar/mcp proposal [merged]
nodesource/ncm-mcp#1 - feat: implement ncm mcp server [merged]
nodesource/ncm-mcp#2 - add ncm MCP server infra and pipelines config [merged]
nodesource/ncm-mcp#4 - feat: implement HTTP/SSE transport for NCM MCP Server [merged]
nodesource/ns-benchmark#27 - refactor: split entry points for mcp and workers [merged]

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

Create Plan

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

Navigation Menu

Repository navigation

Phase 4: MCP Configuration Module #16