Feature Request: Fallback Support for Root-Level .mcp.json Configuration

[HadesArchitect]

Origin: https://discord.com/channels/1349288496988160052/1349358609678598277/1377967872378404964

Summary

Add support for .mcp.json configuration file in the project root directory as a fallback when .kilocode/mcp.json is not available.

Background

Currently, Kilocode looks for MCP (Model Context Protocol) configuration exclusively in .kilocode/mcp.json. Other tools like Zed editor use .mcp.json in the project root directory. This creates a compatibility issue when switching between editors or when teams use different tools.

Proposed Solution

Implement a fallback mechanism that:

1. First checks for .kilocode/mcp.json (current behavior)
2. If not found, checks for .mcp.json in the project root
3. Uses the root .mcp.json configuration if available

Benefits

• Cross-editor compatibility: Projects can share MCP configurations between Kilocode and other editors like Zed
• Reduced configuration duplication: Teams don't need to maintain separate MCP configs for different tools
• Easier onboarding: New users coming from other editors can use their existing MCP configurations
• Backwards compatibility: Existing Kilocode projects continue to work unchanged

Implementation Notes

• Priority should be given to .kilocode/mcp.json to maintain current behavior
• Only use root .mcp.json as a fallback when Kilocode-specific config is not present
• Consider logging when using the fallback to help with debugging

Example Use Case

A developer working on a project that already has .mcp.json configured for Zed can immediately start using Kilocode without needing to duplicate their MCP server configurations.

[HadesArchitect]

Taken by @seuros :)

[HadesArchitect]

Closed in #554