find_tool — Tools That Don't Upload MCP Prompt
find_tool
is one of 2 prompts on the
Tools That Don't Upload
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke find_tool from your client
- Claude Code Tools That Don't Upload Prompt/find_tool run in your project directory
- Claude Desktop Tools That Don't Upload Prompt/find_tool ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Tools That Don't Upload Prompt/find_tool ~/.cursor/mcp.json
- VS Code Tools That Don't Upload Prompt/find_tool .vscode/mcp.json
- Zed Tools That Don't Upload Prompt/find_tool ~/.config/zed/settings.json
- Windsurf Tools That Don't Upload Prompt/find_tool ~/.codeium/windsurf/mcp_config.json
- Cline Tools That Don't Upload Prompt/find_tool ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Tools That Don't Upload Prompt/find_tool ~/.gemini/settings.json
- Grok Tools That Don't Upload Prompt/find_tool .mcp.json (in your project root)
- ChatGPT Tools That Don't Upload Prompt/find_tool Settings → Connectors → Advanced → Developer mode
- Claude.ai Tools That Don't Upload Prompt/find_tool Settings → Connectors → Add custom connector
- LangChain Tools That Don't Upload Prompt/find_tool pip install langchain-mcp-adapters
Other prompts on this server
Tools That Don't Upload also offers 3 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 14 November 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.