Yelp MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HASDATA_API_KEY | Yes | Your HasData API key from the dashboard, required for authentication. |
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 | {
"listChanged": false
} |
| completions | {} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hasdata_yelp_place_getPlaceDetailsA | Get Yelp Place Details Fetches a single Yelp business by Yelp ID or alias with domain targeting. Returns name, address, phone, website, price range, categories, overall rating, review count, hours, amenities, photos, and highlighted reviews. Use to enrich leads or listings with verified Yelp metadata, monitor a competitor's rating and review count over time, or validate hours/amenities before displaying venue details to end users. |
| hasdata_yelp_reviews_getPlaceReviewsA | Get Yelp Place Reviews Fetches the review feed of a single Yelp business by Yelp ID, with sorting (relevance, date, rating, elites), filtering by star rating, language and free-text query, and cursor pagination. To page, either step |
| hasdata_yelp_search_getSearchResultsA | Get Yelp Search Results Runs a Yelp business search by keyword and location with optional map-bounded radius via the |
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 3 tools
Each tool has a clearly distinct purpose: search finds businesses, place details returns metadata for a single business, and reviews returns the review feed. There is no functional overlap between them.
All tools follow the same hasdata_yelp_<area>_get<Thing> pattern, using a consistent snake_case prefix with CamelCase action names. The naming is predictable and makes the resource type obvious.
Three tools is a well-scoped set for a Yelp data access server. Each tool covers a core need—search, business details, and reviews—without redundancy.
The toolset forms a complete read-only workflow: search for businesses, fetch place details, and retrieve reviews. There are no dead ends, and write operations are outside the apparent scope of the server.