find_agent_tool — Forage Tool Resolver MCP Tool Read-only
find_agent_tool
(find agent tool) is one of 1 tool on the
Forage Tool Resolver
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call find_agent_tool from your client
- Claude Code Forage Tool Resolver find_agent_tool run in your project directory
- Claude Desktop Forage Tool Resolver find_agent_tool ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Forage Tool Resolver find_agent_tool ~/.cursor/mcp.json
- VS Code Forage Tool Resolver find_agent_tool .vscode/mcp.json
- Zed Forage Tool Resolver find_agent_tool ~/.config/zed/settings.json
- Windsurf Forage Tool Resolver find_agent_tool ~/.codeium/windsurf/mcp_config.json
- Cline Forage Tool Resolver find_agent_tool ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Forage Tool Resolver find_agent_tool ~/.gemini/settings.json
- Grok Forage Tool Resolver find_agent_tool .mcp.json (in your project root)
- ChatGPT Forage Tool Resolver find_agent_tool Settings → Connectors → Advanced → Developer mode
- Claude.ai Forage Tool Resolver find_agent_tool Settings → Connectors → Add custom connector
- LangChain Forage Tool Resolver find_agent_tool pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http find-agent-tool https://forage.inflbs.xyz/find
This list was read from the server itself, by connecting to it and calling tools/list on 6 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.