fix(setup): bump add-mcp to 2.6.1 to fix deep-merge config corruption

GE
10h ago
+6-6

Summary

Fixes #163

setup mcp pinned add-mcp@1.14.0, which suffered from a deep-merge bug when updating an existing server configuration (such as an older stdio-style firecrawl entry in ~/.codex/config.toml). This created an invalid hybrid configuration combining stdio and remote fields (url is not supported for stdio), preventing Codex from initializing chats.

Upstream resolved this issue in add-mcp 2.x (neon-solutions/add-mcp#86) by replacing existing server entries atomically instead of deep-merging them. Bumping the pin to add-mcp@2.6.1 brings this fix to Firecrawl CLI users while maintaining an exact version pin for supply-chain reproducibility.

Changes

  • src/commands/setup.ts: Bump ADD_MCP_PACKAGE from add-mcp@1.14.0 to add-mcp@2.6.1.
  • src/__tests__/commands/setup.test.ts: Update test expectations to assert add-mcp@2.6.1.

Tests

  • pnpm run type-check: TypeScript type check passed cleanly with 0 errors (tsc --noEmit).
  • npx vitest run src/__tests__/commands/setup.test.ts: All 97 setup unit tests passed.
  • pnpm run test: Entire test suite passed (51 test files passed, 2 skipped, 925 tests passed).
  • pnpm run build: Build succeeded cleanly (tsc).

Summary by cubic

Bumps add-mcp in setup mcp from 1.14.0 to 2.6.1 to fix a deep-merge bug that corrupted existing server configurations, such as older stdio-style firecrawl entries, by creating an invalid hybrid of stdio and remote fields that prevented Codex from initializing chats. Upstream fixed this by replacing server entries atomically instead of deep-merging. Test expectations are updated to assert the new pin.