Otto.de Scraper avatar
Otto.de Scraper

Pricing

$25.00/month + usage

Go to Store
Otto.de Scraper

Otto.de Scraper

Developed by

Lexis Solutions

Lexis Solutions

Maintained by Community

The Otto.de Apify Scraper is an automated tool for extracting valuable data from Otto.de - one of the leading e-commerce platforms in Germany. It provides businesses with insights for market analysis, competitor monitoring, and price tracking. Ideal for e-commerce and market research.

5.0 (5)

Pricing

$25.00/month + usage

16

Total users

54

Monthly users

4

Runs succeeded

97%

Last modified

2 years ago

You can access the Otto.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=lexis-solutions/otto-de-scraper",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with Otto.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=lexis-solutions/otto-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=lexis-solutions/otto-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.