Mobile.de Scraper avatar
Mobile.de Scraper

Pricing

$1.50 / 1,000 results

Go to Store
Mobile.de Scraper

Mobile.de Scraper

Developed by

Ivan Vasiljević

Ivan Vasiljević

Maintained by Community

Extract data from mobile.de for data on thousands of car listings. Scrape car listings, extract descriptions, images, prices, mileage, contact number, addresses, names, engine information, the transmission of the car, and all other listing details.

0.0 (0)

Pricing

$1.50 / 1,000 results

3

Total users

12

Monthly users

9

Runs succeeded

>99%

Last modified

10 days ago

You can access the Mobile.de 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=ivanvs/mobile-de-scraper",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with Mobile.de 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=ivanvs/mobile-de-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=ivanvs/mobile-de-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.