Apple App Store Search Scraper avatar
Apple App Store Search Scraper

Pricing

Pay per event

Go to Store
Apple App Store Search Scraper

Apple App Store Search Scraper

Developed by

Scrape It

Scrape It

Maintained by Community

Search the Apple App Store for apps matching a search term. Scrape rich app information app's name, developer, description, price, rating....

0.0 (0)

Pricing

Pay per event

1

Total users

11

Monthly users

7

Runs succeeded

>99%

Last modified

3 months ago

You can access the Apple App Store Search 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": {
"apify": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.apify.com/sse?actors=dan.scraper/apple-app-store-search-scraper",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with Apple App Store Search Scraper

You have a few options for interacting with the MCP server:

  • Use mcp.apify.com via mcp-remote from your local machine to connect and authenticate using OAuth or an API token (as shown in the JSON configuration above).

  • Set up the connection directly in your MCP client UI by providing the URL https://mcp.apify.com/sse?actors=dan.scraper/apple-app-store-search-scraper along with an API token (or use OAuth).

  • Connect to mcp.apify.com via Server-Sent Events (SSE), as shown below:

{
"mcpServers": {
"apify": {
"type": "sse",
"url": "https://mcp.apify.com/sse?actors=dan.scraper/apple-app-store-search-scraper",
"headers": {
"Authorization": "Bearer <YOUR_API_TOKEN>"
}
}
}
}

You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other 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.