@striderlabs/mcp-yelp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| yelp_search_restaurants | Search for restaurants on Yelp by location, cuisine, price range, and more. |
| yelp_search_businessesC | Search for any type of business on Yelp (not just restaurants). |
| yelp_get_business_details | Get detailed information about a specific business including hours, menu, amenities. |
| yelp_get_reviewsB | Get reviews for a specific business with ratings and text. |
| yelp_get_photos | Get photos for a specific business. |
| yelp_get_menuB | Get menu items and prices for a restaurant. |
| yelp_get_hoursA | Get business hours including special hours and holidays. |
| yelp_find_similar | Find businesses similar to a given business. |
| yelp_get_trendingB | Get trending/hot new restaurants and businesses in a location. |
| yelp_get_collections | Get curated Yelp collections for a location (best of lists, staff picks). |
| yelp_check_wait_time | Check estimated wait time at a restaurant (if available). |
| yelp_get_dealsB | Get current deals and offers for businesses in a location. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct aspect of Yelp data: deals, hours, menu, reviews, trending, and general search. There is no overlap in purpose, so an agent can clearly distinguish them.
All tools start with 'yelp_' and use a verb_noun pattern, but 'search_businesses' uses 'search' instead of 'get', which is a minor deviation. Overall, the naming is predictable and readable.
With 6 tools, the set is well-scoped for a Yelp MCP server. It covers core read operations without unnecessary bloat, fitting the typical use cases for a Yelp integration.
The tools cover search, reviews, hours, menu, deals, and trending, which are key read operations. A minor gap is the lack of a dedicated business detail tool, but search likely covers basic info. Write operations are not expected.