Yelp Scraper (Pay per Result) avatar
Yelp Scraper (Pay per Result)

Deprecated

Pricing

$4.00 / 1,000 results

Go to Store
Yelp Scraper (Pay per Result)

Yelp Scraper (Pay per Result)

Deprecated

Developed by

Caprolok

Caprolok

Maintained by Community

📈 Discover the power of the Yelp Scraper! Extract detailed business profiles, ratings, and reviews from Yelp effortlessly. Perfect for entrepreneurs, analysts, and marketers, this tool offers crucial insights for strategic planning and competitive intelligence. 🏆📊 #YelpScraper #MarketResearch

0.0 (0)

Pricing

$4.00 / 1,000 results

0

Total users

11

Monthly users

8

Last modified

10 months ago

You can access the Yelp Scraper (Pay per Result) programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.

{
"mcpServers": {
"local-actors-mcp-server": {
"command": "npx",
"args": [
"-y",
"@apify/actors-mcp-server",
"--actors",
"caprolok/yelp-scraper-pay-per-result"
],
"env": {
"APIFY_TOKEN": "<YOUR_API_TOKEN>"
}
}
}
}

Configure MCP server with Yelp Scraper (Pay per Result)

You can interact with the MCP server via standard input/output - stdio (as shown above), which is ideal for local integrations and command-line tools such as the Claude desktop client, or you can interact with the server through Server-Sent Events (SSE) to send messages and receive responses, which looks as follows:

{
"mcpServers": {
"remote-actors-mcp-server": {
"type": "sse",
"url": "https://mcp.apify.com/sse?actors=caprolok/yelp-scraper-pay-per-result",
"headers": {
"Authorization": "Bearer <YOUR_API_TOKEN>"
}
}
}
}

You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other supported MCP client of your choice.

If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.