ask_a_locator — Taco Street Locating MCP Tool
ask_a_locator
(ask a locator) is one of 9 tools on the
Taco Street Locating
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call ask_a_locator from your client
- Claude Code Taco Street Locating ask_a_locator run in your project directory
- Claude Desktop Taco Street Locating ask_a_locator ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Taco Street Locating ask_a_locator ~/.cursor/mcp.json
- VS Code Taco Street Locating ask_a_locator .vscode/mcp.json
- Zed Taco Street Locating ask_a_locator ~/.config/zed/settings.json
- Windsurf Taco Street Locating ask_a_locator ~/.codeium/windsurf/mcp_config.json
- Cline Taco Street Locating ask_a_locator ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Taco Street Locating ask_a_locator ~/.gemini/settings.json
- Grok Taco Street Locating ask_a_locator .mcp.json (in your project root)
- ChatGPT Taco Street Locating ask_a_locator Settings → Connectors → Advanced → Developer mode
- Claude.ai Taco Street Locating ask_a_locator Settings → Connectors → Add custom connector
- LangChain Taco Street Locating ask_a_locator pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http taco-street-locating https://ai.tacostreetlocating.com/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.