docs(mcp): document code_outline / code_search / code_expand from #2146#2176
Merged
qin-ctx merged 2 commits intoMay 22, 2026
Merged
Conversation
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
PR Code Suggestions ✨No code suggestions found for the PR. |
qin-ctx
approved these changes
May 22, 2026
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
2 participants
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
Updates the Available MCP Tools table in
docs/{en,zh}/guides/06-mcp-integration.mdto reflect the three new MCP tools added by #2146 (code_outline/code_search/code_expand). Pre-#2146 the table claimed "11 tools" and listed 11 rows; after #2146 the MCP endpoint exposes the three additional code-navigation tools atopenviking/server/mcp_endpoint.pyL840 / L864 / L914. The client-facing setup guide users land on for tool discovery is now stale by three rows and a count.Why this matters
The integration guide is where MCP clients (Claude / Manus / OpenClaw / VikingBot) discover what tools the endpoint actually exposes. Without these three rows agents miss the
code_search → code_outline → code_expandworkflow this PR was specifically designed to enable; users have to readopenviking/server/mcp_endpoint.pyto find out the tools exist.Same form as #2134 (
list_watches+cancel_watchcatch of #2110) — narrow scope, dual-doc parity, no semantic change to the prose around the table.Changes
docs/.../guides/06-mcp-integration.md: count11→14; insert 3 rows betweenforgetandhealthmatching source-file order inmcp_endpoint.py.code_outline(uri)— file URI, returns symbol structure without bodies.code_search(query, uri)— directory URI, scans up to 200 source files, narrow uri for deeper coverage.code_expand(uri, symbol)— file URI,symbolacceptsbar(top-level) orFoo.bar(method).12 LOC (6 EN + 6 ZH — 3 row inserts + count edits, each side).