search_locations — ApplyAll MCP Tool Read-only
search_locations
(search locations) is one of 20 tools on the
ApplyAll
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call search_locations from your client
- Claude Code ApplyAll search_locations run in your project directory
- Claude Desktop ApplyAll search_locations ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ApplyAll search_locations ~/.cursor/mcp.json
- VS Code ApplyAll search_locations .vscode/mcp.json
- Zed ApplyAll search_locations ~/.config/zed/settings.json
- Windsurf ApplyAll search_locations ~/.codeium/windsurf/mcp_config.json
- Cline ApplyAll search_locations ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ApplyAll search_locations ~/.gemini/settings.json
- Grok ApplyAll search_locations .mcp.json (in your project root)
- ChatGPT ApplyAll search_locations Settings → Connectors → Advanced → Developer mode
- Claude.ai ApplyAll search_locations Settings → Connectors → Add custom connector
- LangChain ApplyAll search_locations pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://applyall.com/mcp
Other tools on this server
- search_jobs
- get_job
- search_job_titles
- list_packages
- get_connect_instructions
- register_account
- get_profile
- update_profile
- set_current_location
- add_desired_location
- remove_desired_location
- add_desired_title
- remove_desired_title
- add_blocklist_entry
- remove_blocklist_entry
- upload_resume
- set_applications_paused
- get_credit_balance
- create_checkout
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.