feat(mcp): support project-local configuration - #59
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds automatic project-local
.mcp.jsondiscovery and merges it with configured MCP servers. The merged configuration reloads dynamically and is preserved across built-in Kit child processes.Motivation
Projects can check in their MCP development setup without requiring each user to copy those servers into global Kit configuration or replace their existing configured servers.
Impact
Kit now reads
.mcp.jsonfrom the effective project root forserve,acp,prompt, andtui. Server definitions use whole-server precedence: plugins, configured MCP file, project.mcp.json, then--mcp-config.Project-local stdio servers resolve missing or relative
cwdvalues from the.mcp.jsondirectory. Kit also accepts compatible optionaltypediscriminators used by common MCP configuration formats.Technical details
Layered reloads
Each source is tracked independently. Creating, editing, or deleting the optional project file updates only effectively changed servers, while invalid changes preserve the last valid runtime state.
Child compatibility
Built-in
acp.kitchildren inherit configured and explicit paths separately and rediscover the same project layer. The existing publicRuntime::with_mcp_configAPI retains its legacy single-file behavior.