Repository navigation
Agent have hard time recognizing MCP via executor #1966
Description
I may use executor wrong, however the agents have a hard time recognize connected MCPs. When I instruct it to use certain MCP it says it has none. Only after I specify that MCP is available via executor MCP, the actor pick it up. Do you think it is solvable?
this is claude response:
Activity
baggiiiie commentedon Sep 8, 2026
hey @krzyzanowskim , you can try to add
search_tools=trueto the mcp URL param , this exposes tools registered in executor to the harness directlyStreamlinedStartup commentedon Sep 10, 2026
@baggiiiie I take it that also adds ALL tools for that person/workspace, as well as adds tool names (your screenshot) + tool descriptions i.e., token eat up?
baggiiiie commentedon Sep 10, 2026
@StreamlinedStartup this depends on how your harness of choice implements its mcp client logic.
the problem @krzyzanowskim was facing was probably due to the harness deferring the mcp tool descriptions, most likely harness defers executor mcp description, while executor defers connection tools. therefor agent is having a hard time finding connections
harnesses and executor are doing this to avoid the exact token eating problem you described
two options are:
hope this answers your question!
RhysSullivan commentedon Oct 8, 2026
We're clearing the backlog ahead of the v2 launch, so we're closing this. If it still applies to v2, please open a new issue or PR against v2.
Sent from my Claude