Repository navigation
Store MCP names with the saved connection (0.4.18) - #21
Merged
Merged
Conversation
A saved MCP connection held only its release UID and endpoint, so every listing asked the backend twice to label it and a backend restart during a refresh showed "Unnamed MCP"; 0.4.17 only remembered the last name. - Bundle devtools 0.3.1, which resolves the release's name and its repository's name when an MCP is connected, stores them with the connection as name, display_name and code_repository_branch_uid, lists them without a backend request, and completes a record saved by an earlier version on the first listing that can read it - The worker's name adapter labels discovery rows only, from the code_repository_branch_uid each row now carries, and leaves listings alone - The packaged-worker MCP test covers stored names, listing without a backend request, the one-time completion of an old record and denied directory or branch reads - Release notes, README, guide and verification record the live check: the saved CRM connection was completed by the first listing (5.6 s) and listed from the file afterwards (46 ms, no backend request) Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
Why
A saved MCP connection held only its release UID and endpoint, because the release detail read when connecting carries neither a name nor a repository. Every listing therefore asked the backend twice (release directory, then repository branch) to label it, and a backend restarting during a refresh showed Unnamed MCP. 0.4.17 only remembered the last name.
What changes
mcp-addresolves the release's name and its repository's name once and stores them with the connection asname,display_nameandcode_repository_branch_uid;mcp-listreturns them without a backend request and completes a record saved by an earlier version on the first listing that can read it.src/hosts/claudeMcpNames.tslabels discovery rows only, from thecode_repository_branch_uideach row now carries; listings are left as devtools returns them.tests/claude-mcp.test.cjscovers stored names, listing without a backend request, the one-time completion of an old record, and denied directory or branch reads.docs/releases/0.4.18.md; README, guide and verification updated.Verification
npm run release:checkwith devtools 0.3.1 installed from the registry: 97 Node tests, docs, packaging and distribution checks, loader validation on Desktop's bundled Code 2.1.304;npm run verify:claudepasses.Live, against the local backend with the saved CRM connection as 0.4.17 left it (no name in the file): the first
mcp-listcompleted the record (crm·MainSequenceCRMAPI, 5.6 s) and wrote it tomcp-connections.json; the second listed from the file in 46 ms with no backend request;mcp-toolsandmcp-discovercarried the same labels.🤖 Generated with Claude Code