find-a-tool/SKILL.md — Agent Tested MCP Resource
find-a-tool/SKILL.md
is one of 3 resources on the
Agent Tested
MCP server. Connect the server and your client can attach it as context.
by client
How to attach find-a-tool/SKILL.md from your client
- Claude Code Agent Tested Resource/find-a-tool/SKILL.md run in your project directory
- Claude Desktop Agent Tested Resource/find-a-tool/SKILL.md ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Agent Tested Resource/find-a-tool/SKILL.md ~/.cursor/mcp.json
- VS Code Agent Tested Resource/find-a-tool/SKILL.md .vscode/mcp.json
- Zed Agent Tested Resource/find-a-tool/SKILL.md ~/.config/zed/settings.json
- Windsurf Agent Tested Resource/find-a-tool/SKILL.md ~/.codeium/windsurf/mcp_config.json
- Cline Agent Tested Resource/find-a-tool/SKILL.md ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Agent Tested Resource/find-a-tool/SKILL.md ~/.gemini/settings.json
- Grok Agent Tested Resource/find-a-tool/SKILL.md .mcp.json (in your project root)
- ChatGPT Agent Tested Resource/find-a-tool/SKILL.md Settings → Connectors → Advanced → Developer mode
- Claude.ai Agent Tested Resource/find-a-tool/SKILL.md Settings → Connectors → Add custom connector
- LangChain Agent Tested Resource/find-a-tool/SKILL.md pip install langchain-mcp-adapters
Other resources on this server
Agent Tested also offers 3 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 5 November 2026.
A listing does not declare its resources, 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 resource's type and contents.