MCP search_tool/use_tool cannot call tools that grok mcp doctor already listed (100+ tool stdio server)
Product: Grok Build TUI/CLI
Version: grok 1.0.13 (5e9a58528b76) [stable]
OS: Windows 11
Docs: user-guide 07-mcp-servers.md "Tool Discovery" (search_tool by name/description, then use_tool with fully-qualified server__tool names)
Setup
- One stdio MCP server in ~/.grok/config.toml (native [mcp_servers.*], not Claude-compat for this server).
- Server implements standard MCP tools/list and returns ~113 tools, many namespaced with double underscores (e.g. backend__action).
- Same MCP server is used successfully from other coding agents that inject the full tools/list into the model.
What works
- grok mcp doctor : command found, server started, handshake OK, "113 tools discovered", healthy.
- /mcps shows the server connected.
- A small subset of that server's tools (~12) are injected into the model context and those calls succeed.
What fails
- TUI and headless (grok --prompt-file) both expose search_tool/use_tool instead of the full tools/list.
- search_tool reports ~81 "hidden" tools, but queries for exact names that exist on the server (including the namespaced ones) return no matches. Querying the backend/family name also returns empty or only the 12 already-injected tools.
- use_tool with the fully-qualified name (server__tool) returns: Tool not found.
- Headless runs hit max-turns without ever invoking the MCP tool, even with --yolo / bypassPermissions.
- Arithmetic: 12 in-context + 81 hidden = 93, vs 113 from doctor. The missing slice is real tools on the wire, not a disconnected server.
Expected
- search_tool finds every tool from tools/list by exact name and by description, as documented.
- use_tool can invoke those fully-qualified names after discovery.
- A single stdio MCP server with 100+ namespaced tools should be fully usable. Splitting one gateway into many MCP servers should not be required.
Request
- Fix search_tool indexing so exact names from tools/list are findable (including names with "__").
- Please treat this as a blocker for teams that use one MCP gateway (common pattern). Other agents already consume the same tools/list completely.
- Optional: a documented config to inject the full tools/list (Claude/Codex-style) for large MCP servers, in addition to deferred search.
Happy to attach grok mcp doctor --json (redacted) and a debug-file from a failing search_tool turn.
MCP search_tool/use_tool cannot call tools that grok mcp doctor already listed (100+ tool stdio server)
Product: Grok Build TUI/CLI
Version: grok 1.0.13 (5e9a58528b76) [stable]
OS: Windows 11
Docs: user-guide 07-mcp-servers.md "Tool Discovery" (search_tool by name/description, then use_tool with fully-qualified server__tool names)
Setup
What works
What fails
Expected
Request
Happy to attach grok mcp doctor --json (redacted) and a debug-file from a failing search_tool turn.