Skip to content

mcp_indexer_server: fix: make repo_search tolerant of mcp-remote args schema#35

Merged
voarsh2 merged 1 commit intoContext-Engine-AI:testfrom
voarsh2:fix--make-repo_search-tolerant-of-mcp-remote-args-schema
Nov 27, 2025
Merged

mcp_indexer_server: fix: make repo_search tolerant of mcp-remote args schema#35
voarsh2 merged 1 commit intoContext-Engine-AI:testfrom
voarsh2:fix--make-repo_search-tolerant-of-mcp-remote-args-schema

Conversation

@voarsh2
Copy link
Contributor

@voarsh2 voarsh2 commented Nov 27, 2025

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:

  • Client: repo_searchArguments.args is required
  • Server: repo_search() got an unexpected keyword argument 'args'

To make repo_search compatible with both direct FastMCP clients and the
mcp-remote wrapper, we:

  • Added an optional args: Any = None parameter to repo_search, treated as
    a no-op "compatibility shim" for clients that insist on sending args/kwargs.
  • Left all existing named parameters and kwargs handling unchanged so
    direct callers and internal wrappers keep working as before.

Net effect:

  • repo_search now tolerates the mcp-remote/Claude {args, kwargs} calling
    convention without breaking direct FastMCP usage.

@voarsh2 voarsh2 merged commit e87748b into Context-Engine-AI:test Nov 27, 2025
1 check passed
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants