search_restaurants_by_text — Namaste America MCP Tool Read-only
search_restaurants_by_text
(search restaurants by text) is one of 66 tools on the
Namaste America
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call search_restaurants_by_text from your client
- Claude Code Namaste America search_restaurants_by_text run in your project directory
- Claude Desktop Namaste America search_restaurants_by_text ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Namaste America search_restaurants_by_text ~/.cursor/mcp.json
- VS Code Namaste America search_restaurants_by_text .vscode/mcp.json
- Zed Namaste America search_restaurants_by_text ~/.config/zed/settings.json
- Windsurf Namaste America search_restaurants_by_text ~/.codeium/windsurf/mcp_config.json
- Cline Namaste America search_restaurants_by_text ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Namaste America search_restaurants_by_text ~/.gemini/settings.json
- Grok Namaste America search_restaurants_by_text .mcp.json (in your project root)
- ChatGPT Namaste America search_restaurants_by_text Settings → Connectors → Advanced → Developer mode
- Claude.ai Namaste America search_restaurants_by_text Settings → Connectors → Add custom connector
- LangChain Namaste America search_restaurants_by_text pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http namaste-america https://namasteamerica.us/mcpOther tools on this server
- get_indian_restaurants
- get_indian_movies_in_theaters
- search_h1b_sponsors
- get_restaurant_details
- submit_correction
- submit_review
- get_reviews
- get_indian_temples
- get_temple_details
- search_temples_by_text
- get_indian_groceries
- get_grocery_details
- search_groceries_by_text
- get_indian_professionals
- get_professional_details
- search_professionals_by_text
- get_indian_salons
- get_salon_details
- search_salons_by_text
- get_indian_events
- get_event_details
- search_events_by_text
- get_indian_apparel
- get_apparel_details
- search_apparel_by_text
- get_indian_sweets
- get_sweets_details
- search_sweets_by_text
- get_indian_studios
- get_studio_details
- search_studios_by_text
- get_indian_services
- get_service_details
- search_services_by_text
- get_indian_community
- get_community_details
- search_community_by_text
- get_indian_legal
- get_legal_details
- search_legal_by_text
- get_indian_education
- get_education_details
- search_education_by_text
- get_indian_realestate
- get_realestate_details
- search_realestate_by_text
- get_indian_finance
- get_finance_details
- search_finance_by_text
- search_all
- get_festival_dates
- search_knowledge
- submit_listing
- get_movie_details
- get_h1b_sponsor_details
- search_community_questions
- get_community_answers
- get_today_highlights
- get_offers
- ask_community_question
- save_place
- unsave_place
- list_saved_places
- follow_city
- list_follows
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.