find-a-tool — Agent Tested MCP Prompt
find-a-tool
is one of 3 prompts on the
Agent Tested
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke find-a-tool from your client
- Claude Code Agent Tested Prompt/find-a-tool run in your project directory
- Claude Desktop Agent Tested Prompt/find-a-tool ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Agent Tested Prompt/find-a-tool ~/.cursor/mcp.json
- VS Code Agent Tested Prompt/find-a-tool .vscode/mcp.json
- Zed Agent Tested Prompt/find-a-tool ~/.config/zed/settings.json
- Windsurf Agent Tested Prompt/find-a-tool ~/.codeium/windsurf/mcp_config.json
- Cline Agent Tested Prompt/find-a-tool ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Agent Tested Prompt/find-a-tool ~/.gemini/settings.json
- Grok Agent Tested Prompt/find-a-tool .mcp.json (in your project root)
- ChatGPT Agent Tested Prompt/find-a-tool Settings → Connectors → Advanced → Developer mode
- Claude.ai Agent Tested Prompt/find-a-tool Settings → Connectors → Add custom connector
- LangChain Agent Tested Prompt/find-a-tool pip install langchain-mcp-adapters
Other prompts on this server
Agent Tested 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 5 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.