Skip to main content
Glama
markswendsen-code

@striderlabs/mcp-yelp

Related Servers

Alternatives to @striderlabs/mcp-yelp

No user-submitted related servers found.

    Related 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search Yelp for local businesses and restaurants by term and location, pull full details for a given business such as ratings, price, categories, hours, and photos, and retrieve review snippets. It wraps the Yelp Fusion API and can run either through the Pipeworx gateway or as a local stdio server.
      298 npm
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Provides Yelp Fusion API access through MCP tools and resources for searching businesses, getting reviews, and more.
      5
      -
    • A
      license
      A
      quality
      A
      maintenance
      Enables Yelp business search, place details, and full review feeds as structured JSON through a hosted MCP endpoint, with no Yelp Fusion key required.
      3
      37 npm
      110 PyPI
      11
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      MCP server that enables LLMs to interact with Tripadvisor API, supporting location data, reviews, and photos through standardized MCP interfaces
      5
      64
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Minimal MCP server for the Yelp Fusion API v3, enabling business search, phone lookup, match, details, and reviews via FastMCP.
      5
      -

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues