mcp_indexer_server: fix: make repo_search tolerant of mcp-remote args schema#35
Merged
voarsh2 merged 1 commit intoContext-Engine-AI:testfrom Nov 27, 2025
Conversation
m1rl0k
pushed a commit
that referenced
this pull request
Mar 1, 2026
…-mcp-remote-args-schema mcp_indexer_server: fix: make repo_search tolerant of mcp-remote args schema
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.
The qdrant-indexer MCP server was emitting a flat schema for repo_search
(query, limit, include_snippet, collection, etc.), but the Windsurf/Claude
qdrant-indexer integration (via mcp-remote) was still modeling this tool as
taking {args, kwargs}. This mismatch surfaced as:
To make repo_search compatible with both direct FastMCP clients and the
mcp-remote wrapper, we:
a no-op "compatibility shim" for clients that insist on sending args/kwargs.
direct callers and internal wrappers keep working as before.
Net effect:
convention without breaking direct FastMCP usage.