autosearch_list_my_runs — autosearch MCP Tool
autosearch_list_my_runs
(autosearch list my runs) is one of 6 tools on the
autosearch
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call autosearch_list_my_runs from your client
- Claude Code autosearch autosearch_list_my_runs run in your project directory
- Claude Desktop autosearch autosearch_list_my_runs ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor autosearch autosearch_list_my_runs ~/.cursor/mcp.json
- VS Code autosearch autosearch_list_my_runs .vscode/mcp.json
- Zed autosearch autosearch_list_my_runs ~/.config/zed/settings.json
- Windsurf autosearch autosearch_list_my_runs ~/.codeium/windsurf/mcp_config.json
- Cline autosearch autosearch_list_my_runs ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI autosearch autosearch_list_my_runs ~/.gemini/settings.json
- Grok autosearch autosearch_list_my_runs .mcp.json (in your project root)
- ChatGPT autosearch autosearch_list_my_runs Settings → Connectors → Advanced → Developer mode
- Claude.ai autosearch autosearch_list_my_runs Settings → Connectors → Add custom connector
- LangChain autosearch autosearch_list_my_runs pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http autosearch https://exatoshi.uk/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.