Serper | Google Places Scraper avatar
Serper | Google Places Scraper

Pricing

$10.00 / 1,000 searches

Go to Store
Serper | Google Places Scraper

Serper | Google Places Scraper

Developed by

Rizuan

Rizuan

Maintained by Community

Serper (serper.dev) makes it incredibly cheap to scrape Google Maps. But while they provide the code, you need to implement it yourself. With this actor, you just need to specify your search parameters & API key, and it'll do the extraction for you. Perfect for integration with tools like Clay.

5.0 (1)

Pricing

$10.00 / 1,000 searches

0

Total users

29

Monthly users

8

Runs succeeded

>99%

Last modified

4 months ago

You can access the Serper | Google Places Scraper 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",
"reezuan/serper-google-places-scraper"
],
"env": {
"APIFY_TOKEN": "<YOUR_API_TOKEN>"
}
}
}
}

Configure MCP server with Serper | Google Places Scraper

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=reezuan/serper-google-places-scraper",
"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.