Repository navigation
feat: add standalone mcp-use docs reader - #48
Merged
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.
Adds a standalone Node.js entry that lists the docs MCP tools, searches for quickstart, and prints the returned page. Run it from
examples/mcp-use-docswithnpm ci --ignore-scriptsandnpm start; no model, account or API key is needed. English and Chinese instructions and the agent routing table point to the same entry.The example pins
@mcp-use/client2.4.5 with its lockfile, requires Node.js 22.22.2+, disables SDK telemetry before import, closes the client on either outcome, and stops on tool errors or empty results. QA tagging is opt-in for internal runs.Validation: dependency installation and syntax check passed on Node.js 26.8.1. A bounded QA run completed four documentation requests (all HTTP 200), searched and read the returned quickstart page, and printed its full 44,959-character Markdown. No telemetry request was attempted; no model, chain RPC, account or key was used. This is client compatibility QA, not external adoption or a model-driven workflow. The existing localStorage warning is retained in the saved stderr.