Repository navigation
[Docs] Explain custom MCP tool-list recovery - #3451
Draft
roomote-community[bot] wants to merge 1 commit into
Draft
roomote-community[bot] wants to merge 1 commit into
roomote-community[bot] wants to merge 1 commit into
Conversation
Contributor
Author
2 tasks done
This branch has not been deployed
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.
Related issue
Daily documentation accuracy audit; follows the merged tool-catalog recovery change in #3441. No separate issue.
Why this PR exists
The audit of the 10 PRs merged between 2026-10-09T03:00:45.894Z and 2026-10-10T03:00:45.894Z found that custom MCP tool-list recovery lacked troubleshooting guidance. Existing open documentation PRs do not cover this gap. All 10 merges target develop and postdate the latest release, v1.17.0; this documentation follows develop's implementation, rather than claiming the retry control exists in v1.17.0.
What changed
Explain how to retry a failed remote custom MCP tool-list load from the same Manage tools dialog, including the visible error, disabled retry button during a request, and restored list after success.
The guidance matches
CustomToolManagementDialoginapps/web/src/components/settings/CustomMcpServers.tsxand its existing recovery tests. Readers can recover a failed catalog load without recreating their server connection. No application behavior changes.How it was tested
mise exec -- pnpm --filter @roomote/docs check: Mintlify build validation and broken-link checks passed.mise exec -- pnpm --filter @roomote/docs check-cookbook-index: all seven recipes are current.git diff --check: passed; the final diff contains only the intended seven-line docs addition.Checklist
[Fix],[Feat],[Improve],[Refactor],[Docs], or[Chore]followed by a user-facing descriptionpnpm lintandpnpm check-typespass locallypnpm changesetThe normal fast pre-push static gates passed as listed above; the formatting-inclusive lint/typecheck commands were not separately run. A changeset is not needed for this public-docs-only correction.