fix(mcp): deconflict local and remote MCP servers#23
Merged
Conversation
…deploys
Rename remote MCP server from "jack" to "jack-cloud" and rename file
tools to clearly signal they're for terminal-less environments only:
- update_file → stage_file
- list_staged_changes → list_staged_files
- list_project_files → browse_deployed_source
- read_project_file → read_deployed_file
Tool descriptions now include negative guidance ("if you have
Read/Edit/Write tools, use those instead") to prevent agents from
using remote file staging when local filesystem access is available.
Add dual-connection detection to jack mcp install — automatically
removes remote MCP configs that conflict with the local server.
Narrow CLAUDE.md and agents://context guidance from blanket "always
prefer MCP tools" to "prefer MCP for cloud operations, use built-in
tools for file editing."
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
1 participant
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
"jack"to"jack-cloud"so tools are clearly namespaced (mcp__jack__*vsmcp__jack_cloud__*)stage_file,list_staged_files,browse_deployed_source,read_deployed_filejack mcp install— auto-removes remote MCP configs that conflict with localProblem
When both local (stdio) and remote (HTTP) Jack MCP servers are connected in Claude Code, agents use remote file tools (
update_file,read_project_file) instead of built-in filesystem tools, causing partial deploys:Tracked in #22.
Changes
apps/mcp-worker/src/server.tsapps/mcp-worker/src/tools/source.tsapps/mcp-worker/src/tools/deploy-code.tsapps/mcp-worker/src/staging.tsapps/mcp-worker/CLAUDE.mdapps/cli/src/lib/mcp-config.tsapps/cli/src/mcp/resources/index.tsapps/cli/src/commands/mcp.tsCLAUDE.mdTest plan
stage_file,browse_deployed_source, etc.stage_file+deploy(staged=true)workflow still worksjack mcp installwith a remote MCP entry in~/.claude.jsonand verify it gets removed with warning