@striderlabs/mcp-shakeshack
Related Servers
Alternatives to @striderlabs/mcp-shakeshack
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for Wendy's that enables AI agents to search the menu, view nutrition info, find nearby locations, and place mobile orders.711 npmMIT
- AlicenseAqualityDmaintenanceMCP server that enables AI agents to interact with Chick-fil-A via browser automation for menu search, nutrition info, location finder, and mobile ordering.79 npmMIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to discover restaurants and place food delivery orders on Uber Eats and Thuisbezorgd (Just Eat Takeaway). It provides tools for restaurant discovery and order management through normalized platform APIs.2 npm2MIT
- AlicenseAqualityBmaintenanceAn MCP server for the Open Food Facts API that allows users to search, read, and contribute to a global food database. It enables looking up nutrition data by barcode or name and managing product information through natural language.1046 npm3MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server for food-related queries powered by MiniMax AI, enabling natural language interaction via a chat API.30 npmMIT
- FlicenseAqualityCmaintenanceMCP server that provides food composition data from USDA FoodData Central, enabling search, nutrient lookups, and recipe nutrition calculations.4-
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose with no overlap: find_locations (geographic search), get_featured_items (special menu items), get_location_details (specific location info), get_menu (full menu), get_nutrition_info (nutritional data), get_ordering_info (ordering methods), and search_menu (menu item search). The descriptions reinforce these distinct functions, making tool selection unambiguous.
All tools follow a consistent verb_noun pattern using snake_case: find_locations, get_featured_items, get_location_details, get_menu, get_nutrition_info, get_ordering_info, and search_menu. The verbs 'find', 'get', and 'search' are appropriately used for their respective actions, creating a predictable and readable naming convention throughout.
With 7 tools, the server is well-scoped for its restaurant information domain. Each tool serves a clear purpose (location discovery, menu access, nutrition details, ordering info), and none feel redundant or unnecessary. This count aligns well with typical MCP server ranges (3-15 tools) for focused functionality.
The toolset provides comprehensive coverage for accessing Shake Shack information: locations (find/details), menu (full/featured/search), nutrition, and ordering methods. A minor gap exists in the lack of tools for actual ordering or transaction processing, but given the server's apparent informational focus, this is reasonable. The surface supports common agent workflows without dead ends.