Skip to main content
Glama
pipeworx-io

Yelp MCP

by pipeworx-io

mcp-yelp

Yelp MCP — wraps the Yelp Fusion API (api.yelp.com/v3)

Part of Pipeworx — an MCP gateway connecting AI agents to 1684+ live data sources.

Tools

Tool

Description

search_businesses

Search for local businesses and restaurants on Yelp by term and location. Returns matching businesses with star ratings, review counts, price, categories, address, and phone. Example: search_businesses({ term: "pizza", location: "San Francisco, CA" }).

get_business

Get full details for a single Yelp business by its id or alias. Returns rating, review count, price, categories, address, phone, hours, photos, and coordinates. Example: get_business({ id: "garaje-san-francisco" }).

get_reviews

⚠️ UPSTREAM-UNRELIABLE — Yelp Fusion's /reviews endpoint has been 404-ing on most ids since mid-2026 even for valid businesses. PREFER get_business (which sometimes inlines a snippet) or search_businesses for review-context queries. If you must call get_reviews: pass the ENCRYPTED business id (long alphanumeric, e.g. "WavvLdfdP6g8aZTtbBQHTw") returned in search_businesses results — aliases / slugs (e.g. "garaje-san-francisco") reliably 404. Returns up to 3 review snippets per business (rating, text, author, timestamp); "limit" is capped by Yelp upstream regardless of what you pass.

Related MCP server: Yelp Fusion MCP Server

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "yelp": {
      "url": "https://gateway.pipeworx.io/yelp/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/yelp/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1684+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/search_businesses. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "yelp": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-yelp"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-yelp

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Yelp data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    Enables conversational interactions with Yelp's business data through an MCP server, allowing natural language queries about local businesses, multi-turn conversations, and direct business inquiries powered by Yelp Fusion AI.
    1
    26
    Apache 2.0
  • F
    license
    Not graded
    quality
    D
    maintenance
    Provides access to Yelp's business database for searching local businesses, retrieving detailed ratings and reviews, and performing market research through business counts. It enables users to look up businesses by location, category, or phone number using the Yelp Fusion API.
    1
    -
  • F
    license
    A
    quality
    D
    maintenance
    Provides Yelp Fusion API access through MCP tools and resources for searching businesses, getting reviews, and more.
    5
    -